Yoctopuce modules: inventory and tree structure

By martinm, in Programming, january 17,2016.

The Yoctopuce API was designed to easily drive any Yoctopuce module with a minimum of code. It's therefore very easy to make an inventory of all the modules directly connected by USB to a machine. However, up till now, it was rather difficult, not to say impossible, to rebuild the exact tree structure of a system based on Yoctopuce modules, in particular for modules connected via the network. The latest version of the API now allows you to do this thanks to three new functions.

Building a USB-driven variable resistor

By martinm, in DIY and Electronics, january 08,2016.

From time to time, people ask us if our roadmap would not include a digital USB potentiometer. The answer is no, because such product would probably be too limited to be useful. However, we can tell you how to build your own digital variable resistance, using just a few relays and resistors.

The WebSocket callbacks in Java

By seb, in Programming and New stuff, january 01,2016.

Last week we published a preview of our Java and Javascript library with WebSocket support. This week we have updated our RSS feed reader example in Java, which was using the classical HTTP Callback. We have now made it interactive with the help of WebSockets.

Remote device control using WebSocket callbacks

By mvuilleu, in New stuff and Programming, december 26,2015.

Until now, there were two different ways of accessing Yoctopuce devices over the network: either by direct connection over a local network, or using the special HTTP callback mode which makes it possible to drive a Yoctopuce module sitting on a remote network behind a NAT filter. The HTTP callback method however had some limitations. Today, we are introducing a new connection method, named WebSocket callback, that brings all direct connection features to the callback scheme.

Experimenting with EcmaScript 2015

By mvuilleu, in Programming and New stuff, december 18,2015.

JavaScript comes back from far away. Originally, it was only a source of incompatibilities and a nightmare for web designers. Having to code a version for IE and one for Netscape on the same web site was commonplace. Fortunately, the JavaScript language has evolved amazingly to become the ubiquitous companion of HTML5 on almost all internet sites on the planet. With the latest version of the language, adopted as a new standard this past Summer, new possibilities came into being. They deserve to be known and exploited.