Re: C-Bus via CNI

If you are just sending a string value, then perhaps your command
value should be:
\053800790AC2g0D\x0D
or
\053800790AC2g0D\x0D\x0A

The hex byte on the end is to simulate you pressing the "enter" key in
telnet.

Not sure what the leading backslash is for either - so maybe try with
and without that.

Jarrod

On Feb 19, 8:25 pm, Watch <michael.carr...@optusnet.com.au> wrote:
> When using Telnet I just send
> \053800790AC2g0D
>
> . . . and it works fine.
>
> As for the checksum value - it's a typo on my part in the
> explanation.  For the 'on' command of '79' it's 'C2', for the 'off'
> command of '01' it's 'B8' (based on the application address of '38'
> and the relay address of '0A').
>
> On Feb 19, 7:48 pm, Jarrod Bell <jar...@guilink.com> wrote:
>
>
>
> > How are you sending each hex byte in telnet? Perhaps its not hex
> > afterall, but a string representation of it.
>
> > Also, your first post mentions a checksum value which is different to
> > the value you mention in the actual command. Are you sure the checksum
> > value is entered correctly into the actual command itself?
>
> > Jarrod
>
> > On Feb 19, 7:38 pm, Watch <michael.carr...@optusnet.com.au> wrote:
>
> > > Yes - 'maintain constant connection' is selected.
>
> > > The 'g' is just an acknowledgement character (I shouldn't have used a
> > > 'c' in my earlier attempt).
>
> > > To quote the C-Bus documentation;
>
> > > Each command sent is acknowledged.  To allow decoupling of receive and
> > > transmit processing, the the PCI provides a simple means of tagging a
> > > command.  At the end of each command sent, and just before the <cr>,
> > > place any single lower place alphabetic character, in the range 'g' to
> > > 'z'.  The PCI will acknowledge the command by returning the lower case
> > > letter used, followed by a confirmation character;
> > > .  = positive acknowledgement
> > > # = too many tries
> > > $ = corruption
> > > % = loss of C-Bus clock
>
> > > Based on the success of control via Telnet, the IP address and port
> > > are correct.  The protocol is correct for the CNI.  So my problem must
> > > be in the command itself.
>
> > > On Feb 19, 7:08 pm, Jarrod Bell <jar...@guilink.com> wrote:
>
> > > > Hopefully some of the other C-BUS guys jump in and offer some insight.
>
> > > > The connection issue via telnet after using iViewer is interesting. It
> > > > sounds to me like a bug within the CBUS hardware, not detecting
> > > > disconnections correctly.
> > > > But just to make sure, don't have any iViewer device open when you are
> > > > attempting a telnet connection.
>
> > > > As for the EOM characters, they are only related to feedback parsing,
> > > > nothing to do with the actual sending of commands.
> > > > The EOM is only used to split incoming messages if more than one
> > > > message is arriving quickly at once.
> > > > See here for more info:http://www.commandfusion.com/wiki/index.php?title=GuiDesigner:System_...
>
> > > > The only things to check when sending commands is the IP address,
> > > > port, protocol and the actual command value itself. Also make sure
> > > > 'maintain constant connection' is enabled in this case.
>
> > > > Not sure what the 'g' is in the message - I recall you mentioned it
> > > > was 'c' via your emails. Seems to me the formatting isn't quite right
> > > > somewhere in your commands.
> > > > Hopefully one of the CBUS guys using our software can clear this up.
>
> > > > Jarrod
>
> > > > On Feb 19, 6:15 pm, Watch <michael.carr...@optusnet.com.au> wrote:
>
> > > > > Anybody had experience talking to Clipsal C-Bus?
>
> > > > > I have a C-Bus network interface (CNI) and can send a command via
> > > > > Telnet but cannot get Command Manager to turn on a relay by sending
> > > > > the same string to the same address.
>
> > > > > I can Telnet the device via:
> > > > > open 192.168.0.101 10001
>
> > > > > I can turn on a lamp at address 0A using Telnet via the following
> > > > > string:
> > > > > \053800790AC2g0D
>
> > > > > where;
> > > > > 05 = header indicating point to multipoint, low priority
> > > > > 38 = lighting application address
> > > > > 00 = not used
> > > > > 79 = on command (01 = off)
> > > > > 0A = light group address
> > > > > B8 = checksum = 2's complement of the modulo 256 sum
> > > > > g = confirmation - character to be returned
> > > > > 0D = return or <cr>
>
> > > > > Jarrod ponted out that I should prefix data with \x to declare a hex
> > > > > byte as follows but this didn't work either.
>
> > > > > \x05\x38\x00\x79\x0A\xC2g\x0D
>
> > > > > I've tried changing the EOM field and the connection join field
> > > > > without success.
>
> > > > > Also, after attempting this with Command Fusion, I can't go back and
> > > > > Telnet the port.  It appears that I need to reset all the harware.- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -

--
You received this message because you are subscribed to the Google Groups "CommandFusion" group.
To post to this group, send email to commandfusion@googlegroups.com.
To unsubscribe from this group, send email to commandfusion+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.