LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

my VISA READ isn't reading

I'm not quite sure this will work but its worth a try. Convert hex code into decimal (like 6A = 6*16+10= 106). While in hyperterminal, hold down the ALT key and type 106 on the NUMERICAL keypad (Numlock must be on; do NOT use the row of numbers at the top of the keyboard). Release the ALT key. A special character should appear on the hyperterminal window. It has got to be three digits. If your conversion from hex to decimal comes out with a two digit or even a one digit number (like 1), type in three digits with preceding zeros (like 001). If three digits don't work, try four digits (like 0001).
- tbob

Inventor of the WORM Global
Message 11 of 15
(911 Views)
So we checked with the Codevision AVR program and the board returns to it the correct "AA 55"

But with my VISA read only returns the command I sent, back. Why would I get different things?
0 Kudos
Message 12 of 15
(899 Views)
So we checked with the Codevision AVR program and the board returns to it the correct "AA 55"

But with my VISA read only returns the command I sent, back. Why would I get different things?
0 Kudos
Message 13 of 15
(899 Views)
What does "AA 55" mean? Is this message sent back from your motor right away after the "C7" is received or only after the motor is done moving. If you know exactly how long the returned string "AA 55", instead using "Bytes At Port", wire a constant number to the Read vi and use a wait between the Write and Read to make sure the motor has enough time to respond and send back anything. The code you are using has no problems, but we can use this method to double check. Also have you tried to use Hyperterminal and received "AA 55" back?
Message 14 of 15
(896 Views)
Hello! I used a flat sequence with a wait between the read and write and it is more stable now. AA55 is the "valid commmand" response from the controller
0 Kudos
Message 15 of 15
(873 Views)