www.brultech.com

io_guy wrote:There should really be a way to just disable wireless.

There is now, check the GEM Setup Adv section.

If you get locked out however due to an issue with Ethernet, you'll have to do a full reset to the module.

Do you mean a full reset of the comm module or GEM itself?

io_guy wrote:Do you mean a full reset of the comm module or GEM itself?

Full reset of the WiFi/Ethernet module, not the GEM itself.

I just tried upgrading to GEM_C_Firmware_4.17_.fmw over ethernet and at about 14% i got timeout / error 0.

Now the GEM utility connects to my IP address, but clicking 'get GEM info' results in 'could not communicate with GEM.' and in the UI it says Timeout Error!

What should i do next? (i am not familiar with recovery mode having never used it so any pointer gratefully received)

Ok, i figured out how to get into recovery mode.
I set the BAUD rate to 19,200 via the uart webpage.
I set the COM firmware section to 'recovery mode'.
I rebooted with the PB pushed - on the 2nd attempt the red light turned red.

I started the firmware upgrade process it has now hung at 12.8%.

What next?

--edit--
it now just went from 12.8% to 12.9% after being hung for a minute...

--edit2--
oh now it went from 12.9% to 13.1% after another minute or so.

the UART ver is 4.02.10.C1224

The recovery mode baud rate instructions are only for old firmwares. The GEM will now program at 115200 in Recovery Mode.

Put the baud back up to 115200, and load it with that baud.

ben wrote:The recovery mode baud rate instructions are only for old firmwares. The GEM will now program at 115200 in Recovery Mode.

Put the baud back up to 115200, and load it with that baud.

thanks Ben!

1) Did that, makes no difference - got to 22.9% and now see same slow behaviour - at this rate it will take at least a day to complete
2) if 115200 is supported why did the 7.0 UI tell me to put it to 19,200 - might want to revise that?

what next?
note i am connecting via ethernet not wifi as the OP did to fix

--edit---
i tried via wifi - same issue

--edit2--
tried going back to 4.0 and have same issue so it's not a firmware file issue

Ok fixed.

I unplugged the ethernet cable.
I put a wifi adapter in my desktop so i could connect directly
Nothing else is connecting via wifi to the GEM
I happened to be at 19,200 but i don't think the baud has any bearing on this issues.
Upgrade went fine.

I have a hypothesis - that it is communication from another device that is consuming GEM data that causes the issue (Vera home controller or nodelink for ISY or somesuch) - in my system these connect by ethernet only.

For completeness the unit is a GEM-WE-X (Wifi/Ethernet V2 + XBee Module)

Alex

scyto wrote:Ok fixed.

I unplugged the ethernet cable.
I put a wifi adapter in my desktop so i could connect directly
Nothing else is connecting via wifi to the GEM
I happened to be at 19,200 but i don't think the baud has any bearing on this issues.
Upgrade went fine.

I have a hypothesis - that it is communication from another device that is consuming GEM data that causes the issue (Vera home controller or nodelink for ISY or somesuch) - in my system these connect by ethernet only.

For completeness the unit is a GEM-WE-X (Wifi/Ethernet V2 + XBee Module)

Alex

Hmm, does sound like something might've been coming through the Ethernet. The Xbee wouldn't cause issues as I confirmed with Paul that it ignores the opposing COM port once it starts updating firmware.

ben wrote:
Hmm, does sound like something might've been coming through the Ethernet. The Xbee wouldn't cause issues as I confirmed with Paul that it ignores the opposing COM port once it starts updating firmware.

Well the only things are a Vera and the brultech plugin for that and Nodelink for the ISY. Nothing else i have interrogates the GEM.

I am happy to try and repro and capture stuff as it seems multiple folks had similar issues with this module?