Michael, my name is Steve Hankins and I am a JAVAD user. I am contacting you after a conversation I had with Shawn Billings about a problem I have with my LS (SN 0687) and my Triumph 2, (SN 01758). I have a few issues. I created a new project, (032-2017), and set the coordinate system to NAD 83(2011) Arkansas South, started the job as normal with an autonomous position and collected (17) positions, all without any problems. I returned to the base and connected to start the base file download to the LS, I received an error warning that the task could not be completed, but once I acknowledged the warning it appeared the base was downloading to the LS. I let it finish what I thought was the download by watching the icon in the upper right corner of the display, cycle and count down to completion. I returned to the office later that evening and attempted to DPOS the file. The raw file did not appear to be present in the DPOS screen, so I set the LS and T-2 up on my desk and connected again through base rover setup and downloaded the file. Once again it appeared to download as I watched the the counter progress from 0% to 100% without an issue. I connected again to DPOS to process, and again the file was not present . I rebooted the LS and cleared the NVRAM on the T-2 and tried the process again with the same result, no file. I then connected the LS to Support and completed a forced update on all of the software components, attempted the download again with same result, no file.I also noticed that while moving through these attempts with the LS, that my coordinate system had changed to WGS84(ITRF2008) , I made several attempts to change the system back to NAD83(2011) Arkansas South, but it would not, still reflected WGS84. I then powered down both units and removed the Microsd card, (ScanDisk Ultra PLUS 32GB HC I), and reseated it. I attempted the download process from the T-2 again and was successful this time, the file was present and I was able to DPOS. Upon completion of DPOS, while I was reviewing the point data between RTK and PPK all was well until I moved to point (16), It crashed the LS and sent me out to MicroSoft desktop. I rebooted the LS and tried the process again and experienced the same result when I attempted to view point (16). I rebooted the LS and this time went to the points screen to view the point range, 1-17, and all was well until I picked both points 16 and then 17 where the LS stated "Cannot read database object" for each point. I was able to export the full point range 1-17 via USB and complete my project. I still had the incorrect coordinate system issue as previous. I then reviewed the coordinate list in the LS and discovered I now had a duplicate NAD83(2011) Arkansas South and and old local system that I had deleted weeks ago? I deleted the duplicate system and the local and that has allowed me to change the WGS84 to the correct NAD83(2011) Arkansas South. I question how the duplicate system appeared as well as the deleted local system? I left this project, (032-2017), as is in the LS. I also unpacked an archived project to work on this weekend, (008-2016), and was able to view the point range from the points menu, but had the same message of "Cannot read database object" for the entire list, as well as this project , (008-2016), does not show up when the "Open Project from List" is activated. Also I still have an issue in that each and every time I activate the points menu the Magnificent 7 popup appears, and I am unable to disable it . The "Do not show this hint again" pick is non-responsive. I have also tried going through "Setup" to address this issue, but no luck. I am going to connect the LS to Remote Assistance this evening, Unit (0687), Password JSH1013. Thank you for your help!! Steve
Trouble with LS
- Thread starter Steve Hankins
- Start date
Nate The Surveyor
Well-Known Member
My thoughts... Having done alot of localizes.
It that you could send your troubled projects to support, and that those high amperage Javad guys will figure it out. I have sent a number of projects to support. They have gotten me "back in the fast lane" in about 2 days. Most of the time. It also helps them to find weak spots in the software.
Nate
It that you could send your troubled projects to support, and that those high amperage Javad guys will figure it out. I have sent a number of projects to support. They have gotten me "back in the fast lane" in about 2 days. Most of the time. It also helps them to find weak spots in the software.
Nate
I do not think it has to do with the project itself. I have seen this kind of thing recently with another customer. I had him do a factory recovery and it has seemed to fix the problem. I am not saying that this is the only fix but it may resolve your issue. I would wait and see if one of the developers could weigh in before doing the factory recovery. It is not a hard process but we need to try and figure out what is happening and try and stop it before it starts.
The "Do not show this hint again" pick is non-responsive.
I connected and took a look. I had no problem checking the "Do not show this hint again" box. Are you sure you were tapping the middle of the checkbox?
I question how the duplicate system appeared as well as the deleted local system?
All the coordinates system that are contained in a project that are not present in the list of coordinate systems will be loaded when a project is opened.
I connected and took a look. I had no problem checking the "Do not show this hint again" box. Are you sure you were tapping the middle of the checkbox?
I question how the duplicate system appeared as well as the deleted local system?
All the coordinates system that are contained in a project that are not present in the list of coordinate systems will be loaded when a project is opened.
I tried turning hints off on Steve's LS too. Would not stay off.
I think Steve's project became corrupted somehow.
Steve, it seems that your file system on the internal memory is corrupted. At least corrupted the database where projects list is stored. There are some errors during creating of the full backup and the backup doesn't contains any projects. Fortunately I was able to download projects and other folders through RAMS and have restored full backup. It seems it is OK (see private conversation).
I recommend to use recovery SD, during recovery it will format internal memory. After that your can restore your data using the data backup. If you will have the same problem after that I recommend to do RMA.
Do each project backup before sending it to DPOS as DPOS applying is a massive database operation and if there are any problem with file system a project database can be corrupted.
Thank you Michael, Matt S., Matt J. and Shawn. I will proceed with you direction, and thanks again for the quick and complete response, just outstanding!!
Gentlemen, I apologize for my ignorance, but can you detail for me the procedure to" restore your data using the data backup". I have downloaded the attachment Michael sent and placed it on a USB, just not sure of the steps to take to restore.
Thanks Shawn for the reply. Now issue No.2! I made the recovery SD just fine, removed the existing SD card, inserted recovery SD and powered up. LS steps through the recovery process until it states to remove the recovery SD and click the "Restart" button, the restart button is unresponsive. Powered down and repeated the process, same result, button is unresponsive. Any further thoughts!
Before you power back on again, remove the SD card
Is it possible that the statement "Remove SD card and click Restart button" might mean power off and the on?
Removed SD, powered LS off the back on, boots up with no current OAF. Connect to internet, then support, states no OAF, but new OAF available, click check, returns "This product is not Registered"
Go to second home screen and click system, then restore, then restore factory data.
Now that is a handy piece of knowledge to have! It would be nice to have a "cookbook" of this full recovery procedure so as not to have to impose on others. Shawn as always, thank you for your time and help, I now you have a full plate.
Happy to do it. I thought about calling you but then thought it might be good to spell it out in the thread.
Jim Frame
Well-Known Member
Michael Glutting suggested that I try a Factory Restore to see if it fixes the GNSS board problem with my RMA unit. I did a complete backup to a zip file on a USB drive, then did the restore procedure. When it finished I removed the microSD card, but the reboot button didn't respond, so I power-cycled the receiver. I then did a Restore Factory Data as described above, but when I try to backup from the zip file I get a message that says "Backup was created on another device (serial number mismatch). Only projects, tags & codes and favorites can be restored." Is there a way to get all my data restored? I'm not concerned about projects, as I have all that data backed up elsewhere. But I'd dearly love to avoid having to reconfigure all of my settings.
The instructions on how to perform a factory recovery are included in the download with the factory recovery tool. I have also attached them.
As Matt Sibole previously stated (https://support.javad.com/index.php?threads/rma-concerns.2634/#post-24315), the problem you appeared to be having was that there were many projects and DPOS sessions that were consuming all the resources when the unit was trying to boot up. This problem seems to interfere with or delay the connection to the GNSS board.
See https://support.javad.com/index.php?threads/copying-settings-from-one-ls-to-another.2617/
You can restore Tags and Codes, Profiles, C.S. Favorites, All Projects (or One Project Only) from a full backup from another unit.
Jim Frame
Well-Known Member
Except the same problem showed up after the factory reset.
By "factory reset" you mean you did a factory recovery from the SD card and then did "Restore Factory Data" (System>Restore) and then still had the issue after rebooting?
Jim Frame
Well-Known Member
Yes. I plan to leave it off overnight and see if the problem persists in the morning. If it does, Michael said he'd get another RMA going.