Lost communication with GEM

[FastFreddi]

Hello, I have two GEM monitors. One of them decided to stop communicating. The COM version is 5.13 and ENG is 1.49. I can access the WiFi configuration page but not the GreenEye Monitor page. Dashbox reports last packet :2021-11-06 9:23:22 AM SSLP: 161831. The green light flashes red twice periodically. How should I proceed to troubleshoot?

[ben]

Hello, I have two GEM monitors. One of them decided to stop communicating. The COM version is 5.13 and ENG is 1.49. I can access the WiFi configuration page but not the GreenEye Monitor page. Dashbox reports last packet :2021-11-06 9:23:22 AM SSLP: 161831. The green light flashes red twice periodically. How should I proceed to troubleshoot?

Is it the green light on the DashBox that flashes red twice?

What F/W is the DashBox running (in the footer)?

[FastFreddi]

It's the green light on the GEM flashing red twice, not the Dashbox. Firmware on Dashbox is 4.2.4b17c.

[ben]

It's the green light on the GEM flashing red twice, not the Dashbox. Firmware on Dashbox is 4.2.4b17c.

What's the GEM settings set to? Do you have an STS cable connected or are you going over the network?

Over the Network the GEM should be set to:

- HTTP Get Primary Packet
- Data Post set to the proper settings (DashBox settings, http address set to your DashBox IP)
- Network set to the DashBox IP Port 80

If you're using STS on COM2 (COM1 pointed elsewhere):

- COM2 set to Bin-48-NET-Time
- Baud rates match on DashBox/COM2 GEM

I would check the bolded one above first if STS. Under Settings->System->Change Baudrates it'll show "Unknown Device" if there's a baudrate mismatch.

[FastFreddi]

I can't access any of the settings for this GEM (Failed to load settings, please try again. Retry). I am using the STS cable. My other GEM works fine.

[ben]

I can't access any of the settings for this GEM (Failed to load settings, please try again. Retry). I am using the STS cable. My other GEM works fine.

Did you check under Settings->System->Change Baudrates to see if it says Unkown Device? On the DashBox.

[FastFreddi]

COM1: Connected to unknown device. If this persists, check your baud rate settings or packet format.

COM2: GreenEye Monitor detected.

Both at baud rate of 115200

[Teken]

I didn’t see it mentioned but if the GEM has an Ethernet port. If so I would try to connect that way instead. It should be noted some times you may have to force the connection to 10 / 100 vs 1000 on a managed switch.

If the unit is connected via Ethernet do not go by the fact it doesn’t appear as a online device this is a hardware bug.

Just power cycle the GEM and wait 10-20 seconds for the network to connect. It should be noted if the GEM has been assigned a static IP address you should double check there isn’t any IP conflicts on the network causing this issue.

Ideally, all network appliances should be left in DHCP mode and the IP addresses should be reserved based on each devices MAC address.

This avoids IP conflicts, ease of management, and insures network changes can be pushed with less headaches.

[ben]

COM1: Connected to unknown device. If this persists, check your baud rate settings or packet format.

This shows that the DashBox can't understand the packets coming in due to a baud rate mismatch. Try switching COM1 to 19200 and see if it comes back up.

We may have a bug that's putting COM1 at 115200 when it's set to 19200. I'll have to look into it.

A workaround for this issue is to swap the STS cables on the DashBox-end (the stereo plugs), set COM1 to 115200 and COM2 to 19200 on the DashBox-end. The bug is likely to do with the RF code residing on COM1.

[FastFreddi]

Connecting to the ethernet port still allows access to the AP/STA configuration page (10.0.1.12:80) but still can't access the GEM configuration page (10.0.1.12:8000). Also when I try to connect using the GEM Network Utility, it can find the GEM on the network but when I connect to it I get "Response error 2 0 Response Date ="

Code: Select all

Requesting GEM Serial Number..... FAIL
Reading Settings....OK
Reading Hardware.....OK
Completed

All the items read -935 (PT Type/Range, Primary packet Fortmat, etc)

Changing the baud rate on COM1 to 19200 has restored the Dashbox connection to the GEM.

Now how can we get this working on WiFi/ethernet and get the Baud rate back to 115200?