Scan progress and completion not visible on browser window.  

Page 1 / 2
  RSS
MrH
 MrH
(@mrh)
Active Member

Hello All.

I have just brought and assembled the fabscan kit. The hardware seems to be working (stepper, camera, laser) and I was able to run a calibration successfully. However when running a scan the browser window does not show any progress or images, the turntable  remains empty. When the scan has finished there is no notification on the browser but checking the log showed the 6400 scans were completed. I can hear a click form the stepper (I think) every 5 seconds but there is no further movement. Clicking on the X to stop the scan does that but if I try to LOAD FILES then the window is empty.

The scans folder contains all the jpg files from each scan. I cannot find the point cloud files. Perhaps they have not been generated.

Have tried firefox and chromium browsers on Ubuntu but they behave the same.

Server 0.7.0, Firmware v20190211

Tried again with lower resolution: 533 scans instead of 6400 but the result is the same.

However there was a divide by zero error from one of the FSImageWorker threads when running the low res scan.

I have the log file ready to attach but I cannot see how to do so (but I am sure it will be obvious once someone points it out).

Harbanse

Quote
Posted : 06/06/2019 10:14 pm
turbomolitor
(@turbomolitor)
New Member

Hi everybody,

I'm experiencing exactly the same issue. I wonder whether installing older firmware might do the trick. Haven't found an older version yet.

Maybe someone could produce a link to the previous build.

thanks

Michael

ReplyQuote
Posted : 20/06/2019 9:27 am
mario
(@mario)
Member Admin

It's hard to find the error by description. Can somebody share a log file to the related error. Especially the calibration values from the default.config.json would be also interesting. 

It sounds like the calibration is not done fine. Where have you positioned the calibration sheet. It needs to be in front of the table center. Not exactly in the center. Are you using the printable calibration mount? 

ReplyQuote
Posted : 20/06/2019 10:06 am
turbomolitor
(@turbomolitor)
New Member

