Unable to upgrade GEM COM firmware to 5.13

[ben]

Yes.

EDIT: Was finally able to get it by pointing a browser to the GEM while at 19200 and then changing the speed to 115200 from the advanced tab.

My other 2 GEMs are connected directly to my Dashbox. What would be the recommended procedure to get them updated? They are currently on COM 4.33

If you're not experiencing any issues I would just leave them at 4.33, all F/W improvements in the 4/5 series are all very minor (little packet changes, things like that) and don't impact DashBox performance.

[ben]

Yes.

EDIT: Was finally able to get it by pointing a browser to the GEM while at 19200 and then changing the speed to 115200 from the advanced tab.

My other 2 GEMs are connected directly to my Dashbox. What would be the recommended procedure to get them updated? They are currently on COM 4.33

COM4.33 should be upgradable to COM5.13 without any setting changes if you still want to follow thru. COM firmwares can be loaded at 115200 since COM4.00.

If STS connected, just use DashBox-IP Port 8001/8002 (DashBox RS232 #1/DashBox RS232 #2) via TCP-IP Client.

[crazydane]

Thanks Ben, will do.

I spoke too soon about the Ethernet only GEM being good to go. It dropped from my Dashbox view again:



So I fired up GEM Network Utility again from my laptop connected directly to COM1 on the GEM and did a scan from the Network tab:



Went to the Ethernet Only tab and did a scan here as well:



Clicked the Serial radio button in the upper right corner, and then did a Get GEM Info and got this:



So what am I doing wrong? Should I disconnect my laptop connected to COM1, or is something else going on?

[ben]

Thanks Ben, will do.

I spoke too soon about the Ethernet only GEM being good to go. It dropped from my Dashbox view again:

So I fired up GEM Network Utility again from my laptop connected directly to COM1 on the GEM and did a scan from the Network tab:

Went to the Ethernet Only tab and did a scan here as well:

Clicked the Serial radio button in the upper right corner, and then did a Get GEM Info and got this:

So what am I doing wrong? Should I disconnect my laptop connected to COM1, or is something else going on?

What COM F/W was that GEM running before? Your settings from the Get GEM Info look messed up (PT Type/Range 0 for example).

Can you open the GEM Setup Webpage and grab screencaps of the Channel Option, Chan CT, and Packet Send sections?

[crazydane]

Here you go Ben:

[ben]

Here you go Ben:

All looks good.

Can you check Adv COM1/COM2 settings and make sure Flow Control is set to "Disabled" on both.

Flow Control is floating so if it's enabled it can cause random lockups.

[crazydane]

I currently have the following:



So disable flow control on COM1 and while I'm there, set baud back to 115200?

[crazydane]

Made those 2 changes and after going back into setup mode and then exiting again, the Dashbox can finally see the GEM again.

[ben]

Made those 2 changes and after going back into setup mode and then exiting again, the Dashbox can finally see the GEM again.

Flow Control was definitely the issue. Should be good now.