2 SD Cards - SBC - stop after pause.g 3.5beta2

Phaedrux

I would try doing a full format on one of the sandisk ultra SD cards using the SD card formatter tool. Then try imaging it again with etcher. Failed flashes are not normal, no.

@IndeX4D said in 2 SD Cards - SBC - stop after pause.g 3.5beta2:

Can I also use M122 P104 S20 with sbc?

I don't think so, but maybe.

@IndeX4D said in 2 SD Cards - SBC - stop after pause.g 3.5beta2:

Sadly I have to use any of 3.5 versions cause of closed loop steppers.

Ah, I understand. Even so, it would be good to see how it behaves in 3.4.5 before updating to the 3.5 beta.

IndeX4D

@Phaedrux OK I format the cards and I´ll try it again to flash.
Should I take the newest duetpi version?

I´ll try 3.4.5. in a few min.

Edit: Also when Flash Failed, I have the problem with 2 Sd Cards and printer is running.

thanks

IndeX4D

@Phaedrux

After format, flash is failed. Also with the other sd cards. But I can start duet and print with same problems.

It makes no sense to go ahead with testing when flashing failed, right?

Phaedrux

what is the error when the flash fails?

IndeX4D

This post is deleted!

IndeX4D

@Phaedrux

Strange that I can still print with failed flashing, but my problem occured with a succesful flash.

Can you say what kind of error it is?

Phaedrux

I don't know. But it looks like it failed on verify near the end with a strange error. Maybe try re-installing etcher with a fresh download. Or try a different SD card flasher.

Did you do a full format of the SD card? That's a good way to force it to remap any bad sectors and make sure it's entirely writable.

As for what is happening with the second SD card showing, perhaps @chrishamm knows.

IndeX4D

@Phaedrux
Strangely flashing is failed earlier. Feels like the sd cards are more crazy with every step.
I'll buy new sd card, flash from different computer and use different raspberry.
I'll tell my experience later.

chrishamm

@IndeX4D In SBC mode do NOT touch any files on the second SD card partition (which is /boot on the SBC system or the first FAT partition). This partition contains boot files for the SBC Linux system and several files for standalone mode, so if you delete arbitrary files from there, your SBC will not start any more.

You can use the Raspberry Pi Imager if the other flash tools fail - just make sure you don't have read-only protection set on your SD adapter. M122 P104 is not supported in SBC mode, there are other Linux utilities for the same purpose.

IndeX4D

@chrishamm thanks for your answer

I´ll try everything again with completly new setup in a few minutes,

IndeX4D

Is it ok to run sbc with ethernet not only temporary?

Phaedrux

What do you mean?

IndeX4D

@Phaedrux
Boot was successful. Can't connect WiFi.
But I could use ethernet cable to connect with my router? Is this also fine?

Connected to WIFI!

New SD Card works fine.
SO, only to be sure. Now, I see DWC and have a terminal open to update. Should I upload my sy files in sys folder first, or should I update first?
thanks

Phaedrux

You can use wifi or ethernet on the SBC. That's up to you.

You can update the pi first and then upload your config files later through DWC.

IndeX4D

@Phaedrux

So I don´t know whats wrong. Everything was working fine, but same problem happens. Press pause --> stuck
Interesting. First press pause was working fine with m226 in line in pause.g. But after resuming, it was printing slow till next zhop. then I executed pause again --> Stuck

I changed
-->
Computer to flash
NEW Sd card
Other raspberry
Software versions from 3.4.6 to 3.5 beta3.

The last thing I do is to try it with a also complete new set up for another printer.

Phaedrux

Please post your pause.g and resume.g files

IndeX4D

@Phaedrux
resume.g

G1 R1 X0 Y0 Z5
G1 E0.2 F3600  ; retract 10mm of filament
G1 R1 X0 Y0 Z0

pause.g

; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Aug 02 2021 16:15:35 GMT+0200 (Mitteleuropäische Sommerzeit

M83            ; relative extruder moves
G1 E-0.2 F3600  ; retract 10mm of filament
G91            ; relative positioning
G1 Z5 F360     ; lift Z by 5mm
G90            ; absolute positioning
G1 X200 Y200 F6000 ; go to X=0 Y=0

Phaedrux

Ok after jumping through some hoops I think we've arrived at the actual issue.

There seems to be an issue with pause and resumed speeds when using closed loop steppers and 3.5 beta 2 and 3.

Can you make a video of what you see happening when you pause and resume?

IndeX4D

@Phaedrux
yes I can do.
How can I share it?
mostly the size is to big.... give me a second.

I have this only by using SBC mode.
Could be, that I had some slow down in standalone mode. No freezing. Im not sure, but this always disappeared after short a while.

So no need to try at another printer?

Phaedrux

Perhaps you can upload the video to dropbox or google drive or something like that and share a link here.

No I don't think we need to try and a completely different printer at this point.

Can you send M122 on the current machine and share the results here?
Also please send M98 P"config.g" and share the results.
Also share your config.g as it currently is.