After update 2 v3.2 no response

ahwitmer

@Phaedrux said in After update 2 v3.2 no response:

During the whole process Duet 3 and RPi 4 have been connected with the ribon cable.
The RPi is provided with separate power (switch on Duet set)
Duet 3 is using separate 12V power

The Duet 3 has RRF 3.2 installed as verified by connecting to it via USB terminal and sending M115?
Laptop connected to Duet 3 usb connection the Duet 3 bin file copied to a memory stick in the laptop. Bossa used to transfer it to Duet 3, this has been verified during the update.
Just now verification of firmware revision by connecting the laptop to duet3 via the micro usb connection, using Yaz, M115 results in:
Firmware version 3.2
Firmware_date: 2021-01-05

The Pi4 is powered separately and has a fresh image of DuetPi on a new SD card?
Yes fresh card,
full version downloaded (not Lite), https://pkg.duet3d.com/DuetPi.zip
copied to sd card

You've run sudo apt update and sudo apt upgrade on the Pi?
Started up the printer,
Closed DuetPi
Upper toolbar select terminal
Typed in: sudo apt update
Typed in: sudo apt upgrade
I observed the end of update and of the upgrade, no error messages.

The Pi is now connected to the Duet 3 via ribbon cable and the Duet has no SD card in it?
MicroSD card entry has not been used, cable has never been diconnected during the process.

When powered on, where are you looking and how are you trying to access the duet?
Tried several options:

Via the RPi monitor
via remote login using the duet IP address

Surprising to see that when using the laptop it shows a failure to connect to the Duet, but is does collect the web interface.
In both cases the trying to connect is continuing.

This is the point I got stuck.

If you are currently using the Lite version of DuetPi with no desktop interface, and you are unfamiliar with the Pi in general, it might be a good idea to use the full version of DuetPi and connect it to a display and keyboard and mouse so that you can get a better feel for what is going on rather than just a remote terminal. Even if just for troubleshooting.
Yes indeed I installed the full version, not the lite, got memory enough.

Please note, some weeks ago I upgraded the Duet card, without disconnecting the flatcable.

Hope this helps you in directing my efforts...

Harald

Phaedrux

Can you try this to gather some additional logging?

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional

ahwitmer

@Phaedrux

Typing the first command line:

Typing the second command line:

Apologies for the framing, my iphone considers the picture as a document and crops the picture. If you need a better picture please let me know.

ahwitmer

@ Phaedrux
I read:

Failed to bind to address Http://[::]:80 address already in use

I did not provide an IP address. The RPIDuet is attributed an IP adress by the router, not by me. Any idea what went wrong ?

Although rhe RPI and the Duet are connected, communication between both is not functioning. The PiDuet is working, the Duet is working via micro usb connection but they don't see each other. The RPI is obtaining an IP adress.

Harald

Phaedrux

Still waiting for @chrishamm to get a chance to take a look.

I'm not sure what the problem is with the .Net errors in your screen shot.

Do you happen to have another Pi to test with?

How is your cabling between the Pi and Duet?

ahwitmer

Ah okay I understand.

Unfortunately I have no other RPI available.

Both RPi and Duet have been mounted in a fixed position
MicroSD and Micro USB breakout connectors ar placed on the front of the printer.
The cable has not been disconnected for months
All connectors are accessible without having to dismount anything.
On a hardware level I did not perform any change.

Just before the upgrade, the systems communicated correctly.
I executed the update exactly the same as an earlier version of the firmware. That is why I executed the update to version 3.2 the same.

On 10 January, I reported problems after which I performed the sudo apt update and sudo apt upgrade of the system. This is the only deviation from earlier updates.

ahwitmer

@Phaedrux

In the mean time, I ordered a second RPI to be able to test.
Hope to receive it before the weekend.

ahwitmer

@Phaedrux
Received my spare RPI.

What can you advise me to test ?

Phaedrux

I would put the latest DuetPi image on it, update it, and see if you're getting the exact same errors as before, or whether it's now better.

If there's still no communication we need to check the Duet 3 in standalone mode to ensure it's still working properly.

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Running_in_standalone_mode

ahwitmer

@Phaedrux

Now I report step by step my efforts:

New card formatted using Etcher
New RPI positioned
New RPI, connected with flatcable, provided with separate power, video, mouse keyboard
switched on the printer
During start-up first the message: "Failed to connect to duet, please check your connection (DCS not started)"
In the middle of the screen RPI tries to connect continuously.

