Jump to content
Dataton Forum
Tim M

Light control Command

Recommended Posts

Hi everyone!

I've got some troubles with control commands.

We 've got Butler xt2 & commands for turning the light on and off.

TCP Port 50000

UDP Port 50001

 

Commands are:

On:

\62V:1,C:11,G:9,B:1,S:1,F:500\35

 

Off:

\62V:1,C:11,G:9,B:1,S:15,F:500\35

 

There are no message errors, but we' ve got no effect too.

How can I change commands to make them correct in Watchout?

Tried to change TPC/UDP, to add $0A & $0D - no effect.

 

From D3 server these commands are working.

Share this post


Link to post
Share on other sites

If things don't work from the start, I would always use a Telnet software, e.g. Putty, to analyze the problem. If I'm lucky, the system I want to control sends some answers to my command which can help to analyze communication problems.

Share this post


Link to post
Share on other sites

I haven't used either the D3 or the Butlers, but if I had to guess, I would say the first and last bits are encoded decimal values.  

Try changing this:

\62V:1,C:11,G:9,B:1,S:1,F:500\35 

 

To this:

>V:1,C:11,G:9,B:1,S:1,F:500#

 

--D 

Share this post


Link to post
Share on other sites

Many, many thanks!

It's works!

 

I haven't used either the D3 or the Butlers, but if I had to guess, I would say the first and last bits are encoded decimal values.  

 

Try changing this:

\62V:1,C:11,G:9,B:1,S:1,F:500\35 

 

To this:

>V:1,C:11,G:9,B:1,S:1,F:500#

 

--D 

Share this post


Link to post
Share on other sites

FYI the use of the backslash to designate a hex value is invalid in WATCHOUT string commands.

WATCHOUT uses a dollar sign instead of the backslash.

 

So, if 

>V:1,C:11,G:9,B:1,S:1,F:500#

works, then 

$62V:1,C:11,G:9,B:1,S:1,F:500$35

will also work.

Share this post


Link to post
Share on other sites

Actually, in this case, the backslash indicates a decimal value, not hex...  it's decimal 62 (Hex 3E), so $62V:1,C:11,G:9,B:1,S:1,F:500$35 would not work.  I suspect that ">" and "#" are reserved characters in the D3, which is why they're encoded as decimal.

 

--D

Share this post


Link to post
Share on other sites

Thanks for the clarification.

But if that is the case - decimal 62 and the > symbol would transmit exactly the same over the communication channel,

there is no difference once it is transmitted. The two methods very in data entry, they are the same in transmission.

 

So that just confuses me more iono.gif

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...