PUSH Contols is not getting feedback from C-Bus property, is slow or not at all?
Note: These recommendations or suggestions below are assuming you are familiar with programming PUSH Controls, have the Project Editor Software & have the original project file (.bwe).
I. RS232 preferable
Symptom: slow feedback or control
During our testing when developing the C-Bus module, the performance of the C-Bus module is much better when using C-Bus 5500PC (RS232) compared to C-Bus 5500CN (TCP).
IMPORTANT: when changing communication method between RS232 and TCP, make sure to re-upload the project programming
both to the Push controller and Push app (iOS or Android). Otherwise your site (or part of it) will still be using the old communication method.
II. Double Check your RS232 Cabling
Symptom: from Push app you can control C-Bus lighting but no feedback update (ie. when you physically press a C-Bus switch, the Push app doesn’t update) or vice versa
Check the RS232 cabling, a one-way communication could indicate that there is issue with either the RX or TX side of the cabling.
III. Local Network & Lighting Application Only
Symptom: unable to control or receive feedback, except for C-Bus groups on local network and lighting application
The C-Bus module only support a single network, which is the local network. In regard to feedback, only feedback for C-Bus group with application address of 56 (lighting) will be displayed.
IV. Check Feedback State Id
Symptom: no feedback on sliders however toggle buttons receives feedback (showing latest state); or vice versa
The Feedback State Id is different between a slider and a toggle button. The reason is because a slider displays a value between 0 – 255 but toggle button displays either 0 or 1 (on or off).
Slider
Format: PUSH_CBus_
LevelApplicationAddress_GroupAddress. See sample below for a slider which is programmed for C-Bus group 0/56/32.
Toggle Button
The Feedback State Id for a toggle button is available as a selection from the combo box. See below for a toggle button which is programmed for C-Bus group 0/56/32.
V. No Feedback on non-native C-Bus groups
Symptom: no feedback on C-Bus groups which control non-native C-Bus devices. For example: DALI.
This is due to the behaviour of MMI’s within C-Bus, a non-native C-Bus devices (such as DALI gateway) is not considered an output unit, therefore does not partake in in the MMI process when a switch supporting the application initiates it. Because of this, this means that the feedback of a DALI group address has to be monitored by an output unit which has the particular group addresses programmed into it from that application.
If there are any relays or dimmers on the same application as the DALI gateway, then it is best to load the channels and logic channels with these group addresses, the problem resolves itself at this stage as the group address is programmed into an output unit which partakes in the MMI process.
It is also important that there is a switch on the network which is set up for this application, as with this, no MMI process will begin.
Cheapest option is to use the ELV relay, which will allow us to store 8 group addresses on the channels, plus an additional 4 group addresses into the logic channels.
VI. Remove legacy C-Bus script from your GUI project
Symptom: no feedback on the Push app (ie. when you physically press a C-Bus switch, the Push app doesn’t update)
Legacy C-Bus module (version 3.1 or older) uses a separate script which is located in your GUI project, make sure you delete this when using C-Bus module version 3.2 or above.
