Lost communication with GEM

[ben]

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?

If you have WiFI/Ethernet, make sure your STS cables are connected to COM2 on the GEM. Connecting the STS cable to COM1 on the GEM may clash with the WiFi/Ethernet module.

COM2 GEM-side is generally set to 19200 in order to support an optional Zigbee module.

In the AP/STA page, under Application Settings, what is your configuration on the port? GEM COM1 will always run at 115200 unless it's been changed.

[FastFreddi]

Ok STS switched to COM2.
On application settings:
Baud rate 115200 / Data Bit 8 / Parity none / Stop 1 / CTSRTS Disable

UART AutoFrame disable

Mode Server / Protocl TCP / Port 8000 / Server Address blank / MaxTCP 32 / TCP timeout 300

[ben]

Ok STS switched to COM2.
On application settings:
Baud rate 115200 / Data Bit 8 / Parity none / Stop 1 / CTSRTS Disable

UART AutoFrame disable

Mode Server / Protocl TCP / Port 8000 / Server Address blank / MaxTCP 32 / TCP timeout 300

Try accessing http://10.0.1.12:8000/ now that the STS cable isn't on the same COM port.

Is the end-goal to have the GEM send to the DashBox without the STS cable?

[FastFreddi]

It still does not work. I want the ability to connect through Wifi to integrate with HomeSeer for some automation triggers. Also would like my system to function as it did before. The red light on the GEM keeps blinking twice, two long flashes as opposed to one short red flash on my other GEM which is functioning properly.

[ben]

It still does not work. I want the ability to connect through Wifi to integrate with HomeSeer for some automation triggers. Also would like my system to function as it did before. The red light on the GEM keeps blinking twice, two long flashes as opposed to one short red flash on my other GEM which is functioning properly.

The DashBox can be used to connect to the GEMs also thru 8001/8002 (RS232 #1/RS232 #2).

Can you try:

http://DashBox-IP:8001/ or http://DashBox-IP:8002/

Whichever RS232 the problem GEM is set to.

If you can get in there screencap the Status page and let me know what it says there.

[FastFreddi]

Ok that's great I manage to get in.

Code: Select all

Serial#: 01120803
COM firmware ver: 5.13
ENG firmware ver: 1.49
RealTime Status: ON
Packet Send Interval: 5
Pri. Packet Format: 0
Sec. Packet Format: 4
Sys Status: OK

Code: Select all

Wifi/Ethernet Module: Enabled
GEM Ver: Single Phase Only
PCB Ver: 3
BootLoader Ver: 2
COM1 Flow: OFF
COM2 Flow: OFF
Current Constant: 221
Sys Info: 00100001 OK
Sys Flags: 00000000 OK

Code: Select all

Keep Alive String:""
COM1 Baud: 19200
COM2 Baud: 115200
Phase Setting: Single Phase
Freq: 60Hz
Hardware Configuration: 166
WiFi and Ethernet V2

[ben]

Ok that's great I manage to get in.

Code: Select all

Serial#: 01120803
COM firmware ver: 5.13
ENG firmware ver: 1.49
RealTime Status: ON
Packet Send Interval: 5
Pri. Packet Format: 0
Sec. Packet Format: 4
Sys Status: OK

Code: Select all

Wifi/Ethernet Module: Enabled
GEM Ver: Single Phase Only
PCB Ver: 3
BootLoader Ver: 2
COM1 Flow: OFF
COM2 Flow: OFF
Current Constant: 221
Sys Info: 00100001 OK
Sys Flags: 00000000 OK

Code: Select all

Keep Alive String:""
COM1 Baud: 19200
COM2 Baud: 115200
Phase Setting: Single Phase
Freq: 60Hz
Hardware Configuration: 166
WiFi and Ethernet V2

Yeah, set COM1 Baud to 115200 under Adv on that same Setup Webpage. That should get the WiFi/Ethernet module going.

[FastFreddi]

Yup that did it, thanks. I had forgotten that I could access this page through Dashbox.

[ben]

Yup that did it, thanks. I had forgotten that I could access this page through Dashbox.

Good to hear, let me know if you run into any other issues getting it back setup.