PAC with PICED 4.8.0 Power Failure Restore

Discussion in 'C-Touch/HomeGate/SchedulePlus/PICED Software' started by Josh, Feb 17, 2010.

Page 1 of 2
  1. Josh

    Josh

    Joined:
    Aug 25, 2004
    Messages:
    240
    Likes Received:
    0
    Location:
    Pretoria, South Africa
    At about 18H14 we lost power for about an 2 hours and a few minutes. When power was restored (at about 20H30), PAC sent a TIME broadcast of 18H14.

    I noticed that something was wrong when none of my external lights turned on because the logic uses Sunset to switch outside lights on (Sunset for today is 18H20).

    I did not have this issue before and the only change in my setup is the firmware. Could the new firmware be responsible for this?
     
    Josh, Feb 17, 2010
    #1
  2. Josh

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,391
    Likes Received:
    24
    Location:
    Adelaide, South Australia
    Unsure. Investigating. It may also be a hardware fault, but can't know until it can be replicated.
     
    ashleigh, Feb 18, 2010
    #2
  3. Josh

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,420
    Likes Received:
    62
    Location:
    Adelaide
    Hi Josh,

    We are still investigating, but so far we have been unable to replicate the problem.

    In the meantime please let us know if you have any further problems like this.

    You say that the PAC sent the time broadcast - can I ask how you know this? Do you have a log?

    Cheers,

    Nick
     
    NickD, Feb 19, 2010
    #3
  4. Josh

    Josh

    Joined:
    Aug 25, 2004
    Messages:
    240
    Likes Received:
    0
    Location:
    Pretoria, South Africa
    Nick,

    Unit 005 is PAC, unit 127 is Comfort UCM.

    Here is the log .....
    Code:
    DateTime= 17/02/2010 08:24:41 PM    App= 056  Lighting             Group= 201  ComfortInitialiseFlag Unit= 005                       Event= Group off
DateTime= 17/02/2010 08:24:41 PM    App= 056  Lighting             Group= 127  AskComfortForAlarmModeFlag Unit= 005                       Event= Group off
DateTime= 17/02/2010 08:24:41 PM    App= 056  Lighting             Group= 254  PACStatus            Unit= 005                       Event= Group ramped to 250 ( 98%) over 0 seconds
DateTime= 17/02/2010 08:24:44 PM    App= 208  Security             Group= Unknown                   Unit= 005                       Event= Security unknown event
DateTime= 17/02/2010 08:24:45 PM    App= 208  Security             Group= Unknown                   Unit= 127                       Event= Security status report 2: //628RIETV/254/208  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 #sourceunit=127 OID=276fd2b0-fe1f-102c-bc40-b9730dd942ef
DateTime= 17/02/2010 08:24:45 PM    App= 208  Security             Group= Unknown                   Unit= 005                       Event= Security unknown event
DateTime= 17/02/2010 08:24:45 PM    App= 208  Security             Group= Unknown                   Unit= 127                       Event= Security status report 1: //628RIETV/254/208 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 #sourceunit=127 OID=276fd2b0-fe1f-102c-bc40-b9730dd942ef
DateTime= 17/02/2010 08:24:56 PM    App= 056  Lighting             Group= 097  East Light L State   Unit= 005                       Event= Group on
DateTime= 17/02/2010 08:24:56 PM    App= 056  Lighting             Group= 095  West Light L State   Unit= 005                       Event= Group on
DateTime= 17/02/2010 08:24:57 PM    App= 056  Lighting             Group= 253  DebugTestGA          Unit= 005                       Event= Group ramped to 004 (  2%) over 4 seconds
DateTime= 17/02/2010 08:24:57 PM    App= 056  Lighting             Group= 063  Perimeter Fence Lights Unit= 005                       Event= Group ramped to 255 (100%) over 4 seconds
DateTime= 17/02/2010 08:24:57 PM    App= 056  Lighting             Group= 050  Outside Bar Light 1  Unit= 005                       Event= Group ramped to 204 ( 80%) over 90 seconds
DateTime= 17/02/2010 08:24:57 PM    App= 056  Lighting             Group= 047  Outside Kitchen Light 1 Unit= 005                       Event= Group ramped to 206 ( 81%) over 30 seconds
DateTime= 17/02/2010 08:24:57 PM    App= 056  Lighting             Group= 033  Outside Patio Light  Unit= 005                       Event= Group ramped to 209 ( 82%) over 60 seconds
DateTime= 17/02/2010 08:24:57 PM    App= 056  Lighting             Group= 044  CoveredEntry Light 1 Unit= 005                       Event= Group ramped to 211 ( 83%) over 20 seconds
DateTime= 17/02/2010 08:24:57 PM    App= 056  Lighting             Group= 015  Open Terrace Light   Unit= 005                       Event= Group ramped to 214 ( 84%) over 120 seconds
DateTime= 17/02/2010 08:24:57 PM    App= 056  Lighting             Group= 023  Outside Family Room  Unit= 005                       Event= Group ramped to 201 ( 79%) over 40 seconds
DateTime= 17/02/2010 08:24:57 PM    App= 203  Enable Control       Group= 021  InsideMotionControlledLights Unit= 005                       Event= Network Variable set on
DateTime= 17/02/2010 08:25:01 PM    App= 056  Lighting             Group= 254  PACStatus            Unit= 005                       Event= Group off
DateTime= 17/02/2010 08:25:06 PM    App= 223  Clock and Timekeeping Group= N/A                       Unit= 005                       Event= Group on
DateTime= 17/02/2010 08:25:48 PM    App= 223  Clock and Timekeeping Group= N/A                       Unit= 005                       Event= Date Broadcast: Date set to Wednesday 2010-02-17.
    Will let you know if it happens again.

    Josh
     
    Josh, Feb 19, 2010
    #4
  5. Josh

    Josh

    Joined:
    Aug 25, 2004
    Messages:
    240
    Likes Received:
    0
    Location:
    Pretoria, South Africa
    It happened again while I was away from home. When I arrived, the DLTs showed the time as 9h45 in the morning. Listening to Comfort events revealed that the was a power failure around 9H45, and that time (Comfort time) was set around 16H00 back to 09H45.
     
    Josh, Feb 24, 2010
    #5
  6. Josh

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,391
    Likes Received:
    24
    Location:
    Adelaide, South Australia
    **SOUNDS** like the Comfort system is not sending the date and time in the correct format.
     
    ashleigh, Feb 24, 2010
    #6
  7. Josh

    Ingo

    Joined:
    Dec 2, 2006
    Messages:
    290
    Likes Received:
    1
    Location:
    South Africa
    Josh,

    Try to simulate the problem with a manual 'power failure'. Once you have done this, change the firmware back to 3.43 and do the same to see if it's the firmware. Capture the logs wherever possible.

    Ingo
     
    Ingo, Feb 25, 2010
    #7
  8. Josh

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,420
    Likes Received:
    62
    Location:
    Adelaide
    This would be great, and we do appreciate the help.

    Logs from the Diagnostic utility are the most helpful if possible.

    The PAC should wait around 30-45 seconds after powerup before assuming the role of Time Master (sounds like something from Dr Who) and broadcasting its time, so you have a little bit of time to reconnect the Diagnostic Utility if its PCI has lost connection due to the power fail event.

    Nick
     
    NickD, Feb 25, 2010
    #8
  9. Josh

    Josh

    Joined:
    Aug 25, 2004
    Messages:
    240
    Likes Received:
    0
    Location:
    Pretoria, South Africa
    Nick and Ingo,

    I tried. I hit a snag in the process.

    I loaded 3.43. PAC now reboots every few seconds, I cannot connect to load 3.50 again. No logic is running. The top LED flashes, then both LED stay solid for a while and both switch off for a brief period, and then the process repeats again.
     

    Attached Files:

    Last edited by a moderator: Feb 25, 2010
    Josh, Feb 25, 2010
    #9
  10. Josh

    Josh

    Joined:
    Aug 25, 2004
    Messages:
    240
    Likes Received:
    0
    Location:
    Pretoria, South Africa
    Firmware 3.43 to 3.50

    Here is the log from PICED when I try to tranfer the logic and firmware

    Code:
    25/02/2010 05:54:07 PM  Info     : Connecting to unit at 9600 baud
25/02/2010 05:54:07 PM  PAC      : Tx "80 00 00 06 FF 7A "
25/02/2010 05:54:07 PM  PAC      : Rx "FF F0 00 06 FE 0B "
25/02/2010 05:54:07 PM  PAC      : Tx "80 00 00 06 FF 7A "
25/02/2010 05:54:07 PM  PAC      : Rx "FF F5 00 06 FE 06 "
25/02/2010 05:54:07 PM  PAC      : Tx "80 00 00 06 FF 7A "
25/02/2010 05:54:07 PM  PAC      : Rx "FF F0 00 06 FE 0B "
25/02/2010 05:54:07 PM  PAC      : Tx "80 00 00 06 FF 7A "
25/02/2010 05:54:08 PM  PAC      : Rx "FF FF 00 06 FD FC "
25/02/2010 05:54:08 PM  Info     : Connecting to unit at 38400 baud
25/02/2010 05:54:08 PM  PAC      : Tx "80 00 00 06 FF 7A "
25/02/2010 05:54:09 PM  PAC      : Tx "80 00 00 06 FF 7A "
25/02/2010 05:54:09 PM  PAC      : Rx "FF FF 00 06 FD FC "
25/02/2010 05:54:09 PM  PAC      : Tx "8E 00 00 06 FF 6C "
25/02/2010 05:54:09 PM  PAC      : Tx "8E 00 00 06 FF 6C "
25/02/2010 05:54:09 PM  PAC      : Rx "8E 01 00 0A DE AD BA BA FC 68 "
25/02/2010 05:54:09 PM  PAC      : Tx "80 02 00 0C 00 00 01 F0 00 10 FE 71 "
25/02/2010 05:54:10 PM  PAC      : Rx "80 03 00 1A 00 00 01 F0 31 2E 34 00 00 00 00 00 00 00 00 00 00 00 00 00 FD DF "
25/02/2010 05:54:10 PM  PAC      : Tx "8E 00 00 06 FF 6C "
25/02/2010 05:54:10 PM  PAC      : Rx "8E 01 00 0A DE AD BA BA FC 68 "
25/02/2010 05:54:10 PM  PAC      : Tx "80 02 00 0C 00 00 10 10 00 10 FF 42 "
25/02/2010 05:54:10 PM  PAC      : Rx "80 03 00 1A 00 00 10 10 33 2E 34 33 2E 30 00 00 00 00 00 00 00 00 00 00 FE 1D "
25/02/2010 05:54:24 PM  Info     : Preparing Files
25/02/2010 05:54:24 PM  Info     : Files Ready
25/02/2010 05:54:24 PM  Info     : Prepare for transfer
25/02/2010 05:54:24 PM  Info     : Erase EEPROM
25/02/2010 05:54:24 PM  PAC      : Tx "82 03 00 06 FF 75 "
25/02/2010 05:54:27 PM  PAC      : Tx "82 03 00 06 FF 75 "
25/02/2010 05:54:30 PM  PAC      : Tx "82 03 00 06 FF 75 "
25/02/2010 05:54:33 PM  PAC      : Tx "82 03 00 06 FF 75 "
25/02/2010 05:54:36 PM  PAC      : Tx "82 03 00 06 FF 75 "
25/02/2010 05:54:39 PM  PAC      : Tx "82 03 00 06 FF 75 "
25/02/2010 05:54:42 PM  PAC      : Tx "82 03 00 06 FF 75 "
25/02/2010 05:54:45 PM  PAC      : Tx "82 03 00 06 FF 75 "
25/02/2010 05:54:48 PM  Info     : Stop unit application from running
25/02/2010 05:54:48 PM  PAC      : Tx "87 00 00 06 FF 73 "
25/02/2010 05:54:51 PM  PAC      : Tx "87 00 00 06 FF 73 "
25/02/2010 05:54:54 PM  PAC      : Tx "87 00 00 06 FF 73 "
25/02/2010 05:54:57 PM  PAC      : Tx "87 00 00 06 FF 73 "
25/02/2010 05:55:00 PM  PAC      : Tx "87 00 00 06 FF 73 "
25/02/2010 05:55:03 PM  PAC      : Tx "87 00 00 06 FF 73 "
25/02/2010 05:55:06 PM  PAC      : Tx "87 00 00 06 FF 73 "
25/02/2010 05:55:09 PM  PAC      : Tx "87 00 00 06 FF 73 "
25/02/2010 05:55:13 PM  Info     : Erase Firmware memory
25/02/2010 05:55:13 PM  PAC      : Tx "80 05 00 0A 00 01 00 09 FF 67 "
25/02/2010 05:55:18 PM  PAC      : Tx "80 05 00 0A 00 01 00 09 FF 67 "
25/02/2010 05:55:23 PM  PAC      : Tx "80 05 00 0A 00 01 00 09 FF 67 "
25/02/2010 05:55:28 PM  PAC      : Tx "80 05 00 0A 00 01 00 09 FF 67 "
25/02/2010 05:55:33 PM  Info     : Re-start unit
25/02/2010 05:55:33 PM  PAC      : Tx "87 02 00 06 FF 71 "
25/02/2010 05:55:35 PM  PAC      : Tx "87 02 00 06 FF 71 "
25/02/2010 05:55:37 PM  PAC      : Tx "87 02 00 06 FF 71 "
25/02/2010 05:55:39 PM  PAC      : Tx "87 02 00 06 FF 71 "
25/02/2010 05:55:41 PM  Info     : Close COM Port
     
    Josh, Feb 25, 2010
    #10
  11. Josh

    Darren Senior Member

    Joined:
    Jul 29, 2004
    Messages:
    2,361
    Likes Received:
    0
    Location:
    Adelaide, South Australia
    Are you using either PICED V4.8 or V4.8.1?

    If so, V3.43 firmware is not compatible, and loading this version will cause problems.
     
    Darren, Feb 26, 2010
    #11
  12. Josh

    Josh

    Joined:
    Aug 25, 2004
    Messages:
    240
    Likes Received:
    0
    Location:
    Pretoria, South Africa
    Darren,

    It was suggested that I should load 3.43, hence why I did.


    Josh
     
    Josh, Feb 26, 2010
    #12
  13. Josh

    Darren Senior Member

    Joined:
    Jul 29, 2004
    Messages:
    2,361
    Likes Received:
    0
    Location:
    Adelaide, South Australia
    OK. That version of firmware should only be loaded with the older versions of PICED.

    Regardless of that, it should not cause the PAC to keep resetting. We will look into what is going on.
     
    Darren, Feb 27, 2010
    #13
  14. Josh

    Josh

    Joined:
    Aug 25, 2004
    Messages:
    240
    Likes Received:
    0
    Location:
    Pretoria, South Africa
    Ashleigh,

    Before I had issues with the PAC, I removed Comfort from the network and got the same results.

    Ok. Let me know if you need anything.
     
    Josh, Mar 2, 2010
    #14
  15. Josh

    Davo Guest

    PAC Unit Resetting Also

    Hi Darren,

    I've got exactly the same issue as Josh where I've updated the Firmware to 3.43 using PICED 4.4.1 and the PAC unit just keeps resetting itself and any attempt to flash the firmware just fails with Error 14614 - Transfer Error.

    I've tried updating with PICED 4.7.2 and am getting the same error also.

    Any assistance would be greatly appreciated.
     
    Davo, Mar 2, 2010
    #15
  16. Josh

    Darren Senior Member

    Joined:
    Jul 29, 2004
    Messages:
    2,361
    Likes Received:
    0
    Location:
    Adelaide, South Australia
    It looks like there is a problem if you mix up the PAC and PICED versions. Issue #18794

    We are looking into ways of recovering the PAC unit if you do this.
     
    Darren, Mar 3, 2010
    #16
  17. Josh

    Ingo

    Joined:
    Dec 2, 2006
    Messages:
    290
    Likes Received:
    1
    Location:
    South Africa
    Josh,

    I just had the same time issue you initially had in this thread. On Friday we had a massive thunder storm and my Comfort system went all haywire - it lost comms to the keypads and slaves probably due to some lightning action around my house (these things happen....)

    Anyway, when I got back today, reset Comfort to restore comms, I saw my lights in my house went on as per my nightly routine. Inspecting the date on Comfort it said 5 March at around 19:00 odd hours.

    I suspect that Comfort froze completely and once it got going again it then broadcast the TIME on the CBus network and set my actions in motion.

    All,
    Can I block the time broadcast from setting my PAC time? I will also ask the Comfort forum if I can disable the broadcast of time from that side towards CBus. (I am running 3.43 and PICED 4.72 at the moment)

    Thanks,
    Ingo
     
    Ingo, Mar 7, 2010
    #17
  18. Josh

    Josh

    Joined:
    Aug 25, 2004
    Messages:
    240
    Likes Received:
    0
    Location:
    Pretoria, South Africa
    Ingo,

    Did you listen to the events on Comfort (Keypad) to see when the time set happend?
     
    Josh, Mar 7, 2010
    #18
  19. Josh

    Ingo

    Joined:
    Dec 2, 2006
    Messages:
    290
    Likes Received:
    1
    Location:
    South Africa
    I wasn't at home. When I got here both keypads were beeping very fast and displaying 'Communications Error'. After a reset my system armed again to try and resume the previous state. I then reset all slaves and the master panel just to be sure but by that time the time was already displayed around 19:00.

    Here is my event log. You can see the time after last arming and when the system 'came alive' I reset the system twice and then set the Comfort time via Comfigurator. Once I set Comfort to the correct time the PAC was also updated automatically.

    Mar 03, 17:11, Mode Change : Away
    Mar 05, 15:55, RS485 Comms Fail <- This was today!!!
    Mar 05, 15:55, RS485 Comms Fail : SEM 2
    Mar 05, 15:55, Alarm : RS485 Coms Fail
    Mar 05, 15:55, Tamper
    Mar 05, 15:55, Alarm : Tamper
    Mar 05, 15:55, RS485 Comms Fail : SEM 3
    Mar 05, 15:55, Alarm : RS485 Coms Fail
    Mar 05, 15:55, Tamper
    Mar 05, 15:55, Alarm : Tamper
    Mar 05, 15:55, RS485 Comms Fail
    Mar 05, 15:55, Alarm : RS485 Coms Fail
    Mar 05, 15:55, RS485 Comms Fail
    Mar 05, 15:55, Alarm : RS485 Coms Fail
    Mar 05, 15:55, RS485 Comms Fail : SEM 1
    Mar 05, 15:55, Alarm : RS485 Coms Fail
    Mar 05, 15:55, Tamper
    Mar 05, 15:55, Alarm : Tamper
    Mar 05, 18:57, Zone Activation : 2
    Mar 05, 18:57, Alarm : Entry Alert
    Mar 05, 18:57, Reset
    Mar 05, 18:58, Bypass Zone
    Mar 05, 18:58, Bypass Zone
    Mar 05, 18:58, Unbypass Zone
    Mar 05, 18:58, Unbypass Zone
    Mar 05, 18:58, Sign In : 1
    Mar 05, 18:58, Mode Change : Off
    Mar 05, 18:58, RS485 Comms Fail : SEM 1
    Mar 05, 18:58, RS485 Comms Fail : SEM 2
    Mar 05, 18:58, Alarm : RS485 Coms Fail
    Mar 05, 18:58, RS485 Comms Fail : SEM 3
    Mar 05, 18:58, Alarm : RS485 Coms Fail
    Mar 05, 19:00, RS485 Comms Restore
    Mar 05, 19:00, RS485 Comms Restore
    Mar 05, 19:00, RS485 Comms Restore
    Mar 05, 19:01, Reset
    Mar 05, 19:01, Sign In : 0
    Mar 05, 19:01, Mode Change : Off
    Mar 07, 18:43, Date Time Change <- This was a few minutes later when I set the time via Comfigurator.
     
    Ingo, Mar 7, 2010
    #19
  20. Josh

    Davo Guest

    Hi Darren,

    Has there been any progress on recovering the PAC unit when it keeps resetting?
     
    Davo, Mar 13, 2010
    #20
Page 1 of 2
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. SENPILL After Power Failure....

  2. 06-019-1 Enable & Disable Status After A Power Failure

  3. SENPILL (Multisensor) Occupancy sensor enabled after power failure

  4. Power Failure Recovery Problems

  5. C-bus state recall from C-Touch after power failure

  6. PAC status after power failure

  7. C-Touch MKII Power Failure Recovery

  8. PAC Power Failure Recovery

Loading...