I'm trying to read six input registers from a remote device but the software I put together doesn't seem to do much; no errors but no read-backs either. I'm a beginner, so the answer is probably simple. The remote device input registers start at 200 hex. The device uses TCP and the IP address is correct. My computer communicates well with the remote device through QmodMaster. Any help you could give would be appreciated. Thanks, Mike.
Modbus Read 01.pdf So far 01.vi
Does any one have an idea on how to password encrypt an Excel file (or csv) in LabVIEW or zip up the excel file/csv and add a password to it that way? I need to be able to add a simple encryption to confidential patient data files after they are created and be able open them to read later by the same program. I've tried using OpenG to add a password protection to a Zip file but when I try to add a string variable to the password connector it says password (none) so it makes me feel like I'm doing this wrong. I couldn't really find any similar documentation or tutorials on creating a csv or excel file then zipping up the file and adding a password to the zip with OpenG though I read about the function on the Labview forums. A few other things over I've tried recently: I think a solution would be to use some sort of property/ invoke node with ActiveX like I've attempted to do in the picture below but I can't find anything that explains exactly how property and invoke nodes work with ActiveX to achieve what I wanted, and I was hoping someone would have a tutorial that a LabVIEW beginner like me could use. Something else that I looked at was adding a "blowfish" encryption to encrypt the data but seemed extremely complicated and all I need is a simple password encryption. Finally I tried using an add on called AES crypto but I felt that the encryption methods that were featured in the add on were limiting. For patient names they would be at different lengths and in the example programs it showed that if a string was shorter than 128 bits then it would't be able to encrypt the string. Which is an issue if the patient has even a regular length name. If you have any thoughts or find anything useful let me know. Thanks, From a beginner usmanf
By Igor Titov
During a few last years I received multiple appeals to release AES library that I developed in 2011 into open-source. So, I've just done exactly this: https://github.com/IgorTitov/LabVIEW-Advanced-Encryption-Standard
I released it under MIT license (which means that there are no restrictions whatsoever). No VI passwords, no uglification.
Firstly I am very new to labview so i apologise in advance if i ask some stupid questions.
i am running a vi on my rio ( simple analog in/out express vi s) and another vi on my PC. i am communicating between them through shared variable and it works perfectly, only thing is i have to manually run both vi s.
my question is, is there a simple way to start the vi on myrio from the vi on my PC?
PS:- i tried to work with vi server but i failed because of my limited knowledge.
any help will be much aprreciated.
Thanks & Regards,
I have RIO in a Windows VirtualBox inside a Ubunbtu Host OS.
I am sending data from a C++ program in the Ubuntu Host system to labview within the Guest OS.
I can receive the data on labview installed on the windows guest os. Below is the png of the Windows working program.
But when I tried to send the data to myRIO, I was getting a udp read only error 42.
Somewhere on the NI forums, someone suggested the net address of the "UDP Multicast Read-Only" vi be wired to the address of the RIO which I have done below
Now, the code runs on myRIO but I can't receive any data on RIO. The multicast address I am sending to from Boost Asio C++ is 126.96.36.199 on port 30001.
The RIO has a public ip of 172.22.11.2 and I set up a static ip address for it in NI MAX as the address of the UDP Multicast : "188.8.131.52.
At this moment, I do not see what I am missing. All firewalls have been disabled and I have set the permissions for RIO through the Windows security page.
Any help would be appreciated.