GEM stopped communicating with Dashbox
-
- Posts: 39
- Joined: Sun Nov 05, 2017 8:55 am
Re: GEM stopped communicating with Dashbox
Ben:
My GEM has no additional modules - just the base/serial unit. FYI, here is what the Dashbox "Change Baudrates" page looks like with the current GEM COM2 connection:
When I get a few minutes this afternoon, I will try changing the connection back to COM1.
BTW, I went back and looked at when my Dashbox stopped getting data from the GEM - and it was shortly after I updated the Dashbox to firmware 4.2.4b5 and Updater to 4.2.4b.
My GEM has no additional modules - just the base/serial unit. FYI, here is what the Dashbox "Change Baudrates" page looks like with the current GEM COM2 connection:
When I get a few minutes this afternoon, I will try changing the connection back to COM1.
BTW, I went back and looked at when my Dashbox stopped getting data from the GEM - and it was shortly after I updated the Dashbox to firmware 4.2.4b5 and Updater to 4.2.4b.
- Attachments
-
- Dashbox-Change Baudrates_2021-01-18.JPG (31.32 KiB) Viewed 3401 times
-
- Posts: 39
- Joined: Sun Nov 05, 2017 8:55 am
Re: GEM stopped communicating with Dashbox
Ben:
The Dashbox stopped getting packets when I swapped the serial cable wiring on the GEM end back to using COM1.
Paul
The Dashbox stopped getting packets when I swapped the serial cable wiring on the GEM end back to using COM1.
Paul
-
- Site Admin
- Posts: 4269
- Joined: Fri Jun 04, 2010 9:39 am
Re: GEM stopped communicating with Dashbox
Check the GEM Adv page to see if COM1 is somehow set to 19200. Doesn't look like the issue is on the DashBox-end.BigBadBuzz wrote: ↑Mon Jan 18, 2021 2:14 pmBen:
The Dashbox stopped getting packets when I swapped the serial cable wiring on the GEM end back to using COM1.
Paul
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Brultech Research Inc.
E: ben(at)brultech.com
-
- Posts: 39
- Joined: Sun Nov 05, 2017 8:55 am
Re: GEM stopped communicating with Dashbox
Ben:
COM1 was set to 19200; I don't see how it could have changed, as things had been working that way for many years. I set COM1 to 115200 via the ADV tab and moved the GEM end of the serial cable to COM1 - the Dashbox is receiving packets.
Paul
COM1 was set to 19200; I don't see how it could have changed, as things had been working that way for many years. I set COM1 to 115200 via the ADV tab and moved the GEM end of the serial cable to COM1 - the Dashbox is receiving packets.
Paul
-
- Posts: 39
- Joined: Sun Nov 05, 2017 8:55 am
Re: GEM stopped communicating with Dashbox
Ben:
Thanks for the help in tracking down the issue; I always appreciate the great service Brultech provides!
Just because I can't let things go , it still seems like something in the process of updating the Dashbox firmware caused the COM1 link from GEM to Dashbox to get changed so they no longer communicated. And, even though I had alerts set to send me messages if the Dashbox stopped getting data, I never received any.
Regards,
Paul
Thanks for the help in tracking down the issue; I always appreciate the great service Brultech provides!
Just because I can't let things go , it still seems like something in the process of updating the Dashbox firmware caused the COM1 link from GEM to Dashbox to get changed so they no longer communicated. And, even though I had alerts set to send me messages if the Dashbox stopped getting data, I never received any.
Regards,
Paul
-
- Site Admin
- Posts: 4269
- Joined: Fri Jun 04, 2010 9:39 am
Re: GEM stopped communicating with Dashbox
Were you going from a very old F/W to the newest? At one point the F/W updater only ran at 19200 so you would've had to drop the baud to 19200 for it to operate.BigBadBuzz wrote: ↑Tue Jan 19, 2021 1:29 pmBen:
Thanks for the help in tracking down the issue; I always appreciate the great service Brultech provides!
Just because I can't let things go , it still seems like something in the process of updating the Dashbox firmware caused the COM1 link from GEM to Dashbox to get changed so they no longer communicated. And, even though I had alerts set to send me messages if the Dashbox stopped getting data, I never received any.
Regards,
Paul
Give https://www.brultech.com/dashbox/dashbox_v4_2_4b10.img a try to see if the alerts work after.
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Brultech Research Inc.
E: ben(at)brultech.com
-
- Posts: 39
- Joined: Sun Nov 05, 2017 8:55 am
Re: GEM stopped communicating with Dashbox
Ben:
I believe that I updated from firmware v4.2.4a19 to v4.2.4b5a and from whatever version the old updater was to v4.2.4b1.
Regards,
Paul
I believe that I updated from firmware v4.2.4a19 to v4.2.4b5a and from whatever version the old updater was to v4.2.4b1.
Regards,
Paul
-
- Posts: 39
- Joined: Sun Nov 05, 2017 8:55 am
Re: GEM stopped communicating with Dashbox
Ben:
I updated the Dashbox firmware to v4.2.4b10. I simulated the problem I had earlier by setting Dashbox's COM1 baud rate to 19200. Alert ID 1 is enabled to send email on not receiving packets after 3 minutes - I do not receive emails. Just in case something was amiss along the email chain, I went to Dashbox's Alerts > Email page and clicked on the "Send Test email" button; I did receive an email from that.
Paul
I updated the Dashbox firmware to v4.2.4b10. I simulated the problem I had earlier by setting Dashbox's COM1 baud rate to 19200. Alert ID 1 is enabled to send email on not receiving packets after 3 minutes - I do not receive emails. Just in case something was amiss along the email chain, I went to Dashbox's Alerts > Email page and clicked on the "Send Test email" button; I did receive an email from that.
Paul
-
- Posts: 34
- Joined: Sat Dec 12, 2015 2:21 pm
- Location: Rivière-du-Loup
Re: GEM stopped communicating with Dashbox
4b10 is a beta version?
-
- Site Admin
- Posts: 4269
- Joined: Fri Jun 04, 2010 9:39 am
Re: GEM stopped communicating with Dashbox
Posted it last night, we have enough customers without issues now that it's good to go.
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Brultech Research Inc.
E: ben(at)brultech.com