Hello all,
I got the PI-Hat from Watterott and got the same messages, some in this Forum wrote about.
Now I read all the docs about flashing the arduino but I'm unsure about connecting the reset (for me as an electronic-beginner it's not clear on which side of the reset-button the cable to D10 has to be soldered).
Can someone please help me there?
Best regards
Christoph
I got the PI-Hat from Watterott and got the same messages, some in this Forum wrote about.
I think that is not the same issue. Especially not when you are using the latest image. The bug was fixed within the latest image. That means that the firmware will be flashed automatically by the server when the HAT is a new one. I think you should double check the GPIO pins.
The most important pins are those which are responsible for the serial connection RX, TX and AVR-Dude Reset. Be sure that there are no cold solder joints.
Thanks for the fast answer - I'll check this - good to know, which are the important pins!
Christoph
Hi,
I retried the soldering, but got all the time the same message in the logfile:
2020-01-29 21:00:44,195 - fabscan.server.FSScanServer - INFO - FabScanPi-Server 0.8.2
2020-01-29 21:00:44,196 - fabscan.scanner.interfaces - DEBUG - Scanner Type is: laserscanner
2020-01-29 21:00:44,623 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Port in Config found
2020-01-29 21:00:44,624 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Latest available firmware version is: v.20190811
2020-01-29 21:01:36,214 - fabscan.lib.util.FSUtil - INFO - avrdude-original: Using autoreset DTR on GPIO Pin 7
2020-01-29 21:01:36,250 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - Communication error on port /dev/ttyAMA0 try other flashing baudrate than 57600. Maybe corrupted bootloader.
2020-01-29 21:01:36,250 - fabscan.scanner.laserscanner.driver.FSSerial - ERROR - Fatal FabScanPi HAT or compatible connection error....
2020-01-29 21:01:36,251 - fabscan.server.FSScanServer - INFO - FabScan Server Exit. Bye!
When I tried it with an arduino on ttyUSB0, flashing from the RPi functions.
I attached the pictures from the soldered pins, perhaps you can see sth strange. May it result perhaps from an insufficient powering?
I attached the pictures from the soldered pins, perhaps you can see sth strange. May it result perhaps from an insufficient powering?
Solder joints look good so far. Please try the following.... Login via ssh as user pi as usual.
First stop the FabScanPi-Server with:
sudo /etc/init.d/fabscanpi-server stop
Then check if the connection to the HAT works and the bootloader of the HAT is ok:
sudo avrdude-autoreset -p m328p -b 115200 -carduino -P/dev/ttyAMA0
A message like this is what we want:
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.
If you get a message like
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0xbf
you should try to change the baudrate to 57600.
Maybe this will also help you: https://fabscan.org/community/hardware/hat-not-working-same-as-everyone-else/
Hi,
I tried nearly everything (baudrate, ...) from the mentioned post - and the arduino is not responding.
You wrote how to flash the bootloader, but to come back to my problem, I don't know how to solder the reset-cable to the reset-switch. On the picture published it's not possible to see, if the switch has to be bridged or if I have to connect the cable only to one of both sides of the switch.
Btw. Übrigens eine super Arbeit, die Du geleistet hast und noch leistest!
Christoph
Btw. Übrigens eine super Arbeit, die Du geleistet hast und noch leistest!
Danke.
You wrote how to flash the bootloader, but to come back to my problem, I don't know how to solder the reset-cable to the reset-switch
The image shows that the wire is connected to both pads of the reset switch but you can solder the cable to just one of the pads. I prefer to use a crocodile clamp instead of soldering ( that can be a little bit tricky to get a goof connection ).
Ok, got it!
It was really the bootloader - I bought two shields and tried with both - same error.
Now I flashed the bootloader on one of them - and anything on this side seems to be all right :).
2020-02-01 17:39:06,103 - fabscan.server.FSScanServer - INFO - FabScanPi-Server 0.8.2
2020-02-01 17:39:06,106 - fabscan.scanner.interfaces - DEBUG - Scanner Type is: laserscanner
2020-02-01 17:39:07,400 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Port in Config found
2020-02-01 17:39:07,404 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Latest available firmware version is: v.20190811
2020-02-01 17:39:09,696 - fabscan.lib.util.FSUtil - INFO - avrdude-original: Using autoreset DTR on GPIO Pin 7
2020-02-01 17:39:10,233 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Trying to connect Arduino on port: /dev/ttyAMA0
2020-02-01 17:39:19,244 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Installed firmware version: None
2020-02-01 17:39:19,245 - fabscan.scanner.laserscanner.driver.FSSerial - INFO - Old or no firmare detected trying to flash current firmware...
2020-02-01 17:39:19,304 - fabscan.lib.util.FSUtil - INFO - 782 /usr/lib/python2.7/dist-packages/fabscan/firmware/fabscanpi_v.20190811.hex
2020-02-01 17:39:22,786 - fabscan.lib.util.FSUtil - INFO - avrdude-original: Using autoreset DTR on GPIO Pin 7
2020-02-01 17:39:23,322 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Trying to connect Arduino on port: /dev/ttyAMA0
2020-02-01 17:39:26,331 - fabscan.scanner.laserscanner.driver.FSSerial - INFO - Successfully flashed new Firmware Version: v.20190811
2020-02-01 17:39:26,332 - fabscan.scanner.laserscanner.driver.FSSerial - INFO - FabScanPi is connected to FabScanPi HAT or compatible on port: /dev/ttyAMA0
2020-02-01 17:39:28,339 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Connection baudrate is: 57600
2020-02-01 17:39:28,340 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - Firmware flashing baudrate is: 115200
2020-02-01 17:39:28,342 - fabscan.scanner.laserscanner.FSHardwareController - DEBUG - Reset FabScanPi HAT...
2020-02-01 17:39:28,673 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - M18;
2020-02-01 17:39:29,003 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - G07;
2020-02-01 17:39:29,505 - fabscan.scanner.laserscanner.driver.FSCamera - DEBUG - Cam Stream with Resolution (800, 600) stopped
2020-02-01 17:39:29,505 - fabscan.scanner.laserscanner.FSHardwareController - DEBUG - Reset FabScanPi HAT...
2020-02-01 17:39:29,833 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - M18;
2020-02-01 17:39:30,163 - fabscan.scanner.laserscanner.driver.FSSerial - DEBUG - G07;
2020-02-01 17:39:30,164 - fabscan.scanner.laserscanner.FSHardwareController - DEBUG - Hardware controller initialized...
2020-02-01 17:39:30,430 - fabscan.scanner.laserscanner.FSScanProcessor - INFO - Laser Scan Processor initilized...FSScanProcessor (urn:uuid:511df692-7142-4a1e-8ef1-36bae5746751)
2020-02-01 17:39:30,430 - fabscan.server.FSWebServer - DEBUG - /usr/share/fabscanpi/
2020-02-01 17:39:30,442 - fabscan.FSScanner - INFO - Job scheduler started.
2020-02-01 17:39:30,444 - fabscan.FSScanner - INFO - Scanner initialized...
2020-02-01 17:39:30,446 - fabscan.FSScanner - INFO - Number of cpu cores: 4
2020-02-01 17:39:30,449 - fabscan.lib.util.FSDiscovery - INFO - Registering ip 192.168.2.22 to discovery service.
2020-02-01 17:39:31,042 - fabscan.lib.util.FSDiscovery - INFO - Successfully registered to find.fabscan.org
2020-02-01 17:39:31,154 - fabscan.FSScanner - INFO - Added discovery scheduling job.
2020-02-01 17:40:17,809 - fabscan.server.services.websocket.FSWebSocketHandler - DEBUG - New client connected
2020-02-01 17:40:18,218 - fabscan.FSScanner - DEBUG - Upgrade available: False 0.8.2
2020-02-01 17:40:18,220 - fabscan.scanner.laserscanner.FSScanProcessor - DEBUG - Checking Hardware connections
2020-02-01 17:40:31,158 - fabscan.FSScanner - DEBUG - CPU Temperature: 37.97 C
Thanks for the good idea with the crocodile-clamp. I flashed the bootloader with my familiar notebook and arduino ide.
Best regards
Christoph
Hello Christoph,
When you flashed the bootloader, did you use option A, a Raspberry Pi for flashing, or option B, an Arduino Uno for flashing?
Thank you,
Justin
