All 4 engines synchronized???

avoidthelloyd

Active Member
I’ve had this happen twice now. LS+ and T3. The engines sync and it won’t take a shot. We haven’t been close enough to the base to restart it but rebooting the LS don’t help.

Right now my other unit is working fine on the T2 base. Last time, I had @Shawn Billings - Javad login to RAMS and had no success, but it just started working again after a couple of hours. We sent the project to the engineers. Any thoughts?

082B9383-AD09-453C-BDC9-A7221DAA534C.jpeg
 

avoidthelloyd

Active Member
Bud walked out of the wood quarter mile to the truck and it was still not working there, but by the time he got to the T3 it was back to usual.
 

Wes Hand

Active Member
I have seen this when switching back and forth from an RTN to my base. For whatever reasons the engines will not update to the various signals available. Try selecting auto setup or reset engines if it occurs again. There is a setting to auto setup engines when fixed that I think is under your action profile maybe under options but I’m not sure off the top of my head. I’ve got mine set to 35 seconds but I have still seen it not update the engines on a RTN 5 minutes later and I must manually tap the auto set up engines to get each engine to update properly.
 

avoidthelloyd

Active Member
I have seen this when switching back and forth from an RTN to my base. For whatever reasons the engines will not update to the various signals available. Try selecting auto setup or reset engines if it occurs again. There is a setting to auto setup engines when fixed that I think is under your action profile maybe under options but I’m not sure off the top of my head. I’ve got mine set to 35 seconds but I have still seen it not update the engines on a RTN 5 minutes later and I must manually tap the auto set up engines to get each engine to update properly.
I forgot to mention that resetting engines (which we do alot) and long pressing the reset engines button both didn't help. Thanks! Good thought! So far only one of my units has had this issue and it has been on UHF.
 

Shawn Billings - Javad

Active Member
JAVAD GNSS
I've seen similar issues with both UHF and cellular communication. After discussing with Matt Sibole, I think the issue is in the base and that restarting the base (possibly including clearing NVRAM) will correct the issue.

The reason all of the engines are configured the same is because they don't have enough different signals to create a varied engine profile.
 

Wes Hand

Active Member
I second Shawn on restarting the base. I’ve had days where I’ve started it and the behavior of the LS is not normal. Rebooting LS made no difference. Stopped the base and even power cycled down the base. The restart of the base fixed my issues
 

avoidthelloyd

Active Member
I wish we were working in areas that we could restart it remotely, but I bought the T3 for the rough terrain and timber where there is no cell service... catch 22. For whatever reason is causing the issue, it does seem to fix itself without a restart in time. Just not fast enough... haha.
 
Top