Jump to content

Neil Pate

  • Posts

  • Joined

  • Last visited

  • Days Won


Neil Pate last won the day on September 25

Neil Pate had the most liked content!


Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since

Contact Methods

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Neil Pate's Achievements

  1. I think there were 182. Everything was video recorded and after editing will be posted on YouTube. Expect something in about six weeks.
  2. ok, and what have you tried so far? What would your rough python code for this look like?
  3. @Samuel Molina most people here would absolutely love to help newcomers to the language, but few will actually do your homework for you. What have you tried so far? What are you trying to accomplish? I took a look at your VI but it does not really give any insight into what you are trying to do.
  4. WOW... I have not thought about Tucows in a veeeery long time. Good times 🙂
  5. @ShaunR and @dadreamer (and @Rolf Kalbermatter) how do you know so much about low level Windows stuff? Please never leave our commuity, you are not replaceable!
  6. Can you post your code?
  7. Yup, I was going to use those (no-ip if I recall correctly) but then we needed to introduce a PC and so my problem kinda went away.
  8. OK, this is what I remember. Hardware was something like this: cRIO Ethernet switch Industrial modem (Teltonika something... you put a SIM in and connect the ethernet to the switch) Security I just had to kinda figure out. I think I got it working in the end, check out this thread: The big question mark for me was how I was going to manage the cRIO remotely as my LTE connection could not guarantee a fixed IP address, so I had no simple way to connect to the cRIO after it had been deployed in the field. Finally we decided that we would actually need a PC anyway for something else, and the cRIO would be connected to that. The plan was to remote desktop into the PC and then connect to the cRIO that way, or get the dynamic IP address of the cRIO. Or maybe the idea was to the cRIO to broadcast somewhere its IP address. The project was put on ice and never deployed to the field, so I was not able to test these assumptions. People do get stuff like this to work, so I am sure somebody had a solution for these problems. Hope this helps!
  9. Sure, I will try and remember and type up something tomorrow. Before you get your hopes too high, I got things working ok with Azure IoT hub and Power BI, but it was never productionised.
  10. In the top picture your S11/S12 is an array, which gets auto-indexed in the for loop (the little square thing at the border) which essentially iterates over the elements which allows you to read the items individually. In the bottom picture your S12/S12 is part of a cluster (think struct in other languages). You cannot iterate over this like you do in the for loop.
  11. Thanks, I did not know about this. I am not sure I will ever use it, but I like to know such a feature exists (or not). Reading that thread, I am not 100% in agreement with the comments that moving to class solves everything. Not everything needs to be a class, sometimes a plain old cluster is really ok. Even for biggish clusters. Anyway, completely separate discussion 🙂
  12. Thanks for sharing @David Boyd How did you do this?
  13. I exclusively use the bundle/unbundle, unless I am not able to for example if accessing a field in a parent class. Accessors should be, in my opinion, only for when you want to get access to the data from outside the class, and even then you should really think about if this is strictly necessary. Often you can get rid of accessors by having a better designed API (methods). Lots of sets/gets is a code smell to me.
  14. Urgh, that is not good. That Express VI is one of the few I use every now and then to quickly get some DAQmx code up and running.
  15. So according to the link it seems it does work as long as you have 2021 installed, right?
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.