Release Notes v.0.7.0
You can find detailed information about the main changes in the related blog post.
It is recommended to start with the new released image, because the whole image structure changed. A lot of things are improved.
Changelog:
Added
- new settings dialog options for hardware contolling
- moved calibration button to settings dialog
- added new configuraitons in general settings tab
- prepared platform independet firmware setup (aka cyclop compatible mode)
- api route for live log stream
- api route for debug log zip download
- new firmware version
- made fabscan discoverable in find.fabscan.org
- api scheduler library for registery servcie and future scheduling tasks
- added meshmixer to package dependencies
- added avrdude config to package dependencies
Changed
- replaced old image build script by a new one, based on official raspbian build scripts
- FSUpdate is working for different stages now
Fixed
- fixed camera driver (pi and usb)
- fixed random artifacts at the beginning of object scan
- fixed calibration issue
Thanks for the new release!
Let's do some testing.
First impressions:
- sudo service fabscanpi-server restart doesn't work. Because 'start' works it seems that the 'stop' procedure doesn't work. Have to kill the python process to stop the server.
- First scan after calibration doesn't work for me. It seems to be a loop in the step 'G04 T4 F900'. See logfile and calibration result attached. default.config.json Fabscanpi.log
- Sometimes the webinterface buttons for turntable on/off etc. are not shown. Both the case with latest firefox & chrome browser on Ubuntu. See screenshot attached. Screenshot
Best regards,
Uwe
Hello Uwe,
- sudo service fabscanpi-server restart doesn't work. Because 'start' works it seems that the 'stop' procedure doesn't work. Have to kill the python process to stop the server.
thank you for testing and reporting. Just try to restart/stop and start the service with sudo /etc/init.d/fabscanpi <start|stop|restart>.
- First scan after calibration doesn't work for me. It seems to be a loop in the step 'G04 T4 F900'. See logfile and calibration result attached. default.config.json Fabscanpi.log
I will have a closer look to that.
- Sometimes the webinterface buttons for turntable on/off etc. are not shown. Both the case with latest firefox & chrome browser on Ubuntu. See screenshot attached. Screenshot
This seems to be a case of connection error. Those controls are requested over the api and shown in a generic way. When the request does not respond with the "hardware buttons config object" it can not be rendered to the UI. I think we need more testing to find the cause.
- Mario
Hello and thank you for this update.
Have been struggling to get the wifi working but finally managed to do so (I'd better share my remarks about this in a seperate post)
Discovering the FabScanPi through find.fabscan.org works flawlessly. This option even remembered the ip address when it was wired, as it still shows up above the actual wireless ip-address.
Hi Erik,
thanks for the Feedback. Did you try the wpa_supplicant method? Something like this should work:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
network={
ssid="YOUR_NETWORK_NAME"
psk="YOUR_PASSWORD"
key_mgmt=WPA-PSK
}
Best,
René
Hi René
that's what I did, but I didn't realize I had to write the wpa_supplicant.conf file to a freshly imaged SD-card.
I had first tested the 0.7.0 release via my ethernet connection, then put back the SD-card in my PC and added the wpa_supplicant.conf to the boot partition, but when I put the card back, inserted a WiFi dongle and restarted, I couldn't get an ip-address in my router list (I waited at least 15 minutes...).
So I had a look at this excellent explanations post by HawaiianPi and found out that you need to write this file to a freshly imaged SD-card, use the precise text and capitalization, change the country (I put FR because I'm living in France), put my network SSID and password before my next try. It finally worked ! (really need to wait about 2 minutes to have the WiFi working and another minute to get the FabScanPi recognised.
Now I'm trying to calibrate the scanner but I can't get the turntable in the middle of the picture and probably have to use standoff brackets for the 2 top screws of the camera/led ring module. I'll post about that as soon as I get it working!
Hi,
if I try to start the FabscanPi via LAN (with IP-Adress in Firexfox), I get the message "The FabScanPi server is currently not running".
When I try to restart / stop the server:
pi@fabscanpi:~ $ sudo service fabscanpi restart
Failed to restart fabscanpi.service: Unit fabscanpi.service not found.
pi@fabscanpi:~ $ sudo service fabscanpi stop
Failed to stop fabscanpi.service: Unit fabscanpi.service not loaded.
Here is my logfile:
2019-02-21 22:42:48,677 - fabscan.server.FSScanServer - INFO - FabScanPi-Server 0.7.0
2019-02-21 22:42:50,966 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Port in Config found
2019-02-21 22:42:50,974 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Latest available firmware version is: v.20190211
2019-02-21 22:42:53,215 - fabscan.lib.util.FSUtil - DEBUG - avrdude-original: Using autoreset DTR on GPIO Pin 7
2019-02-21 22:42:53,237 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - No FabScanPi HAT or compatible device found on port /dev/ttyAMA0
2019-02-21 22:42:53,238 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - Fatal FabScanPi HAT or compatible connection error....
2019-02-21 22:42:53,238 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Connection baudrate is: 57600
2019-02-21 22:42:53,238 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Firmware flashing baudrate is: 57600
2019-02-21 22:42:53,239 - fabscan.scanner.laserscanner.FSHardwareController - DEBUG - Reset FabScanPi HAT...
2019-02-21 22:42:53,239 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - 'NoneType' object has no attribute 'write'
2019-02-21 22:42:53,240 - fabscan - CRITICAL - Fatal error: 'NoneType' object has no attribute 'read'
2019-02-28 18:40:53,287 - fabscan.server.FSScanServer - INFO - FabScanPi-Server 0.7.0
2019-02-28 18:40:55,604 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Port in Config found
2019-02-28 18:40:55,614 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Latest available firmware version is: v.20190211
2019-02-28 18:40:57,808 - fabscan.lib.util.FSUtil - DEBUG - avrdude-original: Using autoreset DTR on GPIO Pin 7
2019-02-28 18:40:57,831 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - No FabScanPi HAT or compatible device found on port /dev/ttyAMA0
2019-02-28 18:40:57,832 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - Fatal FabScanPi HAT or compatible connection error....
2019-02-28 18:40:57,832 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Connection baudrate is: 57600
2019-02-28 18:40:57,832 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Firmware flashing baudrate is: 57600
2019-02-28 18:40:57,833 - fabscan.scanner.laserscanner.FSHardwareController - DEBUG - Reset FabScanPi HAT...
2019-02-28 18:40:57,833 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - 'NoneType' object has no attribute 'write'
2019-02-28 18:40:57,834 - fabscan - CRITICAL - Fatal error: 'NoneType' object has no attribute 'read'
2019-02-28 18:49:03,929 - fabscan.server.FSScanServer - INFO - FabScanPi-Server 0.7.0
2019-02-28 18:49:06,214 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Port in Config found
2019-02-28 18:49:06,224 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Latest available firmware version is: v.20190211
2019-02-28 18:49:08,445 - fabscan.lib.util.FSUtil - DEBUG - avrdude-original: Using autoreset DTR on GPIO Pin 7
2019-02-28 18:49:08,467 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - No FabScanPi HAT or compatible device found on port /dev/ttyAMA0
2019-02-28 18:49:08,468 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - Fatal FabScanPi HAT or compatible connection error....
2019-02-28 18:49:08,468 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Connection baudrate is: 57600
2019-02-28 18:49:08,468 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Firmware flashing baudrate is: 57600
2019-02-28 18:49:08,469 - fabscan.scanner.laserscanner.FSHardwareController - DEBUG - Reset FabScanPi HAT...
2019-02-28 18:49:08,469 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - 'NoneType' object has no attribute 'write'
2019-02-28 18:49:08,470 - fabscan - CRITICAL - Fatal error: 'NoneType' object has no attribute 'read'
2019-02-28 19:02:44,814 - fabscan.server.FSScanServer - INFO - FabScanPi-Server 0.7.0
2019-02-28 19:02:47,145 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Port in Config found
2019-02-28 19:02:47,154 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Latest available firmware version is: v.20190211
2019-02-28 19:02:49,360 - fabscan.lib.util.FSUtil - DEBUG - avrdude-original: Using autoreset DTR on GPIO Pin 7
2019-02-28 19:02:49,383 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - No FabScanPi HAT or compatible device found on port /dev/ttyAMA0
2019-02-28 19:02:49,383 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - Fatal FabScanPi HAT or compatible connection error....
2019-02-28 19:02:49,384 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Connection baudrate is: 57600
2019-02-28 19:02:49,384 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Firmware flashing baudrate is: 57600
2019-02-28 19:02:49,385 - fabscan.scanner.laserscanner.FSHardwareController - DEBUG - Reset FabScanPi HAT...
2019-02-28 19:02:49,385 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - 'NoneType' object has no attribute 'write'
2019-02-28 19:02:49,386 - fabscan - CRITICAL - Fatal error: 'NoneType' object has no attribute 'read'
What is going wrong, how can I get my Fabscan Pi started ?
Greetings,
Ralf
I forgot to tell my Browser and FabscanPi Versions:
Firexfox Quantum 65.0.2 (64 Bit)
FabscanPi Kit from Watterott, bought in September 2018
Greetings,
Ralf
Too bad, version 0.6.0 does not work, version 0.7.0 does not work, only version 0.5.0 works with me. The only hope is that version 0.8.0 will work.
2019-02-28 18:49:08,467 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - No FabScanPi HAT or compatible device found on port /dev/ttyAMA0
Means that the pi is not able to connect to the FabScanPi HAT over serial. You mentioned that v.0.5.0 works, that indicates that your FabScanPi HAT seems to be ok.
Have you installed v.0.7.0 by flashing a new image to the SD-Card or by apt-get? ( fresh image is the recommended way for v.0.7.0).
Hi Ralf,
thanks for the log. How do you power your device?
Best,
René
Hi,
I formatted the SD-Card and copied the 0.7.0 image with the Win32DiskImager to it (as recommended). I already use a 12 Volt / 3 Amp. Power Supply. For the 5 Volts, I use the 12V - 5V Step Down Converter from the watterott - Kit.
Greetings,
Ralf
Hello Ralf,
can you please try this.
First:
sudo avrdude-autoreset -p m328p -b 57600 -carduino -P/dev/ttyAMA0
Second:
sudo avrdude-autoreset -p m328p -b 115200 -carduino -P/dev/ttyAMA0
Please post the output of this command here. Some pictures of the
during the scan process (object on the table with opened lid) would
also be helpful.
There is also a better way of providing debug information (like log files) since v.0.7.0. You can call
https://<your_fabscan_ip_address>/api/v1/log/download/
This command will initiate a download of a zip file. The zip contains a lot of files for a better debugging.
- mario
Seems as if everything is setup as recommended. We will have a deeper look into this. If you switch back to 0.5.0, will everything work again? We need to be sure that the HAT is still working.
Hi,
here is the output of the two commands:
pi@fabscanpi:~ $ sudo avrdude-autoreset -p m328p -b 57600 -carduino -P/dev/ttyAM A0
avrdude-original: Using autoreset DTR on GPIO Pin 7
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x30
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x20
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x30
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x20
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x30
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x20
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x30
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x20
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x30
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x20
avrdude done. Thank you.
pi@fabscanpi:~ $ sudo avrdude-autoreset -p m328p -b 115200 -carduino -P/dev/ttyA MA0
avrdude-original: Using autoreset DTR on GPIO Pin 7
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: safemode: Fuses OK (E:00, H:00, L:00)
avrdude done. Thank you.
The download of the zip file with the log file and debugging informations did not work. First, I had a lot of problems with security warnings from firefox. As I solved this problem, there was no zip file in my download path. I still have no access to the frontend (the fabscanPi Server is currently not running ...).
@rene: With the software 0.5.0 my fabscanPi still runs perfect. I had no problems with calibration and already did some scans.
Greetings, Ralf
Hi,
your first log already showed that the Raspberry Pi can not connect to the FabScanPi HAT. Your latest post shows that there is a problem with baud rate 57600. With 115200 it seems to work. 57600 Baud is the default for flashing the firmware. You can set the flashing baud rate to 115200 in the config by adding the following line to the serial config part.
Add this line to the serial section:
"flash_baudrate": 115200
At the end it should look like the following blog:
"serial": {
"plattform_type": "fabscanpi",
"baudrate": 57600,
"autoflash": "True",
"port": "/dev/ttyAMA0",
"flash_baudrate": 115200
}
This should work.
- Mario
Unfortunately, that does not work either. Still the same error. It is different now that no more python process is displayed. If I type
ps -ef | grep -i fabscanpi | grep -i python
nothing happens, only a line feed.
Restarting the server fails:
pi@fabscanpi:~ $ sudo service fabscanpi restart
Failed to restart fabscanpi.service: Unit fabscanpi.service not found.
What else can I try to get the FabscanPi running ?
Greetings,
Ralf
Systemd is not 100% supported yet. So try to start/stop the server by using
sudo /etc/init.d/fabscanpi-server <start|stop>
- Mario
When I try to start the server with
sudo /etc/init.d/fabscanpi-server start
I get:
avrdude-original: Using autoreset DTR on GPIO Pin 7
fabscanpi-server started.
If I type (directly after that)
sudo service fabscanpi restart
I get
Failed to restart fabscanpi.service: Unit fabscanpi.service not found.
The frontend still does not start ("The FabScanPi server is currently not running").
Greetings,
Ralf
