All Activity

Real-time is nice until you need to find that one answer from three weeks ago and it's buried under 400 messages of banter lol. Forums age better imo, Discord is where the traffic is these days though.

ngl undisclosed cross-posts are the worst, you sink time into an answer that's already sitting on the ni forum

I should also point out it is forum etiquette to state and link if a question is a cross-post on Ni.com. https://forums.ni.com/t5/Industrial-Communications/NI-9145-with-NI-9476-9375-in-TwinCAT/td-p/4485626

IIRC. There is a safe-mode that will set outputs to a safe value (presumably 0v for sourcing 24v) when active. However. I think the status LED of the controller should be blinking red to signify that. Apart from that. If a variable can be set but it's not being replicated in the slave device (the NI device is a slave, right?) then it points to a mismatch in the PDO mapping. I do not know how you would tell that from the XML files you supplied but you may know more about their construction than I.

This problem is not unique to mailing lists. Forums, StackOverflow, and official technical support channels still encounter them (although the modern channels do have more tools to deal with them).

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.