PreRelease 4.0

TonyC

Member
The firmware on the T3 is updated to 4.2. You can start the T3 radio from the LS, just not change the settings.
 

Matt Johnson

Well-Known Member
5PLS
The firmware on the T3 is updated to 4.2. You can start the T3 radio from the LS, just not change the settings.

You should see the radio parameters if the radio is being detected. Can you connect the unit to RAMS?

base-setup_20220210-102555.png
 

TonyC

Member
Its an old OAF that I got to test out the 50hz rate on the IMU. It always says that even though I have updated it many times.
 

Matt Johnson

Well-Known Member
5PLS
Its an old OAF that I got to test out the 50hz rate on the IMU. It always says that even though I have updated it many times.

Ok I am not sure why it doesn't want to detect the radio. I will have to have someone else look at it. Can you leave it connected over night?
 

TonyC

Member
I will leave them on with the power supply connected as I need to use them tomorrow. The area has bad cell reception, that is why I needed the T3 base. It will work if you start the base from the LS as long as the settings are correct on the T3.
 

TonyC

Member
It looks like it is working now. I went back and retrieved the original OAF that was sent via email and loaded it into the T3.
The OAF that is currently associated with the T3 in my Javad profile was causing the problem.
 

giulio

Member
Adam said:

Base/Rover setup doesn't work for an LS base which sounds like what you are doing. Jcors isnt available for LS bases yet.
it means that, with firmware 4, I can no longer connect the two ls base / rover with the radios, I hope this is not the case
 

Matt Johnson

Well-Known Member
5PLS
it means that, with firmware 4, I can no longer connect the two ls base / rover with the radios, I hope this is not the case

A LS can still be started as a base with a radio. Adam only stated that the ability to start the base with JCORS corrections hasn't been added yet.
 

Greg Flowe

Active Member
Is anybody noticing longer than usual connection times when starting up your base. Not only getting connected to the base, but starting it. It has more than doubled, if not more. LS+ and T1M. I have updated to the latest stable firmware
 
YES, LS+ and T1m also, I upgraded the firmware on the T1m before trying. Very, very slow to connect and start the T1m base, seems 10 times slower, like its searching for all possibilities, used it on 1 job yesterday and went back to release version, and will stay there because it works. Also had difficulty getting it to use my licensed frequency.
 

Matt Johnson

Well-Known Member
5PLS
Is anybody noticing longer than usual connection times when starting up your base. Not only getting connected to the base, but starting it. It has more than doubled, if not more. LS+ and T1M. I have updated to the latest stable firmware
I believe it is reading more parameters from the base now so if you are connected through Bluetooth it takes longer.
 

Michael Stazhkov

Developer
JAVAD GNSS
I believe it is reading more parameters from the base now so if you are connected through Bluetooth it takes longer.
Not exactly. Just reading GREIS parameters doesn't take much time.
When connecting to base, It is waiting for an internal radio/cellular modem driver when it is ready and can provide information about the module.
When starting base it is waiting when the modem starts transmitting.
 

giulio

Member
I am trying the t'3 ls connection for jcors, I took another step forward: I managed to scan the qcode and register the base and the rover on jcors.
20220226_105755.jpg

20220226_105840.jpg


Now I'm stopped at the connection of the base (t'3) via wifi (not having a screen like Ls I don't know how to connect it to the wifi router and how to enter the wpa2 code)

20220226_105735.jpg
 
Top