Antoine Chalons

En voyant le code, il me semble qu'il a été écrit pour lire un fichier csv, et il ne peut pas lire un fichier xls(x). Si tu dis que ça marchait avant et que ça ne marche plus maintenant sans avoir changé le code, peut être as tu ouvert le fichier csv avec Excel et sauvé en xls(x)? Vérifie le format de ton fichier, et le chemin du fichier lu par le logiciel. Ensuite, si tu veux lire des données dans un fichier xls(x) au lieu de csv, il y a plusieurs méthodes, chacune a ses avantages et inconvénients.. - activeX, Windows only, nécessite Excel installé sur la machine - pandas, multi plateforme, nécessite python et pandas installé - vi de Darren (voir forum NI), ne marche pas avec toutes les versions d'excel, multi-platform Bon courage !

I would suggest rabbitmq, i want(ed) to present it at a LabVIEW user group (LUGE) but haven't done it yet. It's very powerful. I use redis and did a quick presentation (in french) at LUGE recently, i haven't used the stream feature though, I only used it as cache.

i can't really answer your question but I suggest you watch this presentation :

Totaly justified by productivity gains brought by all the amazing new features, right? Someone has to pay for the NXG failure I guess.

该文件中有四行头文件 (4 rows of header in this file) 下面是一个程序，它将读取四个标题行，然后每次读取其余的 100 行 read csv per chunk of 100 rows.vi

您可以按行读取文件 如果您提供文件的一小部分，我可以帮助您编写一个 vi 来逐行加载文件

what is the size of you images and what's the max duration you need to save for? 180FPS is not that much, you could just save images to a SSD or if needed to a RAID drive just make put acquisition in parallel of save and pre-allocate enough buffers to store the acquired images. in 2007 (before SSD existed) I worked on an image streaming to disk system, up to 8000fps (images were tiny and monochrome), max duration was 30 seconds, but with a ggod SSD this is nothing.

This bug has been fixed by NI in patch 24.3.2f2 of LabVIEW 2024 Q3

When you search for a LabVIEW toolkit, you should start on www.vipm.io Take a look at this one : https://www.vipm.io/package/hse_lib_gitlab_api/ if you need support HSE has a discord server, they are quite responsive.

23.1 is between double quotes, which make it a string, not a numerical. if you remove the double quotes, then is will be a numerical value. hope this helps

same here, I don't check the wiki every day, on average I go 2-3 times a month, I never had issues.

I fully agree that anything, even smoke signals in the wind, are better that NSVs. I'm using Redis, I also started from an existing lib found on the interweb, tweaked a bit for my needs. We now have multiple golang services as well as LabVIEW services connecting to Redis for cache and using RabbitMq for messaging. For some small tests on my Windows machine I've used Redis on WSL, easy to use. At the next local user group meeting I might do a short presentation about it, if you have faced any issues, I'd be interested in your feedback. Cheers

I could install it with VIPM 2022 and ZLIB Extract All Files To Dir (Path) successfully unzipped the lvappimg edit : and same with VIPM 2017 on a different Ubuntu VM Thank you so much for that!

that would be great, if you send me 5.0.4 i can install and try

I see that it's not trivial to handle properly all the cases, to avoid error 8 when installing the zip package the first time, my suggestion is to edit the post install vi like I did below, quick and dirty, works for me