Can't connect to my GEM

[rnoble]

So I decided to update my firmware(s)... The COM firmware updated fine. When I attempted to update the ENG firmware I was prompted to switch the baud rate to 19200. Now I can connect to my GEM, but when I try to "Get GEM info" I get the below message

Refresh error 20
Response data=
Data Length = 0

Any idea how I can fix it?

I'm connecting via a serial connection on my DashBox.

[rnoble]

And I have a red LED no matter what I do... Kinda freaking out here.

[ben]

And I have a red LED no matter what I do... Kinda freaking out here.

Is it a blinking red LED or a red LED?

I'm guessing solid red, solid red means it's waiting for firmware. A power cycle will take it out of this state.

So I decided to update my firmware(s)... The COM firmware updated fine. When I attempted to update the ENG firmware I was prompted to switch the baud rate to 19200. Now I can connect to my GEM, but when I try to "Get GEM info" I get the below message

Refresh error 20
Response data=
Data Length = 0

Any idea how I can fix it?

I'm connecting via a serial connection on my DashBox.

The GEM likely jumped back to 115200. If you're using the serial connection to connect through the DashBox, try setting that back to 115200 and rebooting.

EDIT: Based on the information above, you can't talk to it due to it waiting for the firmware file. Try just power cycling it.

[rnoble]

And I have a red LED no matter what I do... Kinda freaking out here.

Is it a blinking red LED or a red LED?

I'm guessing solid red, solid red means it's waiting for firmware. A power cycle will take it out of this state.

So I decided to update my firmware(s)... The COM firmware updated fine. When I attempted to update the ENG firmware I was prompted to switch the baud rate to 19200. Now I can connect to my GEM, but when I try to "Get GEM info" I get the below message

Refresh error 20
Response data=
Data Length = 0

Any idea how I can fix it?

I'm connecting via a serial connection on my DashBox.

The GEM likely jumped back to 115200. If you're using the serial connection to connect through the DashBox, try setting that back to 115200 and rebooting.

EDIT: Based on the information above, you can't talk to it due to it waiting for the firmware file. Try just power cycling it.

It's solid red. I'll try another power-cycle. Do I need to remove the battery?

Thanks!

[ben]

It's solid red. I'll try another power-cycle. Do I need to remove the battery?

Thanks!

Shouldn't need to unless the red LED won't go away. In that case, pop out the battery while power is connected (don't use anything metallic to pop it out), then cycle power to it. Leave the battery out until it's up and running.

Ben

[rnoble]

It's solid red. I'll try another power-cycle. Do I need to remove the battery?

Thanks!

Shouldn't need to unless the red LED won't go away. In that case, pop out the battery while power is connected (don't use anything metallic to pop it out), then cycle power to it. Leave the battery out until it's up and running.

Ben

Went to power cycle it and now it's flashing red... Still can't connect. Thoughts?

[Teken]

Ryan,

Is there still a problem with your GEM? As your Dash Box seems to be working well and energy data is flowing and available for viewing.

[ben]

It's solid red. I'll try another power-cycle. Do I need to remove the battery?

Thanks!

Shouldn't need to unless the red LED won't go away. In that case, pop out the battery while power is connected (don't use anything metallic to pop it out), then cycle power to it. Leave the battery out until it's up and running.

Ben

Went to power cycle it and now it's flashing red... Still can't connect. Thoughts?

Flashing red usually means that the PT is not connected. Make sure it's pushed all the way in.

[rnoble]

Ryan,

Is there still a problem with your GEM? As your Dash Box seems to be working well and energy data is flowing and available for viewing.

I got it figure out last night... The GEM and DashBox were set to difference baud rates... Once I rebooted the GEM in recovery mode and set the DashBox to 19200, I was able to push the new firmwares and be on my way.

For future reference, what is the correct process for pushing new firmware to the GEM connected via serial to a DashBox?

[Teken]

Ryan,

Is there still a problem with your GEM? As your Dash Box seems to be working well and energy data is flowing and available for viewing.

I got it figure out last night... The GEM and DashBox were set to difference baud rates... Once I rebooted the GEM in recovery mode and set the DashBox to 19200, I was able to push the new firmwares and be on my way.

For future reference, what is the correct process for pushing new firmware to the GEM connected via serial to a DashBox?

The first thing I do is set the GEM Network Utility Tool to firmware Mode under the Comm Settings -> Ethernet Only tab.

I then select the Firmware tab -> Open a connection ensuring there is a solid green status -> Select Get GEM info -> Upload the COM firmware using 115200 baud.

Once the system reboots, I set the baud rate to 19200 for the Engine firmware upload. After that is done I always do a full reboot of the GEM.

Once done, I set the baud rate back to 115200 while still in the Firmware tab. Go back to the Ethernet Only tab and change the Comm Setting back to Normal and select Save Settings.