Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
What is the progress on getting thermal imaging for the BLK360? It feels like a bate and switch. This was promised with the BLK360 but so far it has not been delivered. I think the firmware still needs to be updated for this to work, but I'm checking on any updates on the Autodesk end.
Is there anyone who would like to get this started? I believe it’s only fair that we get compensated. If you can all comment your names and good email address to reach you at? That would be a start! Thanks!
Not only is it unacceptable that this doesn't work, it also creates errors that make individual scans corrupt with this error:
"Error An invalid parameter was encountered while communicating with the BLK360. Message: lgs_req_dl_image(): IR image index too large Additional details: Code: Unknown Error: lgs_error_invalid_parameter."
The Autodesk page that I pasted this from said that the push-button method of executing a scan kicks on the IR camera, which the iPad start method does not? This just isn't true because I get this error about 3% of the time using the push-button only. Which by the way totally sucks because that means for every 100 scans I take, 3 of those are done, gone kaput. Hope those randomly selected garbage scans weren't important or anything!
The BLK360 does kind of look like a tombstone doesn't it.
Like everyone else, we've been forced over to Cyclone. It's great, and the thermal imaging does work there, but now we're dealing with a whole new set of dodgy Leica business practices (see Leica "Publisher" for a cold lesson in bull**** proprietary file types that are only available if you fork it over.)
