Emi Or Software Errors?

I am programming a project. There is something wrong I can't understand. Please help me.
There are 3 networks, each has >10 Relays, 1 C-Touch(BW), 1 PC Interface and 1 Schedule Plus(3.7 updated from 3.0),all stand alone.
In C-Touch ande Schedule, scenes' ramp rate is 2 minute, using relays' 'turn on' option lamps with turn on one by one.
When cotrolled by C-Touch, everything is OK. When Schedule Plus is online, the scenes executed correctly. But in the end C-Gate returned reports like this:
# lighting syncupdate //wangqiu/100/56/51 level=115 #sourceunit=-1 OID=...
...
Then loads will turn to the levels according to the reports.
This often occurs on different units, different Group Addresses and resluts in different light levels.
On/off control with Schedule Plus is OK.
All of the 3 networks are all the same situation.
Any one can tell me what happened?
Thanks a lot!

 

It should be programming error, shouldn't it? Is the picture ": created and used by you? If you are doing the project for Olympic Tennis Stadium in China, and these pictures are used in other parts of the program, you may look at all the schedule...etc. Since the picture is in F drive and under your (XXJ) directory, I guess it should be one of your picture that is used by another line of schedule.

If you are not doing that project, or even if you don't know Chinese, then your program or computer must be used by someone else and you better re-program the whole thing from a blank project and probably need to look at the computer that runs Schedule Plus....

 

Thanks for your reply.
The path in Chinese is just a picture I want to paste in the thread,but failed. So I edited it.
In fact there is no picture in the initial Schedule Plus Project, only buttons.
I am doing that project.
I solved the problem with logic, still troublesome, setting scenes in C-Touch reports mistakes every time when Schedule Plus is online.

 

The picture and scene must be called up by either schedule or logic programs running with Schedule Plus. You have to look at your logic, schedule and even the scene contains. The suspect should be logic since it is random and you can solve it by logic. I am not a good programmer, so you may post up what you did for other programmers to look at them. But since you can solve it, you may simply clean up your logic programs but removing all unused lines/modules and see if it still happens without your solution running. Most importantly, get rid of all quotes in Chinese even if it is path names. Clipsal software should be run under English to avoid unexpected errors.

Another possible cause may be the trigger address. If you are using "lighting Application" for trigger address, there is a chance that your scene is triggering another scene......

How many groups are stored in one scene? Sometime it may jam the bus and C-Bus would return to previous setting and probably get stalled. In this case, it should happen using C-touch as well. However, there is a chance that C-Touch issue a bunch of commands and other device generate a duplicate set on their own when all things are triggered....look at the log and see how things going may help.

By the way, I am just talking with the limited knowledge I have. I don't know what generate "# lighting syncupdate ..." so you need more reply from others....

 

In the initial project files, there is no picture,no schedle,no logic.There is only simple scenes(for example:group 1-100 all 100%, 2min ramp rate.group 1-100 all 0%, 1min ramp rate.) and sigle group control buttons.
All trigger groups are in "trigger control application", and used in C-Touch of one network.
I solve it with logic is because of that logic just concern 'on/off' control, and 'on/off' control always works well. The logic is simple too, 'timer+on/off'.
I can't find any clew about "# lighting syncupdate ..." in help files, CGateServerGuide and "C:\Clipsal\C-Gate2\config\C-GateConfig.txt". So I have no idea about it.

 

I tried sevral methods you mentioned, small scenes(1 trigger group starts timmer,then set 3*30+ groups scenes at proper time),non Chinese(Project/network Name, Gruop name...),but it didn't work.

 

you cannot run 50+ dimming commands in one scene. Break them up into two to three scenes, trigger them with at least 0.5 or even 1 second break in-between. C-Bus cannot cope with too much commands at the same time. Dimming commands is longer than ON/OFF. Try to open a log and see if all your scene commands can pass out.....If it fails, C-bus may try to call back previous states. I don't know much details but when it happened to me, I get around it by breaking up the scenes. I was using a PAC controller and trigger the scenes using a small logic program.

 

"40 commands per second, more commands will be queued", I saw it in help files. In one of the C-Touch,every scene contains 124 groups and is composed of two parts, part1 has 100 groups, part2 has the other 24 groups, the scene is triggered by a trigger group. The other 2 C-Touch's scenes all contain 96 or 100 groups. No problem.

 

We should pay attention to this: when Schdule Plus is offline, big scenes with long ramp rate in C-Touch works well. Once Schdule Plus is online mistake will occur.

 

It is nice to know, but for some reason it didn't work (no queueing) for me last time. It was probably due to older firmware, PICED version etc. So it all depends on what version of software or firmware you are using. Last night I worked till mid-night to try to work things around because I got some switches and multi-sensor with different firmware version in a recent shipment. They just behave totally differently and it is killing me that I couldn't work on second application with some of the units. (I couldn't find a proper solution yet...)...so, may be look at the software version, or check if the scene contains are sent out twice when Schedule Plus is running...

 

xxj, you have found a problem with Schedule Plus.

If a SyncUpdate message is received from C-Gate while a ramp is in progress, the group gets set to the new level and the ramp stops.

This has just been fixed for the upcoming release.