RaspPi Image not Working

Hi all,

I’m currently trying to setup 3DPrinterOS on a Raspberry Pi 4 Model B for my Duet2 Ethernet Controller Board (RRF 3.3). I used the proposed way in the guides to create an image and flash it to the RaspPi. However, after booting it does not get an IP-Address via DHCP. In fact, I’m not even sure if it is running properly. Am I missing something? I tried with the Beta and Stable version, with WIFI configuration and without. Any suggestions?

Best regards and thank you in advance.

Hello,
Did you use an Ethernet network connection or a Wifi for RPI?
Did you connect “Duet2 Ethernet Controller Board (RRF 3.3)” with USB to RPI?
Do you have an ability to connect display (hdmi or RPI display) and USB keyboard to check RPI’s loading?
Beta client need to work properly with RPI 4. Today, we have released an updated Stable client, so it need to work with RPI 4 too. Is there any possibility that there was a corruption of image while flashing? Could you try to flash a Beta image again?

Hi,

Thank you for your response! I have tried both, Wi-Fi and Ethernet. Both not working for me tho. Corrupted image is pretty much ruled out, as I’ve tried both variants multiple times. Duet2 Ethernet is connected via USB and worked fine with OctoPrint before. Don’t think that’s the issue. I’ll try the updated Stable as soon as possible. I’ll also try to reinstall the Beta image again, if the stable is still not working. Sadly, I do not have the ability to check with a monitor if everything is working due to the micro HDMI the Pi uses… I might order a corresponding cable, if I can’t get it to work headless.

Best regards!

Edit:

Okay, I’ve tested many variations now, but still can’t get it to work. Tried from Linux and Windows, with Wi-Fi and Ethernet, Stable and Beta, and even different ways to flash the image. Nothing successful so far. Can it be about the Duet Board? It is supported, right? Would it work without having a printer connected? I have no idea what’s wrong. I think I’m getting a micro HDMI cable to see if the Image is working after all. Or do you have any other ideas?

Hi,

