Internal Error in TaskLoop in Duet3-Mini SBC Mode only

poofjunior

Hey folks,

I'm getting this error on the console when I try to home y. (Motors also energize but no movement happens.)

Error: Internal Error in TaskLoop at ../src/Linux/LinuxInterface.cpp(104)

My setup is:
RepRapFirmware for Duet 3 Mini 5+ version 3.2-beta3.2+1 running on Duet 3 Mini5plus Ethernet (SBC mode)

(Duet 3 Mini, Raspi, and 3HC)

I'll mention: before I was running in SBC mode, I was able to run the machine in standalone mode and home normally with identical configs (except for the network settings MCodes).

My homey.g file is as follows:

; Home Y Axis

; In case homey.g is called in isolation, ensure
; (1) Endstop is not already triggered (in case of damaged endstop)
; Ask for user-intervention if any case fails.

if sensors.endstops[1].triggered
  M291 "Cannot Home Y" P"Y Endstop is already triggered!" S2
  abort "Y Endstop was triggered before homing."

G91                     ; Set relative mode
G1 Y-400 F6000 H1       ; Big negative move to search for endstop
G1 Y4 F600              ; Back off the endstop
G1 Y-10 F600 H1         ; Find endstop again slowly
G90                     ; Set absolute mode

I'll mention that there's some logic above to behave differently if the endstops are already triggered, but they were untriggered when I was running it.

Finally, the first few lines of

apt-cache show duetsoftwareframework

shows:

Package: duetsoftwareframework
Architecture: armhf
Version: 3.2.2
Priority: standard
Section: electronics
Maintainer: Duet3D Packaging Authority <pkg@duet3d.com>
Depends: duetcontrolserver (= 3.2.2), duetsd (= 1.1.0), duettools (= 3.2.2), duetwebserver (= 3.2.2), duetwebcontrol (= 3.2.2), reprapfirmware (>= 3.2.2-1), reprapfirmware (<= 3.2.2-999)
Filename: dists/stable/armv7/binary-armhf/duetsoftwareframework_3.2.2_armhf.deb

Any thoughts would be most appreciated!

gloomyandy

@poofjunior Are you really running RRF 3.2-beta3.2+1? Any reason why you have not upgraded to 3.2.2?

Phaedrux

It looks like your firmware versions are out of whack. You've got 3.2beta2+1 on the board, but DSF 3.2.2 on the Pi.

How are you doing your updates? What version are you wanting to run?

poofjunior

@gloomyandy huh; that output was after I ran

sudo apt update
sudo apt upgrade

Do I still need to plop the firmware into the Duet 3 Mini Web Interface, or does the duetsoftwareframework package not do this for you?

Phaedrux

It can get a little out of whack when using beta version that haven't been installed from the unstable branch on the Pi. I suggest you upload the 3.2.2 zip file to the mini via DWC. If that doesn't prompt for a firmware update, then send M997 to initiate it.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip

That should get you back in sync with 3.2.2.

poofjunior

@phaedrux Yup that did it! Uploading the zip and installing the latest firmware fixed it.

Cheers--and thanks for mentioning that I was behind!

Phaedrux

3.3 final should be out soon hopefully and then you'll be able to update with the normal sudo apt update commands.

poofjunior

@phaedrux I am very excited for it! Thanks for the heads-up.