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

sudo /etc/init.d/fabscanpi-server <start|stop>

- Mario

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

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

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

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

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

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).

thanks for the log. How do you power your device?

Best,

René