Here is a small guide for checking that 3DPrinterOS Client RPi image is booting correctly.

  1. Basically make sure that power supply is connected properly by checking LEDs on the RPi. If the red LED is not lit(and even not blinking), then your RPi simply got no power. A blinking red LED means boot cycle or a power level warning. A green LED indicates a CPU load. Normally it is blinking inconsistently on boot and after it, but less frequently if the software runs correctly. A dim green LED means no boot or a crash.
  2. As a fail-safe measure, connect RPi to your router via ethernet cable. This way we can exclude any possible WiFi issues.
  3. Scan your LAN for and get RPi’s IP
    a) If you got a MS Windows PC or any other access to another 3DPrinterOS Client’s Web UI, then you can use it to detect all machines running 3DPrinterOS in your LAN. To open a Web UI of 3DPrinterOS Client running on local machine, you can type 127.0.0.1:8008 in your browser’s address bar and press Enter. In a Web UI click “Settings”, then “Detect clients in LAN” and see a scan result for correct IPs of all other printer
    b) You can use a third-party network scanner software like, for example nmap(https://nmap.org/zenmap/), to identify an RPi running 3DPrinterOS, take a look at addresses that got ports 22(SSH) and 80(HTTP) open.
  4. If you got a correct IP for your RPi, then you can check its Web UI. To do so, you will need to type this IP into an address bar of a browser on a machine in the same LAN as the RPI running 3DPrinterOS.
  5. A remote WebUI can ask you to authenticate. To do so, you will have to type a you ssh credentials into a fields of 3DPrinterOS client authentication page.
  6. After a authentication you can bind an image to your 3DPrinterOS cloud account or use it in Offline mode.
  7. If your can’t reach remote 3DPrinterOS Client Web UI, then try to connect other ssh. On GNU/Linux or MacOS just type into your terminal following: ssh <ip_of_rpi_in_your_line>. On MS Windows install Putty, enter RPi’s IP and choose SSH.
  8. After login into the RPi thought SSH, you can check 3dprinteros-client status by typing
    systemctl status 3dprinteros. You can also try to retrieve logs are located in ~/.3dprinteros/3dprinteros_client.log and ~/.3dprinteros/critical_errors.log
    The you can send status, logs and a description to issues@3dprintreos.com. Zipped logs are much appreciated.

Hi Vladimir,

red LED is consistantly on and green LED flashing at boot and afterwards flashing up from time to time, but rather rarely, Pi is connected directly to router. To check the IP I’m looking at my Routers UI. It would be there if it gets an IP. I did not try a scanner but I’m sure thats not it. Especially because I bought a micro HDMI to have a look at what happens:

...
USB2[1] 400202e1 connected
USB2 root HUB port 1 init
HUB [01:00] 2.16 00000:01 init port 1 speed 1
USB MSD timed out after 20 seconds
Trying partition: 0
lba: 2048 oem: 'mkfs.fat' volume: ' V         ^ '
rsc 4 fat-sectors 188 c-count 48025 c-size 4 r-dir 1 r-sec 32
Trying partition: 0
lba: 2048 oem: 'mkfs.fat' volume: ' V         ^ '
rsc 4 fat-sectors 188 c-count 48025 c-size 4 r-dir 1 r-sec 32
Read config.txt bytes            232 hnd 0x00007376
Read start4x.elf bytes        3546468 hnd 0x00004bbf
Read fixup4x.dat bytes           9192 hnd 0x00004bb5
Firmware: c3c8dbdf147686fb0c3f32aece709d0653368810 Feb 12 2020 12:37:37
0x00b03115 0x00000000 0x00000007
start4x.elf: is not compatible
This board requires newer software
Get the latest software from https://www.raspberrypi.org/downloads/
Trying partition: 0
lba: 2048 oem: 'mkfs.fat' volume: ' V         ^ '
rsc 4 fat-sectors 188 c-count 48025 c-size 4 r-dir 1 r-sec 32
Trying partition: 0
lba: 2048 oem: 'mkfs.fat' volume: ' V         ^ '
rsc 4 fat-sectors 188 c-count 48025 c-size 4 r-dir 1 r-sec 32
Read config.txt bytes            232 hnd 0x00007376
Read start4x.elf bytes        3546468 hnd 0x00004bbf
Read fixup4x.dat bytes           9192 hnd 0x00004bb5
Firmware: c3c8dbdf147686fb0c3f32aece709d0653368810 Feb 12 2020 12:37:37
0x00b03115 0x00000000 0x00000007
start4x.elf: is not compatible
This board requires newer software
Get the latest software from https://www.raspberrypi.org/downloads/
USB2[1] 400202e1 connected
USB2 root HUB port 1 init
HUB [01:00] 2.16 00000:01 init port 1 speed 1
...

This is just looping. However I’m not really getting what it tries to tell me here… Is it about the Duet Board? Would you please have a look at this?

Thanks in advance

Edit:
It also displays the following information, forgot to provide that earlier.

Raspberry Pi 4 Model B - 2GB
bootloader: c2f8c388 Apr 29 2021
 update-ts: 1619712685

board: b03115 1015082b e4:5f:01:83:a5:97
 boot: mode SD 1 order f41 retry 1/1 restart 3/-1
   SD: card detected 00035344534533324780bb98ac44015c
 part: 0 mbr [0x0c: 00000800 0x83:0002f800 0x00:00000000 0x00:00000000]
   fw: start4x.elf fixup4x.dat
  net: down ip : 0.0.0.0 sn: 0.0.0.0 gw: 0.0.0.0
 tftp: 0.0.0.0 00:00:00:00:00:00

Second Edit:
Nothing changes when the Duet board is not connected!

Thank you for a detailed reply.
We will update the firmware and release a new image.
I’ll make sure to notify you in this thread.

Hi.
Here is a link for new image with an updated kernel and bootloader.

https://builds.3dprinteros.com/3DPrinterOSstable3new.zip

login: printeros
password: printeros

No preconfigured wifi, but you can set it yourself using ssh over ethernet, like this:

/etc/wpa_supplicant/wpa_supplicant-wlan0.conf

p2p_disabled=1
ctrl_interface=/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1
network={
ssid=“yourssid”
psk=“yourpassword”
}

I believe that this image should solve the problem.
Any feedback would be much appreciated.

1 Like

Hi Vladimir

Wow! That was quick - awesome. It’s working now :slight_smile:
Just installed it and everything seems to be fine.

Thank you for your great support. Much appreciated.

It’s working now

I’m glad to read that.
Thank you for reporting this issue, we can fix this in the release version now.