Question:
Have not yet performed the sudo update/upgrade on the new RPI. Should I perform the sudo update/upgrade on the new RPI too ?

Please note the original RPI and connection has been working correctly before. I have been able to read temperatures of duet 3 via the rpi etc. Connection went wrong after the update of the firmware in the Duet 3.

Pictures of the ribbon cable connections of the previous

Phaedrux

@ahwitmer said in After update 2 v3.2 no response:

Have not yet performed the sudo update/upgrade on the new RPI. Should I perform the sudo update/upgrade on the new RPI too ?

Yes please.

And if that doesn't work, please try standalone mode to check the Duet 3 is working correctly.

ahwitmer

Last night my RPI performed the rpi auto-update. Again: "Failed to connect to duet, please check your connection (DCS not started)"

Next step (now) sudo update/upgrade

ahwitmer

@Phaedrux
Okay started-up the printer
closed the Duet pi printer screen
activated terminal function

performed the update and the upgrade steps.
This time especially the sudo apt-get upgrade worked out differently compared to the other RPI. This time it says nothing upgraded.
After the actions, restarted the system but unfortunately still the same error message:
"Failed to connect to duet, please check your connection (DCS not started)"
also in the middle of the screen a window continuously running, indicating to connect.
See the picture below:

Phaedrux

Ok, we're not getting anywhere with the Pi. Please setup standalone Duet 3.

Disconnect the ribbon cable
Connect network cable to Duet3
Prepare an SD card for the Duet3 formatted as FAT32
SD card should contain these folders: sys, www, gcodes, macros, menu
Generate a config file set with the config tool: https://configtool.reprapfirmware.org/Start
At the end make sure you check off to include the most recent DWC and firmware files.
extract that to the SD card and make sure the folder structure looks something like this: https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure
check the config.g to make sure network startup is enabled and specify a static IP address if you want
boot up the Duet 3 and try to reach the IP address to load the DWC.

ahwitmer

@Phaedrux
Perhaps a dum question, I just want to understand, you mention an update for DWC

Until now I have the 3.2 firmware upgrade package (Duet2and3Firmware-3.2.zip), however I do not think I intentionally downloaded an update for DWC 3.2.

When searching for the download for DWC I read that you need to have the correct version for the correct firmware. Where do I find the right version?

Question 2
Just to be sure, in following steps, you indicate a make a folder structure. Do you mean like the picture below the "Old method" or just folders "sys, www, gcodes, macros, menu"

Phaedrux

@ahwitmer said in After update 2 v3.2 no response:

(Duet2and3Firmware-3.2.zip), however I do not think I intentionally downloaded an update for DWC 3.2.

DWC is included in that zip file.

For the SD card the important thing is you have those folders you listed, and that your config files are in the /sys folder and the DWC files are in the /www folder.

If you follow these steps:

Generate a config file set with the config tool: https://configtool.reprapfirmware.org/Start
At the end make sure you check off to include the most recent DWC and firmware files.

You will get what you need.

chrishamm

@ahwitmer If it did work with 3.1.1 but not with 3.2, the most likely reason is an SD card in the Duet. Please double-check that there is no card in the Duet but in the Pi. If that is the case, connect a USB cable to the Duet, open a serial console, and send M122. It should report that RRF is operating in SBC mode, not standalone mode.

Last but not least try to downgrade to 3.1.1 again and check if DSF can connect then.

ahwitmer

@chrishamm Thank you for the suggestion. Until today I have not been using the Duet 3 sd card entry at all. I have been working via the RPI all the time.
I had to free access to the SD card connection because the Duet 3 is built-in to an enclosure
I did use the Duet 3 USB connection to update the firmware.

@Phaedrux @chrishamm I'm happy to report that the stand alone version does work.
It is possible to connect with the Duet 3 motherboard using my external pc.

Now back to the RPI use
The Duet 3 does work
Using two (2) different RPI's results in the same communication problems.
Obviously there is a communication problem.
Before version 3.2 the communication existed.

Originally the RPI was connected using the flat cable according to the picture below.

ahwitmer

Until now, I only updated the Duet 3. The expansion boards (3) I did not yet update.
Could it be that the communication problems are caused by the different firmware versions?

Phaedrux

I suppose that's possible, but I'm not sure.

When you're in standalone mode please send M122 and M122 B1 (B2, B3, etc for each expansion board you have) and report the results here please.