We renewed our license in January and received the dongle with the new license. The dongle is one issue! My biggest issue is desktop not processing my data. I have been flying the R360 for a couple years now and the R2A for a year prior. I would say that after 100+ LiDAR projects we have the initialization and ending procedures down. Rule out those factors…… ever since we updated to the first desktop version for muse with the dongle we have had nothing but trouble. I have updated rock desktop every time there is an update. The R360 is also up to date. So can’t be the fact that software isn’t up to date. Since January we have flown several projects…. Over and over and over again. We run 2 Emlid bases just for redundancy and every time we process we get errors using both sets of base data. Sometimes it’s the second, third or last time fourth attempt at collecting the data and we will get luck and it will process. However the processing report show that my data should be trash because of bad PDOP and tightly coupled solutions are all over the place…. When comparing the cloud to control and ground truthing the data looks fine.
I’m not sure if it’s a computer issue, and I’m running a pretty robust machine, and processing on local hard drives, or if there is something bigger at play.
Has anyone had similar issues?
1 Like
We aren’t using the dongle yet, but we’ve had some flights in the last month that haven’t processed when there seems to be no reason. The base data is good, everything seems to have been captured correctly, but it won’t process. One data set even lets us get to the trajectory screen, and we can adjust those parameters - but it will just not do the final processing.
I have spoken to a few other rock users outside of the community forum and sound like we are all having the same issues. and we are not all using the same sensors so… I flew 2 test flight yesterday and 3 today and can’t get any of them to process! I even tried to use a CORS station and it says can’t process because there isn’t a .25p file. I have used CORS stations before when in a pinch and have never had to have the .25p file. not sure if that is an Emlid file or what… I was thinking that after a few updates since I first brought this to the attention of Rock that something would be fixed. that was a month and a few updates ago and still nothing. we do a lot of flying throughout the year, but these first few months of the year are our wind and weather months, and we have pushed our projects as far back as we can. we have to get going now as we will be flying several times a week for the next 2 months but it’s kind of hard to do that when equipment/software doesn’t work. we can’t be the only few that are having these issues. Maybe we are just the only ones speaking up about it in the forum.
ROCK PLEASE HELP!!!
1 Like
we started flying last year. the first test flights would not process to trajectory. took a bit but turned out to be the rinex converter we were running. keep in mind this is for sp80/85 gnss heads. we had to use an old version of the converter with fewer output constellations.
i am not sure about emlid, but this might be an area to test if at all possible. did something happen with their converter recently??? or sometimes in other gnss workflows like radio connections, too many satelittes(if more have come online) can result in data issues if the software/hardware is not expecting so much data.
just a guess, but you seem to have everything else covered. we just flew two or three weeks ago with r3pro and it processed fine.
we got the password login instead of the dongle. still annoying to have to log in/out to swap computers but it does work.
it’s just odd that we have the same workflows, processes and procedures for the last several years and everything worked great through PC master and even with the few hiccups when Rock first released Desktop things still would process. But now we have the dongle license, and we can’t get it to process. we have disabled defenders and firewalls and all the IT things and still no real luck. I went through support and somehow, they got the one flight I sent them to process. not sure if they are using a dongle or what. no real solution on the problem. I have gone back through the archives as there used to be a tutorial on standalone processing, but it seems to have been taken down. It’s just frustrating at this point… what is the saying… if it isn’t broke then don’t fix it. I understand that tech is constantly advancing and evolving so updates are necessary. but I can’t use our system and the only thing that has changed is the Rock Desktop software. I do have a colleague that has agreed to try and process my data through PC master to see what he can find and rule out hardware issues and if it will process through PC master then it tells me that there is a software issue. again, there are a few other users that are experiencing the exact same issues.
and as a side note I have been very pleased with RockRobotic. no real complaints and they have been very helpful with other issues in the past, but this issue has to be resolved. and if it turns out there is something I’m doing wrong I will be the first to admit it.
I have had the exact same problems since being forced to switch to the dongle in January. Before that with the login, no problems. Since then, the dongle creates problems with the security and virus software on all three of my computers. I’ve stopped trying to keep up with all the updates until it works itself out. I have one computer that will process on an older version for whatever reason, and am afraid to update it until I can get another computer to work with the latest update. It drives my IT guy crazy. The new Dongle idea hasn’t worked out as planned. But they will get it worked out eventually, I hope.
We have been having all kinds of issues with PDOD on our flights as well. We also haven’t been able to load CORS data into 1.13.31 udpate.
I am pleased to say that with the 1.13.31 update I am now able to process flights that were previously not working. I have processed about 8 since yesterday. including 2 flights that were processed prior to the dongle just so I could compare them. the processing reports for each are a little different when looking at the overall PDOP and the total combined position separation. I haven’t tried using a CORS station on this latest update. I’ll get to that later this week just as a test.
we have 2 flights to do as soon as the weather moves out, so next week, and I will report back then with the results of the processing. I’m keeping my fingers crossed that everything goes smooth.
I will also bring the 2 clouds from previous desktop and with current desktop version into the cloud and compare to control and each other to see if i notice anything in the clouds themselves.
I have had nothing but issues since they updated Desktop to produce Ortho’s. I have to process a job 3-4 times before it will finish. Service is not much help, I always get “well we don’t have an issue when we process it on our end.” I think i have narrowed it down to Rock Desktop not playing well with other programs you may have running in the background and to an issue with intel Chip.Intel’s 13th and 14th-generation Raptor Lake CPUs are facing serious stability issues and frequent crashes. The issue has been traced to excessive voltage being sent to the CPU cores, which can lead to both performance problems and permanent damage to the processors.
Did you ever find a solution? Are you using the USB dongle license? We haven’t been able to successfully process a flight since moving to the USB license a couple of months ago.
with all of the rock desktop updates we were able to process data. however, every time we update, I have to go through a process with the Virbox user tool (dongle license manager) and repair my dongle driver. it is a process, but I have done it so many times now that it doesn’t take very long. it’s more of an aggregation than anything. let me know if you are still having trouble and we can set up a teams meeting and i can try to help you.
Thanks for the offer Josh. We did eventually get Virbox working, but now we’re running into trajectory error issues on basically every flight.
I’m sorry to hear that you’re still having issues. I know it’s very frustrating. I’m assuming you are up to date with the latest version?
Has anyone managed to get data to process with Rock Desktop after switching to the USB dongle license? We’ve installed Virbox and followed the documentation to recognize the license, but Rock Desktop keeps alternating between throwing the general trajectory error or an error that says “An error has occurred that typically indicates a missing dependency. Please make sure Microsoft Visual C++ Redistributable is installed. You can install it from here: Download” even with flights we previously processed without issue. The errors are inconsistent on which appears for a given attempt, but we’ve installed the latest redistributable. We’ve also confirmed with IT that no security software is interfering and the firewall isn’t blocking anything. If someone out there has been able to use the dongle license successfully, could you please outline here on the forum what steps you took or what setup was required?
We eventually got a computer to process data using Rock Desktop with the USB dongle license. The issue appeared to be one of our security software (not Windows Defender) quarantining the file C:\RockRobotic\RockDesktop\resources\libs\rs\bin\EPIC_NAVSol.dll during installation. Since the file did not exist, exceptions were thrown in the software. Since the quarantining happened on install, it was easy to miss why the software was not behaving as expected given the error provided days after installation. This would have been much easier to diagnose and resolve if the Rock Desktop logs provided more details on what was throwing an exception or if the software had more descriptive errors for end users. Posting this information in the community in case it ends up useful for others having this issue. If you can’t see anything being blocked while running the software, check for anything that was blocked during installation.