View single post by Pgordon | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Posted: Tuesday Jul 28th, 2020 06:48 pm |
|
||||||||||||
Pgordon
|
Hey all... I just had an anomolus event... I made several changes and I didn't have any problems until right at the end when I tried to transfer a new program to the panel.today I: - Added a RIO module, ID=1 (it's an old board that I brought back into service) - Scanned for modules in comfigurator, it found it & established comms - Upgraded the firmware on a couple of UCM's - Eth, and GSM- Added a test response in SCS/RIO response 129 (On response - say a phrase) - incremented the clock drift tuning setting from 0 to +1 as my clock has been running a bit slow- because I'd changed a response I then tried to transfer the file to the panel That's when my issue started... the transfer begun, and almost immediately the panel went mad; sirens blaring, keypads showing intruder alert, it armed to night mode. whilst this was going on, I was constantly trying to stop arming by signing in on the keypad, but whenever I stopped a full alarm, it started again after a few seconds. This continued for the entire duration of the upload - which did complete after the normal amount of time. and once the transfer was complete, and the panel reset, everything went back to normal. I've not repeated a transfer again, since that behavior scared the cat sh**less, and really rather annoyed the family. I'll perform another upload when I get a chance to see if this was a one-off, or if this occurs again. Any idea why it would behave like that? - could I have overtaxed the PSU in the main panel with the added module? - would that even cause behaviour like this?... any other thoughts? TIA Paul G. Last edited on Wednesday Jul 29th, 2020 05:41 am by |
||||||||||||
|