Problem with the latest software.

Phillip Lancaster

Phillip Lancaster

Active Member
Was on Jfield 3.0.0.93 on LS with a T1 base running via cell and 1 watt UHF. Job was to stake over a mile of property line from a job I did in 2007. Conditions was not desirable but I have been in worse with the LS running like a champ. I started and got about 1/4 mile done and it just seemed like a constant struggle for a decent fix. I am looking at station and offset to line. When I get a fix of 3 or more engines I would tape over the stated offset. Move the LS to that point and watch until 3 or more engines. But here is the kicker. I had 5 engines fix on one and it said 6.4 offset right. Taped over 6.4'. Another 5 engine fix and boom. 4.5' back the other way. Huh? So I'm thinking that its just the site I'm on and maybe the wet leaves giving it some trouble. I labor on and get to my 1/2 mile corner. I give up and call it a day. I was hoping I could finish the mile in 8-10 hours but no luck. I get a call the next day from a friend (Jon) and he tells me his LS is acting weird. Pretty much the same problem. Only in staking. Collecting a point is labored but it will work. After about an hour we both update to the latest software recommended on LS and made sure we had the latest firmware on the T1's. Jon is running radio because he's only 1/2 mile from base. I'm over one to two miles from base using cell. Same thing in the woods. Jon is in a gas line right-of-way with better sky than me. Long story short I remember that his company owns 3 LS's and asked if he has another in the truck. He does and its still on Windows. He breaks it out and boom. Side by side running the same time. Night and day difference. Something is rotten in the state of Denmark guys! Windows system works. Linux currently has problems fixing.
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
Did you check the "Systems & Signals Tracking" screen (press Setup hardware button twice > GNSS > Systems & Signals Tracking to confirm that all GPS and GLONASS signals are enabled?

RTK engine performance is determined by the GNSS firmware and should not related to OS or J-Field version. Both Linux and WinCE have the same release version of GNSS firmware, 3.7.4.180724. Is this what Jon had on both units in the side by side comparison or not?
 
Phillip Lancaster

Phillip Lancaster

Active Member
Yes. They were all on. I turned off all except gps and glonass hoping that tracking the other signals would free up some processing power. I also tried the button on the bottom of that screen and other things. Still didn't work.
 
S

Steve Hankins

Active Member
5PLS
I also had a bad day with the LS today. On Pre-release, JField 3.0.0.199, GNSS 3.7.4.180724, Linux OS 4.4.110.29, Triumph 2 base. The LS was no where up to it's usual capability today. I started about 10:00 am this morning and shut down around 4:00 pm. In wide open field in Boundary profile, over 18 minutes for the first session to complete, and another 20 min. for the second. Any attempt near canopy, (edge of field with clear sky for 270°, canopy to my back), was a total fail after 40 min. In the canopy was also a fail. I have checked the GNSS Systems and Signals Tracking, and all GPS and Glonass are on. I tried disabling Glonass, and then trying to collect, never got out of Phase I. Something is very different. I love this system and have it in my hand dailey. I am intimate with this setup, and have been amazed as to it's capability. Something is most definitely wrong. Unit, software, constellation? I was in contact with (4) other users of this system today, all experienced the same issues. What say anybody!
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
Steve Hankins said:
In wide open field in Boundary profile, over 18 minutes for the first session to complete, and another 20 min. for the second. Any attempt near canopy, (edge of field with clear sky for 270°, canopy to my back), was a total fail after 40 min. In the canopy was also a fail
Click to expand...

Do you have raw data files from these points that you can share?
 
Shawn Billings

Shawn Billings

Shawn Billings
5PLS
Can you send me the project archive Steve? Also were all of the points you collected affected by this or only some? If only some, let me know which ones.
 
S

Steve Hankins

Active Member
5PLS
Shawn Billings said:
Can you send me the project archive Steve? Also were all of the points you collected affected by this or only some? If only some, let me know which ones.
Click to expand...
File to large to post here, sent to you by way of Google Drive. All points were somewhat affected. Thank you and Matt for your help.
 
Darren Clemons

Darren Clemons

Well-Known Member
It seems, without a doubt, there is a real, quite serious issue with the Linux migration. With this thread started by Phillip, a long time and experienced user and corroborated by several, as well as Nate and Clay in the other thread, I’d be proned to say: Houston - we have a problem!!!

We have four LS’s, three T1M/LS combos and a 4th LS as an RTN rover. I have one system that is still on Windows and the other three are all on Linux. I am going to take the Windows unit along side one of the Linux units to one of our typical deep, dark places soon to test Philip’s scenario. The two complete systems I’ve migrated have not, as of yet, seemed to exhibit the type behavior I’m reading here. It’s always difficult to say, exactly, if things are “like they should be”, when working where we work in mid August. Sometimes the nastiest spots get results in minutes, sometimes marginal spots take forever.

The newest LS I purchased is another story all in itself, as it’s had major problems since day one - on BOTH Windows and Linux. The internal compass is somehow faulty leading to impossible CTT arrow and staking abilities; it’s constantly had the ghost clicks and crazy screen issues; many times it has “lost” its authorization files leading to the flashing red sat icon. It was finally determined that I’d be issued a replacement LS two weeks ago but, as of now, I still haven’t received it.

I have been heavily, intimately involved in this board for three years now and would have to say to everyone who reads, uses, designs, analyzes, supports and sells Javad equipment: Ladies and gentlemen, we are at a very, very important juncture in the life of the LS and it’s next stage. Up until about a year ago, there was about as little as I’ve ever dealt with as far as problems with equipment was concerned. This tremendous, wonderful piece of “magic” worked like nothing we’ve ever used before - and I trust that it will again.

The Linux migration was, without a doubt, a massive undertaking and there were sure to be major issues along the way but hopefully the design team can slowly get all the wrinkles out and we’ll have our systems back better than ever. Obviously, whatever the issues are, the more raw data and project files shared with the team the better so they can continue to analyze and determine the issues and fix them. In other words, and I’m saying this to myself more than anything, let’s be patient and hope the design team can get things in order.

I, most certainly, can be very impatient and critical at times but having all the issues I had yesterday with discussing my RMA status and lack of my replacement LS with Matthew, I was reminded of 3 years ago, not long after we purchased our 1st unit. Beast mode was just being released in Jfield and my, my the first few weeks were interesting to say the least. But after a little time, several updates and working the bugs out, it transformed the entire system into - well, a beast!!

Let’s hope that everyone involved in design, shipping and support will work on and concentrate on the things that are most important and critical to us, the users. Hopefully, all the Linux issues will be resolved soon, Galileo will be implemented in Jfield and our “beast” will be back growling like never before.
 
S

Steve Hankins

Active Member
5PLS
Steve Hankins said:
I also had a bad day with the LS today. On Pre-release, JField 3.0.0.199, GNSS 3.7.4.180724, Linux OS 4.4.110.29, Triumph 2 base. The LS was no where up to it's usual capability today. I started about 10:00 am this morning and shut down around 4:00 pm. In wide open field in Boundary profile, over 18 minutes for the first session to complete, and another 20 min. for the second. Any attempt near canopy, (edge of field with clear sky for 270°, canopy to my back), was a total fail after 40 min. In the canopy was also a fail. I have checked the GNSS Systems and Signals Tracking, and all GPS and Glonass are on. I tried disabling Glonass, and then trying to collect, never got out of Phase I. Something is very different. I love this system and have it in my hand dailey. I am intimate with this setup, and have been amazed as to it's capability. Something is most definitely wrong. Unit, software, constellation? I was in contact with (4) other users of this system today, all experienced the same issues. What say anybody!
Click to expand...
A follow up to yesterday's post. I went to the field this afternoon to try my luck once again. No changes were made to the LS, everything just as yesterday. The LS worked perfectly in collect, stake point, and stake to a line. I ran through each of these in the open, moderate canopy, and heavy canopy. Worked as well as it ever has. I have to figure the problem of yesterday was not with the LS, must be from the constellations or other interference. Thanks to Shawn, Matt and others for the help, the beast was back today!
 
Clay Davidson

Clay Davidson

Active Member
Well mine ran like ......terrible today. I was in a deep holler and only got 2 shots with rtk. Mostly did 10min repeated static shpts today. And they wouldn't depos. So I guess I'll check ot in the morning. Good thing I wasn't staking out. Most of the shots were 30 minutes and only had a couple of rtk shots with 2 to 3 seconds.
 

Attachments

  • 20180816_124842.jpg
    20180816_124842.jpg
    4 MB · Views: 337
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
I find that GNSS 3.7.4 firmware does not do as well with tracking GNSS signals as older firmware. Stay tuned, there will probably be some update tomorrow.
 
Clay Davidson

Clay Davidson

Active Member
I just updated the gnss to version 3.6.13. I haven't done a field check.

I did do some field work in 3.6.13 prior to udating to 3.7 and I thought it did ok. Definitely better then 3.7
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
Darren Clemons said:
Pre release will back me up to version 3.6.13
Would it be a good idea to try that?
Click to expand...

The tracking with this firmware is good. The "Systems & Signals Tracking" screen will not work properly with older firmware and the current version of J-Field. There will probably be an updated version of J-Field soon to fix the compatibility issue.
 
You must log in or register to reply here.
Top