jss wrote: ↑Sat Jan 01, 2022 6:25 pm
I have a dashbox and two GEMs connected via serial. I upgraded the firmware from 4.2.4a19 to 4.2.4b1 to 4.2.4b17c. After the update, one GEM box continues to work fine (CT2) and the other appears to be sending packets (CT1) but it fails to load settings after using the
Settings button.
Observations
- http://<ipaddr>:8002 works; http://<ipaddr>:8001 does not work.
- Baudrates for both (115200) did not change during the update. Both were purchased at the same time so should be at the same levels of COM software (v4.36).
- The System LED for CT2 is green with a fast red blink every few seconds. The System LED for CT1 is green then two slow red blinks followed by off.
- On the Settings page, the data/time for last packet is updating for CT2 and not for CT1.
- The SSLP for both GEMs is updating on a 5-second interval. SSLP for CT1 is typically 1, always under 5. SSLP for CT1 is increasing by 5 each interval. Does SSLP stand for "Seconds since Last Packet"?
Questions
- Where do I find out how to read these LEDs? The documentation that I have found only states that the left LED is the "System LED" but doesn't say how to read the states.
- What are my next steps to restore this box to a working state?
SSLP is Seconds since last packet, correct.
I'll have to ask Paul where he stuck the LED statutses but normal System LED operations are:
- Blinking red constantly is no PT connected.
- Solid Green is operational.
- Single red flash is the packet leaving the device.
Anything outside those 3 signals should be sent to us for debugging.
The red/off signal may be it trying to communicate with a communication module but it can't.
Do you have a communication module (WiFi, WiFi/Ethernet, Ethernet, etc) on CT1 and do you have the STS cable connected to COM1 GEM-side? If so, the STS cable and communication module will be competing for the Rx signal. This would be why it's still transmitting but not receiving commands when you try to pull settings.
