Calculating Normals Issue

[mbenjamin]

I am not aware of issues related to importing ptx. You may want to contact support and send them your exported ptx files.

[Bob-Boyce]

This is the error when I use Cyclone to import the PTX points from Faro



Unable to import file(s)
E:\scan projects\uw me\points\UWME0001_4.ptx
There are errors reading file(s):
E:\scan projects\uw me\points\UWME0001_4.ptx

File:E:\scan projects\uw me\points\UWME0001_4.ptx
LeicaGeosystems.ApiFramework.Core.OperationFailedException: The monitored process has failed. ---> LeicaGeosystems.ApiFramework.DataManagement.UnexpectedFormatException: Cannot access data at "file:///e:/scan projects/uw me/points/uwme0001_4.ptx#0" ---> System.NullReferenceException: Object reference not set to an instance of an object.

at Q7.A(Int32 A_0)

at X0.E(Int32 A_0)

at KZ.A.E()

--- End of inner exception stack trace ---

at P1.B[A](Exception A_0, Identifier A_1)

at P1.E(Exception A_0, Identifier A_1)

at KZ.A(Exception A_0)

at KZ.A.E()

at AU.E.F()

at AU.D.MoveNext()

at YY.A.E()

at YY.A()

at YY.Read(Byte[] buffer, Int32 index, Int32 length)

at LeicaGeosystems.PointCloudEngine.Codecs.Framework.LocalStreamUniformIterator`1.A.InnerRead(Byte[] buffer, Int32 index, Int32 length)

at LeicaGeosystems.ApiFramework.Core.Utilities.LocalUniformIterator`1.ValueStream.Read(Byte[] buffer, Int32 offset, Int32 count)

at LeicaGeosystems.ApiFramework.Properties.Utilities.PropertyWriterUtilities.ProgressPair.RunStream()

--- End of inner exception stack trace ---

at LeicaGeosystems.ApiFramework.Core.Utilities.ServerSide.ProgressMonitorResultHolder.GetResult()

at LeicaGeosystems.ApiFramework.Properties.Utilities.PropertyWriterUtilities.ProgressPair.InnerGetResult()

at LeicaGeosystems.ApiFramework.Core.Utilities.ServerSide.RemoteProgressMonitor.GetResult()

at LeicaGeosystems.ApiFramework.Core.Utilities.LocalProgressMonitor.GetResult()

at ImportPCSParts(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* fileName, ImpClientServerConnection* pDestDb, list<CyImportScanData\,std::allocator<CyImportScanData> >* rScanData, ImportScanOptions* pImportScanOptions, ImpProgressUpdater* pUpdater)

[mbenjamin]

For us to determine if it is on our end you would need to send Support at least one of the malfunctioning ptx files.

Thanks

[Oliver Buerkler]

Hello Bob.

Did you export PTX of whole scan (right click on the scan in the structure view) while you had an active selection in the scan view?
I just learned from our development team that in this case there is a bug in V4.6 which writes the size of the selection into the PTX header. This may cause the issue while importing into Cyclone?

Work-around:
- remove the selection from the view of the scan, or
- select the whole scan (CTRL-A) before exporting

Version 4.7 will have this bug fixed.

PS:
I do not think that this has anything to do with the normal calculations in Cyclone.

Best regards,
Oliver Bürkler

[stevenramsey]

open the offending ptx file (textpad or similar) and post up the first 20 lines or so. just to see if there is anything strange. Also do a search in the text editor for any "e" or "d" I have had a few PTX files that fail when there is engineering notation inside.

[Bob-Boyce]

[color=#FF0000]Hello Bob.

Did you export PTX of whole scan (right click on the scan in the structure view) while you had an active selection in the scan view?
I just learned from our development team that in this case there is a bug in V4.6 which writes the size of the selection into the PTX header. This may cause the issue while importing into Cyclone?

Work-around:
- remove the selection from the view of the scan, or
- select the whole scan (CTRL-A) before exporting

Version 4.7 will have this bug fixed.

PS:
I do not think that this has anything to do with the normal calculations in Cyclone.

Best regards,
Oliver Bürkler[/color]



Hello Oliver

Thanks for replying to my problem I seem to be having it a lot. The method of extracting the points to a ptx file is with Ctrl-A, right click mouse and create a new 1/4 scan, SAVE. Then in the work space in the structure window I right click the new loaded 1/4 scan and export, scan points, using the ptx format(full scan). This method used to work for me but not now. Maybe I am doing something I should not.

Robert Boyce
Hoffman Corp.
Seattle, Wa

[Bob-Boyce]

Oliver


Thank you very much that was it. I had to stay in the scan view only to export to the PTX file and not use the structure to the left. Thanks!!!!

Bob

[Oliver Buerkler]

Hi Bob.

Great that it is working now for you!
Still our software people have to look into this.

Best regards,
Oliver Bürkler

[Kevin Akin]

I had the same problem when the Edit/Preferences/Point Cloud/Import: Compute Missing Normal Vectors: was set to the default "No". Changing it to "Yes" and reimporting the data fixed the problem. It does add to the time that it takes to import data into Cyclone.

Also change the "Import: Compute Colors During Importing" to "Yes". This will allow the photographic RGB colors to be applied to the point cloud.

As far as I know this is the only way to import C-10 data into Cyclone is through FIle/Import Scanstation C-10 Data. The C-10 PCE format is changed to IMP. Does anyone know if there is another method of importing C-10 data into Cyclone? Can Cyclone use the PCE format directly?