All Activity

Mailing lists were great for maintainers, horrendous for users. Waiting a week to see if your question was answered and trawling through the archives in case you missed a response. One's issue getting engulfed in spam of the same simple issues posted by different people over and over again. I'm glad the days of IRC, Mailing Lists and, hopefully, Discord, are way behind us. Even SQLite eventually dumped the mailing list and support has greatly improved because of it.

I never did the IRC thing, but started with mailing lists as the main support channel. I have quite fond memories of the Info-LabVIEW mailing list started by Tom Coradeschi and currently maintained by Scott Hannahs for posterity. Back when you had to actually connect a modem through your main telephone line in order to go onto the big, friendly (back then at least) internet, mailing lists were very handy as one could respond to the mails offline and then connect to the internet provider to send off all the mails in one batch.

Yeah, the real-time aspect of it does necessarily mean a tradeoff in other places. The LabVIEW Discord is quite well laid out though with sensible channels so we can keep discussion targeted. Personally I value the real-time aspect higher than the formal structure of a traditional forum so I (and many others these days) are gravitating to that kind of technology. It's definitely not perfect though!

IRC? Wow there is a blast from the past. Thank you for digging up some good old memories of many well spent nights spent at my university computer lab arguing with other randos on the internet about alien activity and other tin foil hat stuff 🤣 I did not realise that is where all the LabVIEW developers had gone...

Thanks @Neil Pate! I posted here in the #announcements channel - please let me know if there are any other channels where I should post. https://discord.com/channels/1015999107921354932/1017172031499944037/1549893327971688601 Best, JP

Hi all, Thanks for the input. Sorry I missed the first few replies. As for now, I've already create an NI technical support case on this problem. I also tried NI forum before with no luck.

Discord is a poor support platform and I view Discord with the same contempt as IRC (and for similar reasons). If one thinks Lavag.org is a sub-optimal platform with little activity; answer the question or suggest posting the same question on NI.com. EtherCAT is a niche expertise and if you can't find help here or on NI.com, I very much doubt you will find it on your Discord server.

It is a pity you don't get on so well with Discord, your presence over there is sorely missed.

Both! NI's implementation of EtherCAT leaves a lot to be desired. As to Discord, it's not really the people on there but I just can't seem to manage and keep an overview on the various threads in Discord. Partly that is because I mostly look at it on mobile, but in a webbrowser on the PC it's not that much better, despite the bigger screen.

Because of the people on Discord or because of NI's implementation of EtherCAT? 😉

Unlikely.

@Gabriel Utomo there is not much activity on LAVA these days. You might have more success if you post on the LabVIEW Discord http://discord.gg/labview

Hi all, I need to control a NI 9145 EtherCAT chassis using TwinCAT as the Master. In short, This setup [1] works: Slot 1: NI 9476 (wired only 1x DO to a simple Solenoid Valve, VSup & COM to 24V supply) Slot 2-8: Empty This setup [2] doesn't work: Slot 1: NI 9476 (same as setup [1]) Slot 2: NI 9375 (no wire at all, only slotted in) Slot 3-8: Empty I generated the TwinCAT ESI files using the NI Slave XML Creator, from NI Industrial Comm for EtherCAT 2023. Based on those 2 setup case, I don't think there is any problem on the electrical side. On setup [2], everything looks fine for me on the TwinCAT side, NI 9145 state can change to "OP" and I can set the Online value, but there is no change on the actual DO output. 9476 = sourcing output, so I'm expecting a 24V, which is present if I use setup [1]). I can read the CoE online data, and can also use the AoE - Online tab to read them manually. https://forums.ni.com/t5/image/serverpage/image-id/357407iD344B63133C2AFBD/image-size/medium?v=v2&px=400 Tried: 1. Wire the NI 9375 (setup [2]). The Digital Input worked just fine, but the Output didn't work (both NI 9375 & 9476). 2. Swap the modules with a spare, didn't work. 3. Swap slot 1 & 2 (with their respective ESI files), didn't work. Anyone encounter similar problem, or have any experience using NI 9476 + 9375 together in NI 9145 chassis (maybe using cRIO as the master)? Attached is the ESI file i used for 9476 + 9375. Thank you. Gabriel. DO_DIO.xml

Muchas gracias por tu aporte. Si entiendo, si revisas mis vis veras que cumplía con lo que sugieres, aunque no logre guardar el archivo. Verifique que efectivamente pasaban 2 bytes, se guardaban y nada más. Byte a port causaba el mal funcionamiento, lo elimine según me sugirió Rolf y se resolvió el tema. Aunque corre una vez y cierra el puerto. Estoy en eso...saludos

