If you are have the Message "No FabScanPi HAT or compatible device found" in your log file you need to check the following options.
First double check the solder joints of the 40-pin Header of the FabScanPi-HAT. If you are sure that there are no 'cold' solder joints move on reading, otherwise resolder those joints. Try again and have a look to the logs. If the error still occurs continue reading with 3.
Check if your fabscanpi-server version is 0.8.0 or higher. Have a look into your default.config.json and check the serial baudrate. It should be 57600 for fabscanpi-server >= 0.4.2. If you changed the baudrate and the error still occurs continue with reading 3.
Your bootloader is bricked, what means that you need to flash a new bootloader to your FabScanPi HAT. Continue with reading "How to flash the FabScanPi HAT Bootloader?"
How to flash the Bootloader?
! If you want to leave the HAT connected to the pi during the flashing process. Be sure you stopped the FabScanPi Server. You can use the following command to do that. !
$ sudo /etc/init.d/fabscanpi-server stop
Option A: Using Raspberry Pi for flashing.
Connect the FabScanPi HAT pins as described below. (solder some wires to the solder pads). Use a resistor 2k2...5k6 in series for every signal. (see picture for details)
If you are have the Message "No FabScanPi HAT or compatible device found" in your log file you need to check the following options.
First double check the solder joints of the 40-pin Header of the FabScanPi-HAT. If you are sure that there are no 'cold' solder joints move on reading, otherwise resolder those joints. Try again and have a look to the logs. If the error still occurs continue reading with 3.
Check if your fabscanpi-server version is 0.8.0 or higher. Have a look into your default.config.json and check the serial baudrate. It should be 57600 for fabscanpi-server >= 0.4.2. If you changed the baudrate and the error still occurs continue with reading 3.
Your bootloader is bricked, what means that you need to flash a new bootloader to your FabScanPi HAT. Continue with reading "How to flash the FabScanPi HAT Bootloader?"
How to flash the Bootloader?
! If you want to leave the HAT connected to the pi during the flashing process. Be sure you stopped the FabScanPi Server. You can use the following command to do that. !
$ sudo /etc/init.d/fabscanpi-server stop
Option A: Using Raspberry Pi for flashing.
Connect the FabScanPi HAT pins as described below. (solder some wires to the solder pads). Use a resistor 2k2...5k6 in series for every signal. (see picture for details)
Just curious if you ever got an answer I've followed the directions and can obtain the bootloader hex, but when I run the next command to flash the boot loader it says pi_spi does not exist?
I'm curious if this is due to not editing the .conf file correctly or not
Is there a folder to be in before typing the command like the log file or am I totally missing something?
Also have 2 scan hats and both don't work...
I will bet watterott never flashed the bootloader to begin with
I was able to get one of my hats to work with the new software and the current boot loader. I was connected to the hat as per the above documentation. It would be good to have a log of what you get when you try and run the commands.
Mario is the expert and really helped me get mine going.
Failed to restart fabscanpi.service: Unit fabscanpi.service not found.
Now there isn't a "HAT not found message" in the log file - so i think we are on the right track.
I disabled SSH and set the Pi configuration to the desktop and now the browser reports the same screen via the IP address "The FabScanPi server is currently not running" and I see a flashing courser and mouse pointer on the attached HDMI monitor.
I will have to see how to do that. In the mean time I did some further testing and I want to make sure that the correct bloader.hex file is loaded. When I use the bloader.hex file from the location " https://github.com/watterott/RPi-UNO-HAT/blob/master/software/bloader.hex " I receive the following message.
Just edited your post, because the first lines give us clarity. That is definitely not a correct hex file. It looks more like a dump of the GitHub html page.
The header of the file should start with this lines...
after many trials und reading (almost) all related posts in the forum, I'm still not able to get the Fabscanpi-server started.
I used the image to install Fabscanpi (SW is v.2019-11-08-22-00).
I followed all recommended steps to solve the issue: Changes made to the default.settings.json - file, re-flashed the bootloader, checked for cold solder joints and checked the serial interface (with a scope) while server is starting. All positive.
Below the fabscanpi.log; it always stops trying to connect to the Arduino.
2019-12-01 14:36:25,296 - fabscan.server.FSScanServer - INFO - FabScanPi-Server 0.8.0+201911082051 2019-12-01 14:36:25,298 - fabscan.scanner.interfaces - DEBUG - Scanner Type is: laserscanner 2019-12-01 14:36:25,961 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Port in Config found 2019-12-01 14:36:25,963 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Latest available firmware version is: v.20190811 2019-12-01 14:36:28,140 - fabscan.lib.util.FSUtil - DEBUG - avrdude-original: Using autoreset DTR on GPIO Pin 7 2019-12-01 14:36:30,394 - fabscan.lib.util.FSUtil - DEBUG - avrdude-original: Using autoreset DTR on GPIO Pin 7 2019-12-01 14:36:30,946 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Trying to connect Arduino on port: /dev/ttyAMA0
Please let me know any further ideas on what I can check or change, to get the Scanner up and running.
We use cookies to optimize our website and our service.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.