GEM fatal error
-
- Posts: 37
- Joined: Tue Jan 14, 2014 3:31 pm
Re: GEM fatal error
See short video at this link for the lights on the GEM
-
- Site Admin
- Posts: 4266
- Joined: Fri Jun 04, 2010 9:39 am
Re: GEM fatal error
Have you made sure the cable hasn't fallen out?
Does it still say no device detected?
The GEM is definitely sending packets.
Does it still say no device detected?
The GEM is definitely sending packets.
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Brultech Research Inc.
E: ben(at)brultech.com
-
- Posts: 37
- Joined: Tue Jan 14, 2014 3:31 pm
Re: GEM fatal error
Yes. I have checked the cable is plugged in.
-
- Site Admin
- Posts: 4266
- Joined: Fri Jun 04, 2010 9:39 am
Re: GEM fatal error
Have you rebooted both the GEM and DashBox? I can't see any reason why it's not communicating.
If it's still down after:
- Remove the STS cable from the GEM
- Twist the Tx/Rx sides together
- Open the IP/Port in the GEM Network Utility
- Go to the Debug tab
- Just send random characters and they should be echoed back
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Brultech Research Inc.
E: ben(at)brultech.com
-
- Posts: 37
- Joined: Tue Jan 14, 2014 3:31 pm
Re: GEM fatal error
I've already tried the network utility. While it says it is connected to the gem, it won't get any info from it. The firmware button does nothing. The debug tab gets no response.
I'm away for 2 weeks, but when I get back I will try removing the sts cable and doing that twist thing.
There is only 1 gb of room on the sd card in the dashbox, could that be causing this?
I'm away for 2 weeks, but when I get back I will try removing the sts cable and doing that twist thing.
There is only 1 gb of room on the sd card in the dashbox, could that be causing this?
-
- Site Admin
- Posts: 4266
- Joined: Fri Jun 04, 2010 9:39 am
Re: GEM fatal error
agr077 wrote: ↑Tue Aug 16, 2022 4:02 pmI've already tried the network utility. While it says it is connected to the gem, it won't get any info from it. The firmware button does nothing. The debug tab gets no response.
I'm away for 2 weeks, but when I get back I will try removing the sts cable and doing that twist thing.
There is only 1 gb of room on the sd card in the dashbox, could that be causing this?
SD card space won't have any issue with communication, it'll run down to ~0.4GB before stopping data logging but you'd still be able to pull settings.
The GEM Network Utility will be able to connect to that port regardless of the status of the GEM. All it's doing is bridging the TCP port to the serial port, so the issue has to either be the STS cable connection or the GEM itself.
Since you're not getting the "Unknown Device" anymore under Settings->System->Change Baudrates regardless of 19200 or 115200 baud it sounds like something happened with the physical connection back to the GEM. From your video the GEM is sending packets. "Unknown Device" shows up whenever the DashBox gets something in that it can't interpret.
I'm thinking the Tx wire is loose on the GEM-side.
Reading thru earlier posts,
Did you check the 3-wires on the GEM end? One or many of those 3 wires may have become loose if they weren't inserted all of the way.agr077 wrote:Yes. I have checked the cable is plugged in.
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Brultech Research Inc.
E: ben(at)brultech.com
-
- Posts: 37
- Joined: Tue Jan 14, 2014 3:31 pm
Re: GEM fatal error
I did check the cable connection on the GEM. I undid and redid it and it looks to be fine.
Last edited by agr077 on Sat Sep 03, 2022 5:38 am, edited 2 times in total.
-
- Site Admin
- Posts: 4266
- Joined: Fri Jun 04, 2010 9:39 am
Re: GEM fatal error
Colour code looks fine too. COM2 runs at 19200 by default so set the baud to that. COM1 runs at 115200.
Sorry, by wire twist I mean remove it from the GEM and just touch the ends together. You're creating a loop between Tx and Rx by doing so. After when you go into the GEM Network Utility Debug tab anything you send with the command boxes on the left should echo back. This will tell you whether or not the STS cable has an issue.
Sorry, by wire twist I mean remove it from the GEM and just touch the ends together. You're creating a loop between Tx and Rx by doing so. After when you go into the GEM Network Utility Debug tab anything you send with the command boxes on the left should echo back. This will tell you whether or not the STS cable has an issue.
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Brultech Research Inc.
E: ben(at)brultech.com
-
- Posts: 37
- Joined: Tue Jan 14, 2014 3:31 pm
Re: GEM fatal error
ok. I took the white and red out of the GEM and twised them together. On the GEM network utility on my window pc I hit a couple of the commands in the debug tab and nothing happened except that the command appears once in the screen.
Does this mean the cable somehow went bad or does the command appearing once indicate the cable is good?
Does this mean the cable somehow went bad or does the command appearing once indicate the cable is good?
-
- Site Admin
- Posts: 4266
- Joined: Fri Jun 04, 2010 9:39 am
Re: GEM fatal error
That means the cable is good, you're just looping back what's sent.agr077 wrote: ↑Fri Sep 02, 2022 2:16 pmok. I took the white and red out of the GEM and twised them together. On the GEM network utility on my window pc I hit a couple of the commands in the debug tab and nothing happened except that the command appears once in the screen.
Does this mean the cable somehow went bad or does the command appearing once indicate the cable is good?
Plug it back into the GEM.
Are you able to port forward to the DashBox? If you can email me and give me access to Port 9500 on the DashBox I can see if I can figure it out.
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Brultech Research Inc.
E: ben(at)brultech.com