03-05-2014 04:41 AM
I have an .exe application that communicates with an instrument. The .exe includes a GUI with a few configuration options, then acts as a data logger once the instrument is running.
I'd like to use LabVIEW to fully automate this instrument as part of an automated (and un-manned) maufacturing process, configuration and datalogging. There is no addtional information available from the vendor.
Does anyone have experience to share on the best approach to this type of task? Attached are data grabs from NISpy and the corresponding data exported from the GUI application. The setup of the serial link is obvious, but I don't see the data. Is "...CTk...." the data in an encoded format? Would Portmon to similar sniffer software provide more information?
03-05-2014 09:56 AM
03-05-2014 10:50 AM
No manual/programmer's guide for this equipment? Maybe it is easier to see the output with Hyperterminal?
03-05-2014 10:52 AM - edited 03-05-2014 11:05 AM
discovered you can change export options to include buffer data. Now using match pattern VIs to strip the data from the txt file with LabVIEW.
03-05-2014 11:04 AM
I don't know about you, but I consider these kinds of projects to be some of the most fun - but they have the potential to be very frustrating at the same time. I'm glad you are working towards a solution.
03-06-2014 01:11 AM - edited 03-06-2014 01:13 AM
seems that the device is simply streaming values
try to run this program
if you can see some data in the read string indicator(s) fine 🙂
hit edit-make current values default and save the vi and repost it if you need help in decoding.
03-06-2014 10:30 AM
thanks for the pointers Bill and Henrik. For anyone who finds this stuff fun, VI attached.........
03-06-2014 10:45 AM
Arrg still with LV2012
03-06-2014 11:04 AM
Have you tried a serial port sniffer like PortMon part of the Sysinternals Suite from MS Technet.
03-06-2014 11:29 AM
I've got the data using NI-Spy, did look at portmon tho. The interesting part now is finding the data, last time I designed a serial link, to avoid having the start byte in my data, I used only a portion of each 8-bytes for data. When you reverse engineer somone else's work, it's hard to know what part of each byte is actual data, then from that what is low-high, msb lsb etc...