Leaderboard
Popular Content
Showing content with the highest reputation on 06/08/2018 in all areas
-
Maybe you should give it a name and start selling it :-o1 point
-
I was thinking, an useful addition to the cool Modbus Comm Tester would be a section for Read Device Identification. Probably fitting nicely the 7th rectangle on the FP is the difficult part of it; the extension of the code, which is elegantly written, seems trivial. What do you think about?1 point
-
It's not necessarily a mistake but if you go down that path you have to make double and triple sure to not create circular references and similar stuff in your class hierarchy. While this can work on a Windows system (albeit with horrendous load times when loading the top level VI and according compile times) an executable on RT usually simply dies on startup with such a hierarchy.1 point
-
It's always a project by project decision for me. If I need the flexibility, I'll go TS. Otherwise, it's not worth the deployment licensing hassle. Another advantage to rolling your own is you get to use LabVIEW's block diagram representation of the sequence. It's a great visual—things in parallel execute in parallel. Data flows on wires. What can I say?1 point