Sí, se entiende el planteo. Para guardar una imagen JPG no conviene tratar la trama como texto, porque cualquier conversión a string “normal”, fin de línea, encoding o formato puede modificar bytes y el archivo queda inválido. En LabVIEW deberías abrir el archivo con Open/Create/Replace File en modo binario, y escribir directamente los bytes filtrados con Write to Binary File. Asegúrate de que lo que llega al write sea un array de U8 o un string tratado como datos binarios, sin pasar por funciones de texto. También revisa que estés eliminando solo tu encabezado EB91 y no bytes propios del JPG; normalmente un JPG empieza con FF D8 y termina con FF D9. Si después de filtrar el primer byte útil no es FF D8, ahí probablemente está el problema.

I don’t have an RT target handy either right now, but I’ll leave this bumped in case someone here has a cRIO setup and can reproduce it. If anyone jumps in, the most useful thing would probably be a tiny project showing one parent spawning one child on RT, plus the exact LabVIEW version, target model, and whether it fails only as startup/deployed app or also when run interactively. RT issues can be annoyingly context-sensitive, the kind that behave perfectly on Windows and then become “creative” once deployed.

Hi ,I'm from Malaysia .May I know the proper procedures to obtain the CLAD certificate? Need your guidance to properly obtain the course certification. Thank you.

Me queda claro tu sugerencia, Byte a port, fuera. Ahora probaré la modificación que indicaste, entiendo que funcionará sin problemas. Muchas gracias por tu ayuda. Asunto Solucionado, Tema cerrado. Un saludo desde Córdoba, Argentina.🤛

Muchas gracias por tu ayuda, con pequeños cambios lo adapte para que lea la trama del Visa y funciona de maravillas. Lo tuyo es muy profesional. Un saludo, desde Córdoba, Argentina 🫡 PD: se ve poco en la fotito ejemplo 😁

Lots of exclamation points against using Bytes At Serial Port and then goes on to use Bytes At Serial Port More seriously though. You avoid a lot of the problems if you just pop up on the read prototype and set it to Synchronous IO mode instead of Asynchronous.

Shauns code is more robust than just scanning the lines. But you should NOT use Bytes at Serial Port ever (with a few very rare exceptions that you are unlikely to ever encounter)! This is the default presentation that everybody should watch who is trying to implement serial port communication in LabVIEW: https://labviewwiki.org/wiki/VIWeek_2020/Proper_way_to_communicate_over_serial Once you fixed the serial port communication, by using the termination character properly that you already enabled in the Serial Port Init by default, and simply removing the Byte at Port completely and instead wire a large number like 512 to the byte to read input, your main problem is this part of your code. You should replace this with this part of Shaun's code: Your code currently only converts the first two hex parameters of every received byte sequence and with your Bytes at Serial Port function you frequently won't receive an entire line, so only convert part of it. The remainder will be read in the next iteration but totally throw the Match Regular Expression function off the tracks as it does not see the expected line header.

I don't have an Arduino to hand but here is a quick and dirty conversion of your dump file so you can see how it would be done. Not much in the JPG to look at though str2jpg.zip

Hola, gracias por su respuesta, el archivo de texto lo realice para verificar que los datos recibidos sean los correctos. Los datos que recibo es una foto, los envia la Esp32 via arduino, la intención es recibirlos, archivarlos en un file jpg y luego levantarlos y presentarlos en una solapa dedicada. Verificare sus indicaciones y me mantengo atento a su revisión de mis .Vi Gracias por su atención 👍

I haven't looked at the VIs yet but could it be that you use the Write to Text File node and have not disabled the convert EOL option on it? If you want to write binary data, it is usually better to use the according Write to Binary File instead, but here you must not forget to wire a FALSE to the prepend array of string size input if the binary data is already the final format you need in the file.

Tom McQuillan also presented this at gdevcon-na in chicago and those videos just recently went live. The whole video is worth a watch if you're curious about Nominal's business, but if you start at 14:03-17:24 I think its actually a solid tl;dr for why Nominal might be useful to you and how to grab the library. I'll also add here that around this core library I've created add-ins for other NI ecosystem products: A plugin for streaming from FlexLogger, drop-in plugin for existing projects A TestStand steps library which wraps the LabVIEW api in a more test-step-friendly way A TestStand model (report) plugin, which allows drop-in logging of existing test results to Nominal A VeriStand custom device which works very much like the standard "embedded data logger" custom device and can serve as a drop-in replacement or additional logging destination These are still early in their release cycle so if any of this does interest you and you want to try things out, please don't hesitate to reach out so I can make sure to rapidly resolve any issues you might encounter. I mean, obviously my code is perfect and would never have bugs but...just in case.🙃