From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
07-08-2013 08:18 AM
07-08-2013 10:03 AM
I tried with a simple write and read and also different form of writing but still there is the sam error.
07-08-2013 10:58 AM
07-08-2013 11:02 AM
Time to break out hyperterminal and see if you can send commands that way.
07-08-2013 11:06 AM
07-09-2013 04:05 AM
It seems the problem is with cable as I checked with hyperterminal and shows error. I will check with another cable...
07-09-2013 08:53 AM - edited 07-09-2013 08:55 AM
07-09-2013 09:01 AM - edited 07-09-2013 09:02 AM
@sam009 wrote:
It seems the problem is with cable as I checked with hyperterminal and shows error. I will check with another cable...
What was the error? A cable issue would be about in the middle of the list of things I would check at this point. If you are absolutely certain that the comm settings are appropriate, then the next thing I would suspect is command syntax. In fact, I just read the manual now. Look at table right above section 10.2.2. Admittedly, it is a crappy chart - I've never seen a hex number notated with a capital "H" before - but it is telling you that a CR = 0D wich is an ASCII carriage return. That doesn't mean that you send the string "0D" with your command instead of the (CR). Check out this link to see how to implement this.
07-10-2013 05:02 AM
Thanks all of you,
your comments were very useful I could solve the problem by all your help. I changed the cable and little bit change in the command code. (CR) replaced by \r . Now program is running.