Several of our customers have had trouble creating an executable file from a LabVIEW project using the Yoctopuce library. An issue with a "library not found". Therefore this week we are going to provide you with a small tutorial on this topic.
Starting this week, you can use Yoctopuce modules directly from an application written in TypeScript. We have indeed just published a new programming library for this language, which is becoming more and more popular. It's therefore the occasion to offer you a tutorial for new users of Yoctopuce modules, with a short and simple but realistic example. As usual, we assume that you have some prior knowledge of TypeScript programming, but we'll explain the rest in detail.
Despite all our efforts, sometimes our software or our programming libraries do not behave in the way expected by our customers. This can be due to a bug or to a too complex interface. If this happens to you, support is available to help you solve these issues. However, we often get vague or incomplete questions. In order to avoid unnecessary email exchanges, here is a list of recommendations for contacting support.
Our .NET Proxy library was originally designed to enable integration with LabVIEW, but you can easily use it in other development environments, such as WinDEV. And since we're not one to brag, we'll prove it to you...
Almost all the features of the Yoctopuce API are present in the LabVIEW library, this represents more than 2000 possible distinct functions through more than 80 classes. However, there is only one VI per class, so how could we cram an average of 25 calls per VI? This week, we are going to explain to you in more details the concept of proxy objects for the LabVIEW Yoctopuce API.
1 2 3 4 5 6 7