Hello,

again pls, look to my previous post, what Smiffy have sugested to you also I have expect before with that $01, therefore I've ask you for original documentation. Without to see original documentation we can play only on sand together without proper result. In original documentation is also important info what bytes length is request, of course due respective request.

smiffy

Just a guess, but maybe the <CR> are not actually meant to interpreted literally? Could it be that Hypreterminal uses the <XX> to mark a special control character (in this case carriage return or ASCII code 13)? So <CR> is not sent as 3c 40 52 3e but actually sent as 13.
You could verify this by actually monitoring what is send by using a telegram trace.

But a quick test could be to try this sequence (replacing <CR> (3c 40 52 3e) with ASCII 13).

24 30 31 50 31 13

Nice Shot!

Please check again is it "24 30 31 50 31 13" or "24 30 31 50 31 D"?

Hello,

in case that mentioned <CR> must be control byte (as is in most cases in communication Solutions), it must be 16#D. But look again to all posts here, I still recommend for proper solution to see exact documentation with messages format. Simply I can't believe to user who is new to this Solutions.

Hi

Thanks for all the advice. I think i'm getting nearer a solution thanks to all of you. UnfortunatelyI'm getting alot of signal reflection when i send commands despite soldering a resistor @ 130 Ohm on both ends of the wires. I have to figure that out before I can say for sure it works

The "Carriage Return (CR)" is definitely a single byte control character however if can just input that as the last character in the array of bytes i'm sending from remains unsure.

Sorry, Duris. I'm not ignoring you. I just  don't fully understand what you mean.

Here a link to my program if it helps. And again, thanks. Have look at the datablock called S_Send to messege formats.

Hello,

ok, simply if I can say again, I want help you but simply attach that documentation here, where is all communication to sensor described. If you don't want to share that documentation or link to it, give us right info. Then you can investigate for your own, also post questions to next your problems, but I'll cancel my support in that case, sry.

Duris_I

Hello,

ok, simply if I can say again, I want help you but simply attach that documentation here, where is all communication to sensor described. If you don't want to share that documentation or link to it, give us right info. Then you can investigate for your own, also post questions to next your problems, but I'll cancel my support in that case, sry.

 Ok. The documentation on my desk next to me i'll try to scan the most relevant pages and attach them here

Update: Here it is attached