Mes premières impressions sur les Realwear HMT-1

Et voilà, j’ai lâché quelques teasers, maintenant je dois assumer. Nous sommes donc partis pour mes premières impressions au déballage de cet appareil étrange, un unboxing quoi :-). J’ai pu donc, courtesy of Lenovo, avoir entre mes mains un Realwear HMT-1, et mener quelques essais : mise en route et configuration manuelle Installation d’une application, utilisation des lunettes avec un document PDF, et essais de base Utilisation de la plate-forme Foresight by Realwear Je parlerais sûrement de Lenovo Thinkreality, la plate-forme dédiée à la gestion des devices de XR, mais cela fera l’objet d’un second article, celui-ci sera déjà bien assez long. ...

8 décembre 2021 · 9 min · Frederi Mandin

One augmented reality use case : the remote expert

J’admets être venu au sujet du remote Expert par accident. Une demande client sur le sujet m’a amené à creuser quelques pistes. Une fois les quelques solutions utilisées et testées, j’avais en main de quoi effectuer simplement quelques démos, parfois de manière inopinée. J’ai été convaincu très vite du potentiel de cette solution simple à mettre en œuvre. Les quelques démos effectuées au détour d’une conférence ou d’une simple discussion montrent que les clients sont convaincus aussi. Le Remote Expert (ou Remote Assist), qu’est-ce que c’est? Imaginons que vous ayez dans votre structure une flotte d’intervenants sur site pour des tâches très variées. Ceux-ci ne peuvent pas être experts dans tous les domaines, ni connaître par avance tout ce dont ils auront besoin avant d’être appelés en dépannage. D’un autre côté, vous aurez sûrement un expert du domaine, qui maitrisera parfaitement l’intervention à effectuer. Mais celui-ci ne sera pas en mesure d’être présent sur l’ensemble des sites au cours d’une journée, les pannes ne se planifiant jamais comme cela nous arrangerait. Il faudrait donc une solution permettant à l’expert de se démultiplier. Comme le clonage humain n’est pas encore au point ni éthiquement accepté, il faut trouver autre chose. Et voici le Remote Expert. Cette solution consiste à utiliser un appareil mobile sur le site de l’intervention, pour partager l’environnement de travail avec l’expert. Et surtout de pouvoir annoter et donner des indications sur cet environnement. ...

29 mai 2019 · 5 min · Frederi Mandin

Brainwave, Tensorflow : AI at the edge

About two years ago, Google announced the availability of TensorFlow processing units in its cloud. They are dedicated microcontrollers built for training and running Machine Learning models. TPU are available within Gcloud as an execution platform for ML (of course, optimized for TensorFlow). During the summer, they unveiled the edge equivalent of these TPU, which are named… Edge-TPU :) These are very specific ASIC designed to execute ML models on an edge device, i.e. a small device close to the sensors gathering the data. This allows for a fast decision, without the need to send a truckload of data back up to the cloud. But wait for it… Microsoft did just uncover a device called DataBox Edge. I know, the main purpose of this device is to provide a storage gateway to help you use Azure storage locally, and move the data between the device and Azure, hence the name. Bear with me, the path is a bit convoluted, and I would like you to enjoy every turn of it. Databox Edge is also equipped with what has been called IoT Edge. This nifty piece of technology will enable you to run Azure-based workloads on an edge device, such as Azure Functions, Azure ML, Azure Stream Analytics etc. IoT Edge has been out in the open for about a year now, to be deployed onto compatible devices. And, and that’s where we hit the Edge-TPU spot, also included in Databox Edge is a shiny new Microsoft hardware, called Brainwave. The name kind of gives away the purpose, especially after I guided you through the maze. Anyway, this chip is designed to run AI models on an edge device, and do it with impressive performance and efficiency. I know, at this point, you would point out at the fact that it might again be a case of “We did it first!” from Google. I’d like to focus a big difference between the two approaches. For once, I could not say which would win in the long term. In theory I prefer the approach from Microsoft, but that does not mean it will prevail (or that they would not change tactics and build something more like Edge-TPU). The difference is that Google built an ASIC, whereas Microsoft used Intel FPGA to deploy its Brainwave architecture. OK, this needs some explaining. First the names : ASIC means Application Specific Integrated Circuit. FPGA means Field Programmable Gate Array. You see where this is going? An ASIC is a very specific chip, designed to do only one thing, but optimized to its core. I should be able to execute one kind of job, but do it perfectly. One the other hand, an FPGA is reprogrammable after its deployment, to be able to adapt to future needs. Its performance is close to an ASIC, but not quite equal. To complete the panorama, going from specific to general use, we would then add GPU (Graphical Processing Units, as in your graphics cards) and then CPUs (ye good ol’ Pentium). Microsoft took the path of versatility, whereas Google focused on a particular use. As I mentioned, I’m not sure who has the best strategy, and whether there will even be a fight, but I am very curious to see both chips in the wild!

2 novembre 2018 · 3 min · Frederi Mandin

IoT Challenges

After a long summer break, getting back to writing is a bit difficult, so here is a first post for a new era. I’ll be switching jobs early September, so there might a slight variation in the subjects I’ll write about. As highlighted in Gartner 2018 Cycle of Hype study, IoT is now a mature tech and we will see more and more large scale projects being deployed in the wild. I would like to expand a bit about what it entails to start an IoT initiative, whether it be to design a new product to sell, or to gain some insight and improve your own processes. The steps are familiar to anyone who has ever come close to a project in his/her life: 1. 2. 3. 4. 5. 6. ...

24 août 2018 · 4 min · Frederi Mandin

IoT everywhere, for everyone

Today is another tentative to explain part of the Microsoft Azure catalog of solutions. As I did write about the different flavors of containers in Azure, I feel that it’s time for a little explanation about the different ways of running you IoT solution in Azure. There are three major ways of running an IoT platform in Azure : build your own, Azure IoT Suite and IoT Central. There are some sub-versions of those, that I will mention as I go along but these are the main players. I have listed those in a specific order, on purpose : ...

27 février 2018 · 3 min · Frederi Mandin

Voice control and security

I will assume that I am definitely not the first one to write about that, but I feel the need to write anyway. We saw during a few recent events that our new beloved always listening devices can interpret an ordre form almost anyone (Someone ordered a Whopper? Burger King: OK Google!) It seems trivial and a bit childish, but when you start integrating many services into a system like that, you may have to think about security. This goes at different levels : from limiting commands to voice-print recognition. ...

26 juin 2017 · 3 min · Frederi Mandin