I have already formatted my sd-card and istalled firmware 2017 07 09,  and  thus deleted the default.config.json. With this older version it seems to work fine, the turntable is not empty now, there is a progrss bar and the estimated remainig time is displayed, though the results may not be totally satisfactory (maybe a more accurate calibration might yield better results. I did the calibrating as you described above.

 

ReplyQuote
Posted : 20/06/2019 12:11 pm
Danilo0702
(@danilo0702)
Trusted Member

I also tried to upload a logfile. The forum guidelines do not allow the format.

ReplyQuote
Posted : 20/06/2019 12:13 pm
MrH
 MrH
(@mrh)
Active Member

I am using the 3-D printed mount.The checkerboard pattern is as specified on the webpage, 11 mm pattern.

I tried many calibrations with the sheet in front of the table mount which failed. When I put it behind it succeeded. I will try it again with the sheet in front.

Things to note for others:

Using a pi 3 with a separate power supply (12 to 5 converter removed).

I will upload the log file and the default.config.json file for reference soon.

Checked that the stepper motor driver ref voltage is 0.8 V.

Added a cooling fan (the pi was reaching 85 C and throttling back).

This post was modified 4 months ago by MrH
ReplyQuote
Posted : 20/06/2019 8:38 pm
MrH
 MrH
(@mrh)
Active Member

This is the default.config.json file after a calibration that succeeded.

Sorry about the appearance.

I don't want to paste the log file here - it is too big. Adding a debug to FSImageWorker showed that it was returning updasd empty for all the laser_raw images.

{
"folders": {
"www": "/usr/share/fabscanpi/",
"scans": "/home/pi/scans/"
},
"laser": {
"numbers": 1
},
"scanner_type": "laserscanner",
"calibration": {
"weight_matrix": [],
"dist_camera_matrix": [],
"pattern": {
"square_size": 11,
"rows": 6,
"columns": 8,
"origin_distance": 37.2
},
"camera_matrix": [
[
1318.708,
0.0,
618.002
],
[
0.0,
1319.61,
784.467
],
[
0.0,
0.0,
1.0
]
],
"distortion_vector": [
0.195,
-0.026,
-0.011,
-0.001,
-1.712
],
"laser_planes": [
{
"deviation": 2.6443359503622165e-13,
"distance": 175.34699312556825,
"normal": [
0.300147036899012,
-0.010636675855017954,
0.9538336423965648
]
}
],
"platform_translation": [
-0.43822154557948423,
52.34339389443525,
149.83121531868218
],
"platform_rotation": [
[
0.0,
0.9997717975207634,
-0.021362417515384476
],
[
-0.012884040336818104,
-0.021360644377214015,
-0.9996888137697598
],
[
-0.9999169973075761,
0.00027523424896016316,
0.01288110016687066
]
]
},
"keep_raw_images": "True",
"meshlab": {
"path": "/usr/bin/"
},
"process_numbers": 4,
"turntable": {
"steps": 6400,
"radius": 70
},
"camera": {
"rotate": "True",
"type": "PICAM",
"vflip": "False",
"preview_resolution": {
"width": 800,
"height": 600
},
"hflip": "True",
"resolution": {
"width": 1640,
"height": 1232
}
},
"discoverable": "True",
"serial": {
"plattform_type": "fabscanpi",
"baudrate": 57600,
"autoflash": "True",
"port": "/dev/ttyAMA0"
},
"texture_illumination": 40
}

ReplyQuote
Posted : 20/06/2019 9:13 pm
MrH
 MrH
(@mrh)
Active Member

Log file attached.

Another calibration was done which completed successfully but still not showing scans.

This post was modified 3 months ago by MrH
ReplyQuote
Posted : 10/07/2019 8:49 pm
MrH
 MrH
(@mrh)
Active Member

OK, that file was rejected even though it was a .txt file.

Which file types are allowed?

ReplyQuote
Posted : 10/07/2019 8:58 pm
MrH
 MrH
(@mrh)
Active Member

Trying again.

ReplyQuote
Posted : 10/07/2019 9:03 pm
MrH
 MrH
(@mrh)
Active Member

That was better. Here is the calibration file.

ReplyQuote
Posted : 10/07/2019 9:04 pm
jakob
(@jakob)
New Member

Hi everybody

I have the same problem and would like to know if anyone has an solution for that.

On my Raspberry Pi 3 I have the server version v.0.7.0 and firmware version v.20190211 installed. Everything is working very well. I can turn the led/laser on and off...

I did the calibration as in the description and was told that it was done successfully.

But if i now try to scan an object there is no result. The Browser will not show any progress on the turning table.

I have looked at the logging file and found that the scanner was creating images but not creating a .ply file.

So i would like to know if anyone has any ideas what the problem might be.

 

Jakob

 

 
ReplyQuote
Posted : 16/10/2019 3:19 pm
jakob
(@jakob)
New Member

# logging file

2019-02-22 00:25:08,764 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: M18;
2019-02-22 00:25:09,134 - fabscan.scanner.laserscanner.driver.FSCamera - DEBUG - Cam Stream with Resolution (800, 600) started
2019-02-22 00:25:09,144 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: M05 R0 G0 B0;
2019-02-22 00:25:13,612 - fabscan.FSScanner - INFO - Start command received...
2019-02-22 00:25:13,632 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: M21;
2019-02-22 00:25:13,647 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: M18;
2019-02-22 00:25:13,659 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G07;
2019-02-22 00:25:13,754 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: M05 R0 G0 B0;
2019-02-22 00:25:14,267 - fabscan.scanner.laserscanner.driver.FSCamera - DEBUG - Cam Stream with Resolution (800, 600) stopped
2019-02-22 00:25:14,582 - fabscan.scanner.laserscanner.FSScanProcessor - INFO - Scan started
2019-02-22 00:25:14,584 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: M22;
2019-02-22 00:25:20,510 - fabscan.scanner.laserscanner.driver.FSCamera - DEBUG - Cam Stream with Resolution (1640, 1232) started
2019-02-22 00:25:29,287 - fabscan.scanner.laserscanner.FSScanProcessor - INFO - Started object scan initialisation
2019-02-22 00:25:30,202 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: M17;
2019-02-22 00:25:30,285 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: M05 R0 G0 B0;
2019-02-22 00:25:32,945 - fabscan.worker.FSImageWorker - INFO - Creating 4 image worker processes.
2019-02-22 00:25:33,664 - fabscan.worker.FSImageWorker - DEBUG - process 1625 started
2019-02-22 00:25:33,664 - fabscan.worker.FSImageWorker - DEBUG - process 1626 started
2019-02-22 00:25:33,765 - fabscan.worker.FSImageWorker - DEBUG - process 1627 started
2019-02-22 00:25:33,833 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: M21;
2019-02-22 00:25:33,891 - fabscan.worker.FSImageWorker - DEBUG - process 1628 started
2019-02-22 00:25:34,896 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 0 of 400 at laser position 1
2019-02-22 00:25:42,572 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:25:43,274 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 1 of 400 at laser position 1
2019-02-22 00:25:43,396 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:25:44,102 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 2 of 400 at laser position 1
2019-02-22 00:25:44,301 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:25:45,006 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 3 of 400 at laser position 1
2019-02-22 00:25:45,195 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:25:45,899 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 4 of 400 at laser position 1
2019-02-22 00:25:46,033 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:25:46,738 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 5 of 400 at laser position 1
2019-02-22 00:25:46,873 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:25:47,583 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 6 of 400 at laser position 1
2019-02-22 00:25:47,755 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:25:48,459 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 7 of 400 at laser position 1
2019-02-22 00:25:48,624 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;

# . There were no other important messages here
# .
# .

2019-02-22 00:31:29,511 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:31:30,219 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 397 of 400 at laser position 1
2019-02-22 00:31:30,412 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:31:31,117 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 398 of 400 at laser position 1
2019-02-22 00:31:31,266 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:31:31,972 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 399 of 400 at laser position 1
2019-02-22 00:31:32,163 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Command successfully sent: G04 T64 F900;
2019-02-22 00:31:32,867 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Laser Progress: 400 of 400 at laser position 1
2019-02-22 00:31:33,001 - fabscan.scanner.laserscanner.FSScanProcessor - INFO - Finishing object scan.
2019-02-22 00:31:33,196 - fabscan.worker.FSImageWorker - DEBUG - Killed Worker Process with PID 1625

# Sometimes it kills the other fabscan.worker.FSImageWorker processes, but never all at once
# And also sometimes this error occurs when a new client logs on. But i dont think that this error is the reason for the problem.

2019-02-22 00:40:30,290 - fabscan.server.services.websocket.FSWebSocketHandler - DEBUG - Client disconnected
2019-02-22 00:40:31,476 - fabscan.server.services.websocket.FSWebSocketHandler - DEBUG - New client connected
2019-02-22 00:40:31,532 - fabscan.lib.util.FSUpdate - DEBUG - Scanner is Online...
2019-02-22 00:40:31,770 - fabscan.lib.util.FSUpdate - ERROR - <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)>
2019-02-22 00:40:31,791 - fabscan.FSScanner - DEBUG - Upgrade available: False 0.7.0
2019-02-22 00:40:31,818 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Checking Hardware connections

