| PM | Quote | Reply | Full Topic |
| Joined: | Sunday Jan 21st, 2007 |
| Location: | South Africa |
| Posts: | 562 |
| Status: |
Offline
|
I feel your pain, it's frustrating as hell, I know, but it's no joke.
To put it simply, the RS485 corruption was probably the most logical cause of the problem with the data you supplied previously. As you now provided more extensive data it points to perhaps a different cause but still doesn't rule out possible bus issues.
I never had issues like this and can only speculate but I would go to the second suggestion made in the previous post and remove all keypads except one, probably leave the closest one to Comfort and see what happens.
In the absence of evidence pointing to a specific problem I would turn this all around and say remove all external devices and add them back one by one. If you can manage once device per day I am sure you might find the culprit within a few days. But yes, if the bus has a problem it would manifest in the other connected devices as well.
Attach your capture so we can have a look and give us times/dates when particular things happened so we can try and figure out what actually happens on the inside.
Just to comment on the Bus Monitor, yes the code is sometimes a bit 'flakey' and Cytech is probably going to flame me for saying this but it does work. When I have Bus Monitor running for a long while it sortoff slows down meaning data on the bus is captured up to a minute later after the action. Also, when you quit Bus Monitor it doesn't always exit on the UCM side. With this I mean a code is sent to the UCM to activate/deactivate the packet capture mode and sometimes it doesn't exit that mode. In a case like that you just reset the UCM. I normally use my UCM/USB for captures and UCM/Eth for control, or is that vice-versa, anyway you get the message.
Ingo
| Close Window |