Remote scenes issue

Strange thing happening on our intallation. Occasiony Trigger Application refuse to work, though Lighting application works well.
We have 2 C-Touch screens installed, master and slave, with identical programms, several NEO, one of them is wireless, to controll remote scenes stored in C-Touch. But sometimes they refuse to work, scenes toggle only from slave C-Touch, but not from anywhere else (even computer). C-Bus Toolkit Application log on wired side shows no Trigger application activity when we try to toggle scenes, though in wireless network they toggle. It can last for seweral hours and then everything works fine again.
We can see no actual reasons for such behaviour. It can happen when the installation is closed and there is noone left. And we weren't able to reproduce this situation, it occurs by itself.
Have someone encoutered something like that? Or have any suggestions on this matter?

Valery R.

 

Run the C-Bus Diagnostic software while this problem is occurring. In particular, look at the traffic analyser graph. You may find that you are getting communications errors.

 

We used C-Bus Diagnostic and haven't found any errors.
If it is becouse of communications errors, then why this problem may disappear and reappear after some time? And why only Trigger control malfunctions, while Lighting application works well at the same time?

Valery R.

 

just a few things to look at before people can help:

How do you remote trigger the scenes: what functions do you use in Switch? What trigger address and action selectors for the scene? Did you store the scene at one C-Tocuh or Two C-Touch?)

How many group Address inside one scene. (Sometime 50+ commands in a scene will "jam" the c-Bus network. Especially if you have two C-Touch storing the same scene.)

Since you see no activity at the trigger address level, it should be mainly programming issues rather than jamming.

 

Did you look to see if there were errors while this problem was occurring, or was it at some other time ? You haven't said whether you could see the trigger message on C-Bus when this problem was occurring.

It is possible that there is electrical interference which changes from time to time. The network could also get very busy at certain times.

It would be unlikely for just the Trigger Control application to be affected by communication problems. However, the most common cause of this type of problem is communications problems, so it should be investigated first.