LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Getting a parity error coming from VISA Read

NewMachine wrote:

> hello - i can't find "serial read" or "write". is this an example vi
> or something? thanks!

That are the old serial functions. They are only provided as
compatibility functions in LabVIEW 7, are not in the function palette as
they are in fact in LabVIEW 7 accessing VISA inside of them to, so using
VISA directly is more efficient and simpler in the long run.

As to your problem, I think your instrument my expect a certain command
termination such as carriage return and/or line feed. When you hit the
return key in HyperTerminal to send of the command, the program in fact
adds a carriage return and/or line feed to the end of the string it
sends out.

Some instruments sit there and wait for this terminati
on character
before they will even attempt to decode the command and send you an
answer back.

Make the string control or constant you use to define the command to
send to the instrument, to "'\' Codes Display" from the context menu,
then append '\r' and/or '\n' without the quotes to the end of that string.

Rolf Kalbermatter
Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 11 of 25
(1,932 Views)
good to know, thanks....
0 Kudos
Message 12 of 25
(1,745 Views)
I seem to be getting the same error that NewMachine is getting. I also don't get the temperature reading properly. I am using an Omega MDSi8 controller. I have made quite certain that the settings all match. The parity is odd on both the computer and the device. Why does this happen?
----------------------------------------------------------------------------------------------------------------------------------------------------
I've got a sneaking suspicion that Jesus might have been made of bread. Why else did they have to put him in a warm cave and wait three days for him to rise?

Damnant quadnon intelligunt - They condemn what they do not understand.
0 Kudos
Message 13 of 25
(1,718 Views)
Try running portmon to see if it shows anything strange in the dataflow. Also try to find a demo from the equipment vendor so you can compare two different programs talking to the device.
 
0 Kudos
Message 14 of 25
(1,714 Views)
I tried Portmon and attatched a screenshot of what it sent me. It says the communication is all sucessful, so why do I get the error? I have indeed tried several programs, and all of them give the same error. I have also tried this in Hyperterminal and I get no data returned. I have called Omega and Newport and neither of them know what seems to be the problem.

Thank you,
Cole
----------------------------------------------------------------------------------------------------------------------------------------------------
I've got a sneaking suspicion that Jesus might have been made of bread. Why else did they have to put him in a warm cave and wait three days for him to rise?

Damnant quadnon intelligunt - They condemn what they do not understand.
0 Kudos
Message 15 of 25
(1,706 Views)
Sorry, forgot to put in the one from Hyperterminal too.
----------------------------------------------------------------------------------------------------------------------------------------------------
I've got a sneaking suspicion that Jesus might have been made of bread. Why else did they have to put him in a warm cave and wait three days for him to rise?

Damnant quadnon intelligunt - They condemn what they do not understand.
0 Kudos
Message 16 of 25
(1,704 Views)
It looks like you've got Xon/Xoff flow control turned on. The manual doesn't mention this (that I could see). Try it with no flow control.
0 Kudos
Message 17 of 25
(1,693 Views)
Right, sorry about that. I forgot it then but I have tried it before with no flow control and the same thing happens. I will run it again for you with none and post the Labview screenshot. It should be attached to this post. I find it odd that the XonLimit and XoffLimit are both 64, though I have the port set to no flow control. I don't know what those mean, but they seem related to flow control. Is this an issue?


Found a new thing as well. Sometimes, seemingly randomly, I will get a ?43 error from the device, but then the next time I run it I get the parity error a few times, then the ?43 again. The ?43 error has to do with commands not being entered properly, though I am certain that this command is right. i have called Omega and Newport to confirm it even. This doesn't make sense to me.

Message Edited by JohnGalt on 01-31-2006 12:57 PM

Message Edited by JohnGalt on 01-31-2006 12:57 PM

----------------------------------------------------------------------------------------------------------------------------------------------------
I've got a sneaking suspicion that Jesus might have been made of bread. Why else did they have to put him in a warm cave and wait three days for him to rise?

Damnant quadnon intelligunt - They condemn what they do not understand.
0 Kudos
Message 18 of 25
(1,691 Views)
I have also managed to aquire the screenshot of Portmon when the ?43 error occurs. I don't know if it will help, but it can't hurt.
----------------------------------------------------------------------------------------------------------------------------------------------------
I've got a sneaking suspicion that Jesus might have been made of bread. Why else did they have to put him in a warm cave and wait three days for him to rise?

Damnant quadnon intelligunt - They condemn what they do not understand.
0 Kudos
Message 19 of 25
(1,683 Views)

Can you post your code in 7.0 format?? Are you talking ASCII format or modbus format to the MDSI8??

http://www.omega.com/manuals/manualpdf/M3397.pdf

0 Kudos
Message 20 of 25
(1,668 Views)