Turn off IRNSS and QZSS on both T3 and LS+.
Manually programming engines for better performance, no longer using 'auto setup rtk'
- Thread starter Dragonsnake
- Start date
Thank you, Matt, for highlighting the issue with GLO P1. JAVAD acknowledges the problem, and a fix is underway.
Regards,
Vlad
Dragonsnake
New Member
That's interesting about GLO P1... I never knew it had issues... But luckily it seems that Javad is working on a fix for GLO P1. Ah, I just saw John Rosco's post, it seems this is in reference to GLO B. OK, I know how to do it now.
Matt Johnson - I have not tried setting signals to something less than unlimited but more than the default. Perhaps this may increase performance even further, and perhaps it may even allow the 8 signals per engine to be used, which then we could use your signals config again. That is a good idea, maybe I'll try 50 next time. I'll have to re-configure the engines to be 8 per engine and NOT use GLO B at the moment, did your old guide already exclude GLO B from the manual set up?
Phillip Lancaster - That's great this works for you! I had the same experience too. In fact I do a lot of wooded topo in a grid pattern for topographic maps which need really good contours for various civil engineering projects, that's why we were so interested in the Javad since it meant I didn't have to lug the total station into the horrifically shrouded-at-eye-level woods anymore. I agree with your statement about IRNSS and QZSS being disabled, I believe one of those is relevant to geo-sychned satellites over the country of India, and the other one is for Japan, meaning they ONLY work if you are physically located in those countries.
avoidthelloyd - If you find that some of the engines are grayed out, this happened to me a few times too. I had to restart both the rover and the base and try again. Sometimes I had to restart 2 or 3 times. Also I hard pressed the power off button on the rover and held it so it shut off abruptly, this might have helped. But eventually, the engines became white and clickable again. Also, if you wanted to keep using auto setup rtk engines button for some reason, you can create your own shortcut in one of the little side boxes on the collect and stake out menus that will perform the auto rtk setup command. You have to long press one of those side buttons and search around all the available options, but it's in there somewhere, I used to use it all the time before I moved to Matt Johnson's overall method of setting up engines manually.
Nate The Surveyor - I've had shots that refused to work over a reasonable amount of time, usually what I do in this situation is a 'distance, distance' offset in which I carry a handheld laser with me and take 2 shots that are 90 degrees horizontal apart from each other, then do a circle, circle intersection in autocad to accurately get the coordinates of the shot I actually wanted. Something usually like 10' on each of the legs is a reasonable amount of distance to do this. Then you use the laser to get the horizontal distance to the point you wanted, like a drill hole in a stone wall or monument (you may have to set up a rock or something to be on top of the point of interest) You can also use the javad software to create a point using a distance, distance intersection. You might want to take a bearing reading with the compass to confirm that the correct point was created, since the circles will intersect twice. Meaning, take an inverse from one of the original points that you used to create the distance, distance offset, and inverse it to the point that was created, and make sure the bearing is close to the measured bearing to confirm. It should be noted that this technique only works for horizontal placement and doesn't work for vertical.
Matt Johnson - I have not tried setting signals to something less than unlimited but more than the default. Perhaps this may increase performance even further, and perhaps it may even allow the 8 signals per engine to be used, which then we could use your signals config again. That is a good idea, maybe I'll try 50 next time. I'll have to re-configure the engines to be 8 per engine and NOT use GLO B at the moment, did your old guide already exclude GLO B from the manual set up?
Phillip Lancaster - That's great this works for you! I had the same experience too. In fact I do a lot of wooded topo in a grid pattern for topographic maps which need really good contours for various civil engineering projects, that's why we were so interested in the Javad since it meant I didn't have to lug the total station into the horrifically shrouded-at-eye-level woods anymore. I agree with your statement about IRNSS and QZSS being disabled, I believe one of those is relevant to geo-sychned satellites over the country of India, and the other one is for Japan, meaning they ONLY work if you are physically located in those countries.
avoidthelloyd - If you find that some of the engines are grayed out, this happened to me a few times too. I had to restart both the rover and the base and try again. Sometimes I had to restart 2 or 3 times. Also I hard pressed the power off button on the rover and held it so it shut off abruptly, this might have helped. But eventually, the engines became white and clickable again. Also, if you wanted to keep using auto setup rtk engines button for some reason, you can create your own shortcut in one of the little side boxes on the collect and stake out menus that will perform the auto rtk setup command. You have to long press one of those side buttons and search around all the available options, but it's in there somewhere, I used to use it all the time before I moved to Matt Johnson's overall method of setting up engines manually.
Nate The Surveyor - I've had shots that refused to work over a reasonable amount of time, usually what I do in this situation is a 'distance, distance' offset in which I carry a handheld laser with me and take 2 shots that are 90 degrees horizontal apart from each other, then do a circle, circle intersection in autocad to accurately get the coordinates of the shot I actually wanted. Something usually like 10' on each of the legs is a reasonable amount of distance to do this. Then you use the laser to get the horizontal distance to the point you wanted, like a drill hole in a stone wall or monument (you may have to set up a rock or something to be on top of the point of interest) You can also use the javad software to create a point using a distance, distance intersection. You might want to take a bearing reading with the compass to confirm that the correct point was created, since the circles will intersect twice. Meaning, take an inverse from one of the original points that you used to create the distance, distance offset, and inverse it to the point that was created, and make sure the bearing is close to the measured bearing to confirm. It should be noted that this technique only works for horizontal placement and doesn't work for vertical.
Dragonsnake
New Member
Matt, you're a genius! I set all the engines to max signals 60, and then I took out GLO P1 since you and also someone from javad said it was currently bugged and would mess up any engine it was put into. I also took out USA C since it only shows up in my list of available signals sometimes, and when it does, it is always a low, red color quality like signal strength 2, much less than the other signals which are usually green or blue and have numbers like 6, 7, 8, etc.
So after doing that, I put all the engines to 8 signals each, with the following config:
Engine 1
USA A
BDS E
GAL E
BDS B
BDS D
GAL D
USA F
GLO D
Engine 2
BDS E
USA A
GAL A
BDS A
USA B
GAL F
USA E
GLO C
Engine 3
BDS B
GAL E
GAL A
BDS A
USA D
GAL C
GLO A
BDS F
Engine 4
GAL D
BDS D
USA B
GAL F
USA E
GAL C
USA D
BDS C
This actually works great! I had a job where I had to locate a dirt pathway in heavily forested, dense woodlands and it worked awesome! I was even able to carry elevations. I was surprised how good it worked. I think the problem I had before was I put the max signals to 'unlimited' which is what was causing the rover software to chug to uselessness out in the open, but putting the cap at max signals 60 seemed to help there.
This is the best config I've ever used, I wonder why Javad doesn't make something like this the default option for signals set up? Works way better than auto set up as far as I can see, and no risk of the rare bug in which all engines are set to the same signals. Maybe they think it will overclock the processor or something and cause heat and stability issues. But this config works fine I used it all day today.
Sadly the message board is not letting me edit my first post so hopefully people will see this new config here on the 2nd page.
So after doing that, I put all the engines to 8 signals each, with the following config:
Engine 1
USA A
BDS E
GAL E
BDS B
BDS D
GAL D
USA F
GLO D
Engine 2
BDS E
USA A
GAL A
BDS A
USA B
GAL F
USA E
GLO C
Engine 3
BDS B
GAL E
GAL A
BDS A
USA D
GAL C
GLO A
BDS F
Engine 4
GAL D
BDS D
USA B
GAL F
USA E
GAL C
USA D
BDS C
This actually works great! I had a job where I had to locate a dirt pathway in heavily forested, dense woodlands and it worked awesome! I was even able to carry elevations. I was surprised how good it worked. I think the problem I had before was I put the max signals to 'unlimited' which is what was causing the rover software to chug to uselessness out in the open, but putting the cap at max signals 60 seemed to help there.
This is the best config I've ever used, I wonder why Javad doesn't make something like this the default option for signals set up? Works way better than auto set up as far as I can see, and no risk of the rare bug in which all engines are set to the same signals. Maybe they think it will overclock the processor or something and cause heat and stability issues. But this config works fine I used it all day today.
Sadly the message board is not letting me edit my first post so hopefully people will see this new config here on the 2nd page.
Dear friends,
We are at the final stage of testing the fix. We hope you will like the improvements made.
We will let you know in this thread when the pre-release version of J-Field with firmware is available for you.
Have a great day,
Vlad
We are at the final stage of testing the fix. We hope you will like the improvements made.
We will let you know in this thread when the pre-release version of J-Field with firmware is available for you.
Have a great day,
Vlad
Dear JAVAD Friends,
We are pleased to announce that a new version of GNSS Firmware (4.2.0.4) and J-Field (4.0.1.671) is now available on the Pre-Release branch.
This pre-release includes essential fixes and improvements. Please see the release notes below for full details:
Please share feedback with us on how the pre-release version works for you.
Have a great day,
Vlad
We are pleased to announce that a new version of GNSS Firmware (4.2.0.4) and J-Field (4.0.1.671) is now available on the Pre-Release branch.
This pre-release includes essential fixes and improvements. Please see the release notes below for full details:
Please share feedback with us on how the pre-release version works for you.
Have a great day,
Vlad
Last edited by a moderator:
Nate The Surveyor
Well-Known Member
I just fixed it. It should be visible now.
Thank you, Matt!
I think this just means that it is not possible to view the public IP address of a base connected to the internet through the cellular modem. It shouldn't affect the ability to use a Jetpack.
JFIELD reports the 'Remote-Base' IP Address configuration information, which may not be the Internet Static IP-Address that is required to remotely access 'the base' . . .
Updated this today, and it's a huge improvement over past updates. Totally recommend people updating their LS+'s!!! Love the new engine configuration. Big improvement! Repeatedly got 2.2+ variety within 1 or 2 seconds. It stayed in a multiple engine fix longer than the past updates. I still think it could be better. Well, I know it could be better because I ran it when it was better. I am Happy, Happy, Happy!!!
Nate The Surveyor
Well-Known Member
Does JERCI still work, on this update?
Nate
Nate
Greg Flowe
Active Member
Nate, It does still connect on mine with the pre release
Jim Frame
Well-Known Member
"JFIELD reports the 'Remote-Base' IP Address configuration information, which may not be the Internet Static IP-Address that is required to remotely access 'the base' . . ."
I'm still confused. If it's just reporting a different IP without interfering with the Jetpack connection that'd be okay, and Matt says he *thinks* this won't affect static IP Jetpack use, but I reckon I'll hold off on the update under the "if it ain't broke" theory.
I'm still confused. If it's just reporting a different IP without interfering with the Jetpack connection that'd be okay, and Matt says he *thinks* this won't affect static IP Jetpack use, but I reckon I'll hold off on the update under the "if it ain't broke" theory.
See Thread 'LS+ Action Profile Settings'