Another feedback question

OK, I'm sure this has been covered, but I've read a lot of threads, as well as the protocol documentation, and I'm still a little bit fuzzy. My main questions are in regards to properly initializing the RS232 interface.
My desired end result would be to have the system respond to my level status requests when my program launches, to initially populate levels. This is working now.
Then, when a level is changed by any source (keypad, or the RS232 port) I'd like to have that be reported as well, so that other instances can see the updated levels. That is the part I'm having trouble getting to work properly.
I am trying to avoid constantly polling with level status requests due to the amount of traffic it creates.
Any info would be greatly appreciated.

 

Whenever a C-Bus unit sends a message to turn something on, change the level, etc, you should see the message it sends on the serial port. You will most likely already be receiving these messages (depending upon PCI mode). If you're using the C-Bus module, these will be decoded for you.

There are very few cases in C-Bus when polling is required.

 

Thanks for replying. I do see messages when a keypad changes a light level. I do not see changes when the level change was initiated by a device connected to a serial port. Basically, I will have multiple RS232 devices. When one makes a change to the network, I was hoping for some kind of broadcast update to let the others know.

 

OK, your initial post seemed to indicate that you weren't seeing these messages from any devices, which is a different thing. The messages are being sent, but they're not being sent in a format that your current PCI mode is decoding for you.

You will need to turn on the Local SAL option in the interfaces that you are using to send messages on to C-Bus. This option needs to be set when you initialise the PCI.

If you look in the Serial Interface Users Guide you will see this option explained in Section 4.2.9. There's some further info in section 10.3.6.

 

Thanks guys. I actually did read the serial protocol guide before posting, which is how I got as far as I have. Clearly I missed something, or didn't properly implement what I read.
I'll tackle it again, thanks.

 

So, after trying this again, I cannot make the CNI report level changes initiated via the RS232 port.
I see the MMIs coming in every 3 seconds. If I press a button on a keypad, I see the monitored SAL on the serial interface. But no matter how I initialize the CNI, I cannot see a monitored SAL come back for a command sent into the serial interface, which is my main hurdle.
I have tested this by creating my own commands, using the diagnostic utility, etc.

Let's say I press a button on my keypad. I see the following message come through the serial port:
05023800790048<CR>

Now I want to perform the exact same function via my device attached to the serial port, so I send in:
\05380079004A<CR>

But alas, I cannot see a return. The client device connected to the serial port has multiple other devices connected to it, sharing that serial port. So if one of those secondary clients initiates a level change, I want the others to be able to see that change through a SAL on the shared rs232 interface. I suppose I am still missing something, but I have been playing with those interface options for a while now and cannot get the desired behavior.

 

You have described your set-up slightly differently this time.

It sounds like you have multiple devices sharing a single serial (RS232) port through a "client" (which I assume multiplexes the messages). You haven't stated what this serial port does, but I assume it is connected to a PCI. If this is not correct, maybe draw a diagram for us.

When you send a command to C-Bus you don't get an echo of that command from the PCI if you have SMART mode set. You could initialise your PCI to not use SMART mode (see Serial Interface User Guide), but this changes the format of received messages as well.

This sounds like the problem previously diagnosed as requiring Local SAL to be set. You haven't said if you have done that.

If you still have problems, I would suggest posting a block diagram of your system so that we can get a clear picture. I am not sure if we are correctly understanding your questions at the moment.

 

Yes, I have set Local SAL on (and off, along with any combination of initialization options I can think of) and had it set before I made my first post.

The simplest way to describe it is this:
I am not looking for a local echo.
If I send the PCI a message to control a lighting load, I want all PCIs on the network (including the one the message was sent into) to respond with the SAL message, EXACTLY as if the command originated from a keypad.