GPIB to RS-232 Transition

[Pa1_korea]

Sorry.. i forgot to attach my VI.

Here it is.

[Pa1_korea]

Sorry..Forgot to post the VI.. Here it is

[GerdW]

Hi Pa1,

can you answer the questions from my last post?

Especially the question on TermChars?

Does your device wait for a special TermChar when receiving commands over RS232? What is mentioned in your manual on this topic? RTFM…

Using BytesAtPort is also wrong here! How many bytes do you expect in the receive buffer immediatly after sending a command? Either use the TermChar described in your manual or request the exact number of bytes in the expected message!

[Pa1_korea]

Here are the answers.

1) The coonections are perfect.

2) I have sent only the *IDN?\n command

3) What is TermChars?..Is it terminal characters. I have tried it with \n and without it..but the result is same

4) VI is attached?

[GerdW]

Hi Pa,

2) I have sent only the *IDN?\n command

No, you don't!

There is no NL char (\n, new line) in your command!

[Pa1_korea]

Hii..GerdW...

The result is the same even if the \n is added. 

[GerdW]

Hi Pa,

there is a difference between the NL char and your "\n" chars!

You wrote two chars: "\" followed by "n".

Your device expects a NL char, written in \-code-display as "\n" or in hex-code-display as 0A!

[Pa1_korea]

Thanks GerdW...

Are RS232 and GPIB command format the same?

[GerdW]

Hi Pa,

Are RS232 and GPIB command format the same?

As has been mentioned several times before: Read the manual of your device! RTFM…

(Most often the commands are the same. But as I already mentioned above the termchar may change.)

[RTSLVU]

You are not configuring your serial port!

Try something like this: