ascii data from my serial port does not represent the data I am really receiving

[Mastergrammer]

I created a program that sends data to a serial port and then recives new data. I send and recive data as ascii charicters however some of the ascii charicters I am reciving are not what they seem, my serial port monitor tells me that " “.... " equals " 93 00 00 00 1c " in hex. (it also says " 93 00 00 00 1d" is the same) how do i convice my serial reader vi to give me realevant data?

 

[TCPlomp]

It looks like you use the old* Serial drivers. I suggest you move to the VISA system.

Is the Dumpview your program? Your diagram diagram does not show a write function or 'equals' function so I don't know how I can help you.

Ton

PS as in really old and might be obsolete once.

[Mastergrammer]

Im using lab view 6.1, I tried to use VISA but I cant find the COM3 port I'm using. No drop down menu appears when i place a VISA Resource Name control.

The dump view is from a serial port monitoring program (not labVIEW) and shows the output of my program as well as the responce from the divice I am sending info to.

Here are some examples of the problems I encounter.

[smercurio_fc]

Did you install NI-VISA?

[Ben]

I think that version of LV needed an entry in "Visaconf.ini" for it to show in the drop down list.

Is the number of bits set right?

Ben

[TCPlomp]

So is the issue that LabVIEW is not reading the 1D and 1C, or is not writing them?

Note that 1D and 1C are field/file seperators

Ton

[Mastergrammer]

The issue is, Labview receives “.... which I cannot do anything useful with. At some point my computer receives 93 00 00 00 1c from COM3 but I do not have access to that info through labview for some reason

[Ben]

Try right-clciking on your indicator anc choose "slash codes" or "Hex".

Ben

[LV_Pro]

Where are you seeing the "....   ? That is what your dump program is displaying, and if you have the output of your serial read connected to a string indicator it may well show that as well, as the returned "numbers" (actually bytes) aren't displayable characters. If you do have a string indicator showing the returned data, have you "right clicked" on it and selected "hex display"?

I see Ben typed faster that I did!

Message Edited by LV_Pro on 06-11-2010 02:53 PM

[Ben]

---

LV_Pro wrote:

...

I see Ben typed faster that I did!

Message Edited by LV_Pro on 06-11-2010 02:53 PM

---

Kudos to you Putnam for confirming my post before you saw it.

Ben