Youlin Gao

Hi Arne,

since your question is more account specific, I'll help you to open up a support case rather a forum question which is public.
In the case we can check in detail also with your account managers how to solve your problem.

Best, Youlin

As a note the problem reported here is resolved in a support case. Cause was a mismatch in the processing software version.

Pasting the error message and search in our KBAs is always a good method to find out common solutions we've summarized, for data authentication errors one can use this one:
https://support.navvis.com/knowledgebase/article/KA-02416/en-us

Best,
Youlin from Navvis

Hi Tom!<br> <br> thank you for using our forum! That's often a question asked by our new partners, and the answer is simple: the default password is also "mapper".&nbsp;<br> <br> You can keep using this password, or for security reasons you can also change the password in the Ubuntu system. But keep in mind that please don't change the user name of "mapper".<br> <br> More information you can also find in our documentation:&nbsp;https://docs.navvis.com/mapping/v2.15.1/en/html/updating.html?highlight=mapper%20password#updating-the-software<br> <br> Best, Youlin

Hi Jason,

thanks for using our forum! (btw we moved your request from IVION to the M6/VLX section)

Tunnel mappings are always the most difficult situations for the system. Through your description there seemed to be indeed a SLAM lost when you noticed the VLX icon staying static in the screen, and a sensible decision to have a retake after noticing.

However, I'm not really sure of the features effectiveness in the tunnel. Just from the quality map it looks there are features, but in a repeated manner every 2-3 meters. This could be easily also a confusing environment for the SLAM. A specific feature is for example a barrel on the current point and after a few meters a chair (another unique feature) etc. 

In the post-processing stage, you can also try to select the outdoor preset for processing, this might also help to correct the original mapping's SLAM break.

I hope the above points can help to some extent. If you would like to deeper investigate on this mapping data, we can also move on to a support case. There we could check deeper with your original data, processed data etc. to see if there's anything to tweak in mapping and processing.

Best, Youlin

Hi Christian,

thanks for using our forum to put up questions.
We've also discussed the same question with our developers, so far from our mapping device natively it's not easy to have a structured pointcloud, as the scan position is constantly varying. Our current software is also not supporting the conversion.

But I've also emphasized your request with our developers again, it's good to know on how universal and the impact of the use cases, we'd also provide the information to our devs and see if it could be developed into a new feature.

Best, Youlin

Hi Ben & Peter,

Great to know that there're more and more scenarios that you're interested and that VLX has the potential reach to all these difficult situations.

Just found that I missed the last question from Ben, about clearing noisy pointclouds. From IVION we can do such croping of desired range of pointclouds, but only to export them:
https://ivion.docs.navvis.com/navvis-ivion-end-user/advanced-functions/cropping-and-downloading-point-clouds

To clean desired area of pointclouds and present it as default in IVION is still not available, a workaround is to clean the pointcloud.ply in 3rd party software before web-processing, and after web-processing it would be a cleaned version. (Of course this local step needs desktop processing SW and not our cloud processing.)

Best, Youlin

 

Hi Mariusz,

sorry to hear that it failed repeatedly, I also saw your team put up a support case. Let's move further discussions there, one of my colleague is working on it.

We're putting this issue to a higher priority since it happens repeatedly, currently we're searching for cause and solution with our development team and will update you in the support case.

Regarding the error code, sorry currently we don't have a public reference for the codes. In this case it's coming from other services like AWS with AWS specific descriptions. But I think it makes sense that we summarise and draft a user friendly error codes reference, with some solution steps so users can react on those errors. Will bring this up within our team on this general topic.

Best, Youlin

Hi Mariusz,

thanks for using the forum. To your problem, this looks like an error thrown from our cloud infrastructure from Amazon Web Services.
For some reference, here's a page from AWS on describing the spot instance interruption: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html

For your case, could you try to restart the processing once again and see if the processing can finish normally?

If it doesn't, please create a support case via our portal or by sending one email to support@navvis.com.
Usually our forum is used for discussion of broader topics that is visible to the public audience, and for issue that requires logs, data etc. we switch to the support case where we could handle faster and easier.

Best, Youlin


 

Hi Ben, 

thanks for the screenshot and description, I think I understood better of your scenario.

My previous reply was imagining you were on a boat and floating up & down under a wharf but without moving around much -> boat floor could be scanned well but the "ceiling" would be blurry.

From your last mail I guess you're on a small boat but moving quite a lot under the wharf, if the main structure you're capturing is the wharf, then actually what we can imagine is the wharf is static (which is true) and the VLX/mapper/boat is moving.
In an ideal case you'll get a relatively good scanning of the wharf structure, but the boat captured by the VLX will be the noise and will be like a trailing pointclouds in the final result. Similar to e.g. if you're stretching your hands during an indoor scanning you'll get a trailing pointclouds of your hand.

Sounds like a quite challenging environment and let me know if I misunderstood anything of your scenario.

Best, Youlin



 

Hi Ben,

thanks for using our forum to put up questions :)

I'm not too sure about the exact structure in your scenario, but yes, if in the environment, where the floor is static and the ceiling is "moving", then the SLAM and the accurate capturing of the structure will be suffered.

Could be that the scanning can still be finished and the result doesn't have a broken structure, but I guess the "moving" structures like the ceiling might be cloudy or inaccurate. It's similar to e.g. mapping a corridor with a constantly moving door, in the end the could be the corridor is still correctly scanned but the door is not a trustworthy object.

Hope it helped a bit,
Best, Youlin