ReplyQuote
Posted : 16/10/2019 3:24 pm
jakob
(@jakob)
New Member

# default.config.json

{
"folders": {
"www": "/usr/share/fabscanpi/",
"scans": "/home/pi/scans/"
},
"laser": {
"numbers": 1
},
"scanner_type": "laserscanner",
"calibration": {
"weight_matrix": [],
"dist_camera_matrix": [],
"pattern": {
"square_size": 11,
"rows": 6,
"columns": 8,
"origin_distance": 37.2
},
"camera_matrix": [
[
1342.704,
0.0,
651.126
],
[
0.0,
1328.477,
860.723
],
[
0.0,
0.0,
1.0
]
],
"distortion_vector": [
0.107,
0.418,
0.004,
0.023,
-1.615
],
"laser_planes": [
{
"deviation": 0.054310088751715,
"distance": 97.11689696727404,
"normal": [
0.7624364978155963,
-0.02213432115323592,
0.6466843578019911
]
}
],
"platform_translation": [
-15.20115677873161,
45.87626070394074,
167.7697916996413
],
"platform_rotation": [
[
0.0,
0.9999993091957267,
0.001175418253021654
],
[
0.04193686163526889,
0.0011743841939169364,
-0.9991195726528179
],
[
-0.9991202628493651,
4.9293352640538587e-05,
-0.041936832665105665
]
]
},
"keep_raw_images": "True",
"meshlab": {
"path": "/usr/bin/"
},
"process_numbers": 4,
"turntable": {
"steps": 6400,
"radius": 70
},
"camera": {
"rotate": "True",
"type": "PICAM",
"vflip": "False",
"preview_resolution": {
"width": 800,
"height": 600
},
"hflip": "True",
"resolution": {
"width": 1640,
"height": 1232
}
},
"discoverable": "True",
"serial": {
"plattform_type": "fabscanpi",
"baudrate": 57600,
"autoflash": "True",
"port": "/dev/ttyAMA0"
},
"texture_illumination": 40
}

ReplyQuote
Posted : 16/10/2019 3:24 pm
mario
(@mario)
Member Admin

Your calibration looks good so far. I think there is another issue. Which browser do you use? Have you reconnected/refreshed the browser during the scan process ?

ReplyQuote
Posted : 16/10/2019 7:30 pm
Page 1 / 2
Share: