Home AMX User Forum AMXForums Archive Threads AMX Hardware

Zigbee Firmware (latest)

jjamesjjames Just another dudePosts: 2,906
Anyone else running into problems when updating? My ZGW's Zigbee Firmware says "X" after updating from 3.0.0; it's as if it kills the Zigbee RF on some ZGWs, not all.

Any ideas?

Comments

  • DiogoDiogo Junior Member Posts: 65
    happened the same with me, but was working just fine, but I reupgrade the firmware and it shows up withou the XXX.

    You should try it.
  • jjamesjjames Just another dude Posts: 2,906
    Oh I've downgraded & upgraded numerous times and still no luck. I've not tried actually connecting anything, so maybe it STILL works, but is just reporting bad info.
  • the8thstthe8thst Junior Member Posts: 470
    Is that the update that you have to send to the Gateway twice, or is that only if upgrading a gateway that is an older version than 3.x?

    I haven't had problems with the new firmware upgrades at all, but I do remember some of them needing to be sent once -> hard cycle power -> resend first file.
  • jjamesjjames Just another dude Posts: 2,906
    Here's some more info. The web pages reports "X" for the Zigbee Firmware and 0 for the channel number on the summary page as well as no EUI; under the Pan (Network) page, the network status is blank, but is reporting an extended pan ID all while being enabled. I cannot even see the ZGW when I try to commission a new remote.

    Now, on an online tree through studio I get the proper firmware, but 3.01.05 for the repeater and end-user and 3.01.06 for the coordinator. So it appears to work at least through Studio.

    Through telnet, I ran the debugMem and rfTest commands. debugMem yields:
    1/20/10 1:19:19 PM-Shell::BuiltIn debugMem
    Global Message Count
     MxMsg       0
     ZigBeeMsg   0
     ICSPMsg     0
     XmodemMsg   0
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-Trying to restart (null) - ignored
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: v
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 2
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: b
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 6
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 1
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: .
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: u
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: p
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: l
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: o
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: e
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: b
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: l
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 2
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: .
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: r
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: u
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: n
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 3
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: .
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: e
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: b
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: l
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: i
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: n
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: f
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: o
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: B
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: L
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: >
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x00
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-Trying to restart (null) - ignored
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: v
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 2
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: b
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 6
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 1
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: .
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: u
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: p
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: l
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: o
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: e
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: b
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: l
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 2
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: .
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: r
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: u
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: n
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 3
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: .
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: e
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: b
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: l
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: i
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: n
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: f
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: o
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: B
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: L
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: >
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x00
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-Trying to restart (null) - ignored
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: v
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 2
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: b
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 6
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 1
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: .
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: u
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: p
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: l
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: o
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: e
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: b
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: l
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 2
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: .
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: r
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: u
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: n
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 3
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: .
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: e
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: b
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: l
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: i
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: n
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: f
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: o
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0d
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x0a
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: B
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: L
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: >
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data:
    1/20/10 1:19:32 PM-SerialPortIn::processByte received unknown data: 0x00
    

    rfTest results in:
    1/20/10 1:20:05 PM-Shell::BuiltIn rfTest
    rfTest, No ZigBee devices available
    

    The front of the ZGW displays an active PWR/STATUS blink and a good LAN link; RF is not on.

    I'd downgraded to 3.00.00 to see if I could redo the process; at 3.00.00 - everything seems to work. Once I upgrade one step (3.01.05), that's when things go crazy. I can continue to upgrade to 3.01.11, but the Zigbee Firmware is toast.

    I'll be calling into TS to see if they have some input.
  • jjamesjjames Just another dude Posts: 2,906
    the8thst wrote: »
    I haven't had problems with the new firmware upgrades at all, but I do remember some of them needing to be sent once -> hard cycle power -> resend first file.

    That's the weird thing . . . it doesn't "fail" the first time. Maybe I'll send it a couple of times for the heck of it.

    Thanks for the reminder.
  • DHawthorneDHawthorne Old Timer Posts: 4,584
    I had no problems with the few I've upgraded.
  • atiofamericaatiofamerica Junior Member Posts: 10
    Same thing happened to me. You have to go back to an early version of firmware then bring it back to the latest. Make sure the auto reboot is not checked.
  • jjamesjjames Just another dude Posts: 2,906
    To further deepen the pain I've been feeling because of this new firmware - my R4s have been falling offline when I send a mere 20 commands to it; before it wouldn't. It seems as if the gateway would choke because all of the R4s connected would fall offline when sending about 20 commands any remote.

    I'll be calling TS regarding this - but so far, I've not seen any improvement from the previous firmware to the current for the ZGWs. I'm not suggesting to avoid the upgrade, I'm simply sharing my experience and thoughts.
  • jjamesjjames Just another dude Posts: 2,906
    Same thing happened to me. You have to go back to an early version of firmware then bring it back to the latest. Make sure the auto reboot is not checked.

    Can you explain your process? Which don't need to be checked? I was always told that the ZGW Firmware (not the Zigbee end-device or repeater firmware) needed to be rebooted until the last step.
  • jjamesjjames Just another dude Posts: 2,906
    Okay . . . got off the phone with TS.

    If you're encountering an "X" for your Zigbee Firmware on the gateway after an upgrade, do the following.

    1) Call AMX Tech Support and get ZGW firmware version 1.01.20 from their FTP site (if you have the credentials, great - don't post them here. Otherwise call and get it from AMX.)
    2) Downgrade your ZGW to 1.01.20
    3) Follow the upgrade process of going from Zigbee to Zigbee Pro (3.0.0)
    4) Upgrade to the firmware you need. If you need the latest, I'd suggest doing any firmware upgrades in between 3.0.0 to 3.01.11; since I'm going with 3.01.07 - I'm going to stop there.

    A couple of notes:
    * After you downgrade to 1.01.20 - keep in mind that version does not support a password protected connection to the master. So if you need a username & password to connect - remove it temporarily.

    * Versions 1.01.20 & 3.00.00 only require one file and a reboot is needed.

    After spending about 30 minutes on a ZGW - it still shows up with an X for the Zigbee Firmware. Talk about depressing.

    Edit: After resending ALL of 3.01.07 . . . it started working again. Talk about puzzling.
  • DiogoDiogo Junior Member Posts: 65
    Jeremiah,

    If you are having problems with falling offline for too many traffic, make the current/previous logic(I really don't know how it's called in english, by here we call "break" logic) and put messages to a minimum.

    Should appear like:
         
         IF PREVIOUS_VALUE <> CURRENT_VALUE
         {
               SEND_LEVEL dvR4, 1, CURRENT_VALUE
               PREVIOUS_VALUE = CURRENT_VALUE
         }
     
    
  • Joe HebertJoe Hebert Junior Member Posts: 2,159
    Diogo wrote: »
    Jeremiah,

    If you are having problems with falling offline for too many traffic, make the current/previous logic(I really don't know how it's called in english, by here we call "break" logic) and put messages to a minimum.

    Should appear like:
         
         IF PREVIOUS_VALUE <> CURRENT_VALUE
         {
               SEND_LEVEL dvR4, 1, CURRENT_VALUE
               PREVIOUS_VALUE = CURRENT_VALUE
         }
     
    
    The IF condition shouldn?t be necessary. The master tracks the current state of all levels and only sends level updates if the level value has changed.
  • jjamesjjames Just another dude Posts: 2,906
    I'm not having problems with the levels, but commands such as TXT, BMP, SHO, ENA, etc.

    I'm currently running this without any problems:
    Gateway Firmware: 3.01.07
    Gateway Zigbee FW: 3.01.05
    R4 Firmware: 3.01.05

    I was having a ton of problems (ZGW locking up and kicking all connected remotes offline) with TXT, BMP, etc. on the latest firmware which is:
    Gateway FW: 3.01.11
    Gateway Zigbee FW: 3.01.06
    R4 Firmware 3.01.05
  • Zigbee Firmware (latest)
    jjames wrote: »
    Anyone else running into problems when updating? My ZGW's Zigbee Firmware says "X" after updating from 3.0.0; it's as if it kills the Zigbee RF on some ZGWs, not all.

    Any ideas?

    When upgrading the ZigBee PRO firmware, after the PPC has been upgraded, the PPC then upgrades the ZigBee radio firmware. While the radio is being upgraded, the gateway "Summary" web page will display an "X" for the version of the ZigBee Firmware. The radio upgrade takes about 2 minutes. Since this page is not self refreshing, the "X" will be displayed until the page is refreshed. Sometimes it is necessary to close and reopen the browser. After the radio is programmed, the correct version is shown in NetLinx even though it does not show the correct version on the web page.
  • sjohnson wrote: »
    When upgrading the ZigBee PRO firmware, after the PPC has been upgraded, the PPC then upgrades the ZigBee radio firmware. While the radio is being upgraded, the gateway "Summary" web page will display an "X" for the version of the ZigBee Firmware. The radio upgrade takes about 2 minutes. Since this page is not self refreshing, the "X" will be displayed until the page is refreshed. Sometimes it is necessary to close and reopen the browser. After the radio is programmed, the correct version is shown in NetLinx even though it does not show the correct version on the web page.

    To elaborate a little more.

    When you download a new radio version to the gateway, the gateway does not upgrade it immediately. Instead it will upgrade after you reboot the gateway. This upgrade takes about 1-2 minutes, and if you reboot the gateway during this time, the radio will only get a partial load of firmware.

    This will cause the gateway to be unable to talk to the radio, so if the gateway boots up and cannot talk to the radio, then it starts upgrading the radio to the last version that was loaded. While this is happening, the radio's version will show up as X.

    Give it 2-3 minutes to finish, and everything should be fine.
  • jjamesjjames Just another dude Posts: 2,906
    Hmm - I'm not onsite to actually check, but one ZGW has been online for a day or two and it's still display an "X". Perhaps an RMA is in order . . .

    Anyway - I'd been running into major problems with this firmware (such as multiple commands knocking off the remotes), so I'll stick with 3.01.07 / .05 for now until it's fixed.

    Thanks though!
  • jjames wrote: »
    Hmm - I'm not onsite to actually check, but one ZGW has been online for a day or two and it's still display an "X". Perhaps an RMA is in order . . .

    Anyway - I'd been running into major problems with this firmware (such as multiple commands knocking off the remotes), so I'll stick with 3.01.07 / .05 for now until it's fixed.

    Thanks though!

    The only other possibility that I know about is that you ran into an old bug on the Pre 3.0 firmware. There was a chance in the old firmware that the radio upgrade would fail if you had traffic running on your system. this would cause the download to time out without upgrading the radio. If you were upgrading from pre 3.0 to anything 3.0 you may have run into this. The solution is to go back to the pre 3.0 and re upgrade, and make sure there are no remotes online when you do it.
  • jjamesjjames Just another dude Posts: 2,906
    rhargrave wrote: »
    The only other possibility that I know about is that you ran into an old bug on the Pre 3.0 firmware. There was a chance in the old firmware that the radio upgrade would fail if you had traffic running on your system. this would cause the download to time out without upgrading the radio. If you were upgrading from pre 3.0 to anything 3.0 you may have run into this. The solution is to go back to the pre 3.0 and re upgrade, and make sure there are no remotes online when you do it.

    Thanks, I'll run through it again and see what happens. I guess I'll be a bit more patient.
  • jjames wrote: »
    Thanks, I'll run through it again and see what happens. I guess I'll be a bit more patient.

    Looking at the log you posted earlier, the radio is stuck in bootloader mode. That is a sure sign of a failed radio upgrade. 3.01.11 will auto recover from that fault, but I am not sure if 3.01.07 will.
Sign In or Register to comment.