Dashbox not seeing any data or GEMs

[tiredinva]

I recently setup two GEMs with Ethernet. On the GEMS themselves, the live data it is showing values for wattage consumed but I'm unable to see anything within Dashbox.
Could use help on how to proceed, I tried various combinations including connected the STS cable to COM2 and connected the Red wire to RX / White to TX / Black to Ground on both GEMS
I'm including the various config I tried with no luck and screenshots, would appreciate any help
GEM Configuration

Packet Send
1. Tried HTTP Get in Primary Packet format with Secondary format disabled
2. Tried Bin48-Net-Time in Primary Packet format with Secondary format disabled
3. Tried Bin48-Net-Time in Primary Packet format with Secondary format Bin48-Net-Time
4. All of the above with timeouts of 5 and 8 seconds
5. Number of ECM-1240 devices to simulate (1 to 5): Tried 1 and 3


Data Post
1. Dashbox / Stand Alone
1. Entered IP of Dashbox, left the URL extension as is
2. Tried with all 32 channels enabled and disabled


Advanced
1. Com1 Flow set to enabled and Com1 set to disabled. The manual seemed to indicate that’s required to be enabled for Ethernet

Status




GEM Network Config
1. Server port set to 8000 for both GEMS
2. Server port set to 8001 for one GEM and 8002 for the second GEM. After doing this the GEM network utility can no longer connect to the GEM nor can I using the browser.
3. Tried idle timeout set to 2, 3 and 5

Dashbox Configuration

1. With only Ethernet I showed no GEMS detected

2. After connecting STS / COM2 cable I saw one GEM but no data

3. Tried clear memory per another post https://www.brultech.com/community/view ... =41&t=2303 in the forum and now show no GEMs detected http://dashbox-ip/index.php/pages/settings/clearMemory

[ben]

Looks like you're just missing the network config portion.

- Download the GEM Network Utlity: https://brultech.com/software/files/dow ... _8.01_.exe
- Set Server IP to the DashBox IP, Remote Port to 80 (HTTP) or 8001/8002 (Bin-32-NET)
- Leave in Mixed Mode
- Set Idle Time less then your Packet Send Interval.

STS cable-wise, COM1 of the GEM typically runs at 115200, COM2 at 19200. Set the baud accordingly. If hooked up to COM1, don't hook up the Rx as it'll conflict with the Ethernet module.

[tiredinva]

Made some progress.
Set the baud rate to 19200 and the ports to 8001 and 8002. I can now see both of them in the baud rate page
RS232 #1: GreenEye Monitor detected.
RS232 #2: GreenEye Monitor detected.

But the overall energy monitors page is still blank
Energy Monitors Added: No data available in table
Detected Energy Monitors: No monitors currently reporting data.

[ben]

Made some progress.
Set the baud rate to 19200 and the ports to 8001 and 8002. I can now see both of them in the baud rate page
RS232 #1: GreenEye Monitor detected.
RS232 #2: GreenEye Monitor detected.

But the overall energy monitors page is still blank
Energy Monitors Added: No data available in table
Detected Energy Monitors: No monitors currently reporting data.

What packet format are you sending?

Does http://dashbox-ip:8001/ bring up the GEM Setup Webpage? (replace DashBox IP with the actual IP).

What COM Port GEM-side are the STS cables connected to?

[tiredinva]

What packet format are you sending?
Format 4 - Bin48-NET-Time

What COM Port GEM-side are the STS cables connected to?
Both are connected to COM2

Does http://dashbox-ip:8001/ bring up the GEM Setup Webpage? (replace DashBox IP with the actual IP).
Yes and No,
http://dashbox-ip:8001/ spins forever
http://dashbox-ip:8002/ shows the login page

Also
if I try to access the first GEM (the one associated with port 8001) from a web page it pauses and then returns a binary response
if I try to access the second GEM (the one associated with port 8002) from a web page it shows me the regular setup page

[ben]

What packet format are you sending?
Format 4 - Bin48-NET-Time
What COM Port GEM-side are the STS cables connected to?
Both are connected to COM2

Does http://dashbox-ip:8001/ bring up the GEM Setup Webpage? (replace DashBox IP with the actual IP).
Yes and No,
http://dashbox-ip:8001/ spins forever
http://dashbox-ip:8002/ shows the login page

Also
if I try to access the first GEM (the one associated with port 8001) from a web page it pauses and then returns a binary response
if I try to access the second GEM (the one associated with port 8002) from a web page it shows me the regular setup page

Sounds like the Rx line on GEM1 isn't in all the way/loose since the Tx is working. 8002 is communcating fine.

I would switch to Bin-32-NET on Primary Packet Format and set Secondary Packet Format to Disabled so it repeats Bin-32-NET.

- Reboot the DashBox (Settings->System->Reboot DashBox)
- Refresh your browser tab
- Check Settings->Energy Monitors and Settings->System->Change Baudrates.

[tiredinva]

I reseated the COM wires + switched the packet format and it is working correctly now (not sure which of the two resolved the issue). Thank you so much!

[ben]

I reseated the COM wires + switched the packet format and it is working correctly now (not sure which of the two resolved the issue). Thank you so much!

Good to hear. It sounds like the one the Rx wire may have been a little loose since you couldn't talk back to it.

Feel free to email or post here if you run into any other issues or have any questions.

[tiredinva]

Ben, I'm having a similar issue again. I just had the ethernet board swapped out and the dashbox is not receiving packets. The status says inactive with a message that the last packet received on 2023-06-08 6:20:22 PM, SSLP: 1452022. I can still access the GEM using the http://dashbox-ip:8001/ address and the live data button is working as it should. Dashbox is clearly communicating with the GEM just not correctly detecting the packets. No other settings were changed beyond swapped out the ethernet board.

[ben]

Ben, I'm having a similar issue again. I just had the ethernet board swapped out and the dashbox is not receiving packets. The status says inactive with a message that the last packet received on 2023-06-08 6:20:22 PM, SSLP: 1452022. I can still access the GEM using the http://dashbox-ip:8001/ address and the live data button is working as it should. Dashbox is clearly communicating with the GEM just not correctly detecting the packets. No other settings were changed beyond swapped out the ethernet board.

What's it say under Change Baud Rates on the DashBox?

Take a screenshot of Adv and Packet Send in the GEM Setup Webpage and post them, just want to make sure nothing got corrupted while swapping the module.