Posts made by R3D

@dc42 yeah it is only ever the bottom sensor that exhibits that behavior. I am fairly confident my connector crimps are good as I have tried to shake/shimmy the harness around while heated and attempted to recreate the readings but they were stable. I just hate that the problem is so inconsistent and hard to replicate. I will start by replacing the sensor and double checking my connections on both sides and see if that fixes the issue.

I have a large 3d printer with a Dyze Typhoon extruder with 2 pt100 sensors controlling two separate heaters. Each pt100 is connected to 4 wires in pairs of twisted wire, covered in a grounded shield and no other cables run through the shield other than some grounds. They then go to the duet amplifier board on my MB6HC running in SBC mode running FW 3.4.6. I have had many successful prints before this issue popped up but now I have many failed prints due to heater fault errors and I do not understand where it is coming from. My heater tune is stable and when not printing there doesn't seem to have an issue. I have pictures below that show what I am seeing on the temperature graph. Any help would be greatly appreciated.

Thanks,

@t3p3tony No I only have a single part on the build plate, albeit a large one. I will upgrade to 3.3 and see if that produces similar error messages.

Duet 2 running 3.2.2 standalone. I don't have issues with smaller prints but when I am printing a larger part, the print fails halfway through with a software reset.

M122 lists the reason as a HardFault bfarValid precise, none spinning. Full M122 ouput below.

console (1).txt

tried to find some similar issues on this and came to a few that ranged from a bad board to a bad SBC and some were firmware related. would like to know what I can do to figure out what is happening. Config.g is below too if that helps.

config.g

I appreciate any help in this.

@dc42 Sorry if I wasn't clear, I rolled back firmware on both the MB6HC and the SammyC21s. Both are now running 3.2.2

Thanks,

@dc42 So I rolled back to 3.2.2 and tested, again I had no movement. I wanted to see if I could see the step pulse being generated so I probed PA11 while commanding a long slow move to give me time to get a clear probe picture, and this was the only discernable signal I saw. I am no electrical engineer but this looks woefully inadequate as it looks like it hardly sinks 500mv, unless I am reading the scope wrong... any suggestions?...also the second pic was after the move had finished....looks just like the first.

Thanks.

@dc42 I do see that it is set to 0 in BoardDef.h, would you suggest to run a different firmware other than 3.3b2? Perhaps 3.2.2?

Thanks,

@dc42 OKay, so now the sammys show they are running 3.3b2 but I still do not have any movement at all....

@dc42 Just realized I did not have FreeRTOS included.... it compiled OK now, will test and see if new binary works.

Thanks,

@dc42 Im not sure if I am just doing something wrong but I keep coming up with build errors now saying something like this.

In file included from C:\Users\Tony\git\Duet3Expansion\src/Tasks.h:12,
from C:\Users\Tony\git\Duet3Expansion\src/Movement/DDA.h:12,
from ../src/Movement/Kinematics/CartesianKinematics.cpp:9:
C:\Users\Tony\git\RRFLibraries\src/RTOSIface/RTOSIface.h:23:11: fatal error: FreeRTOS.h: No such file or directory
23 | # include "FreeRTOS.h"
| ^~~~~~~~~~~~
compilation terminated.
make: *** [src/Movement/Kinematics/CartesianKinematics.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from C:\Users\Tony\git\Duet3Expansion\src/AdcAveragingFilter.h:12,
from C:\Users\Tony\git\Duet3Expansion\src/Platform.h:12,
from ../src/Movement/Kinematics/Kinematics.cpp:11:
C:\Users\Tony\git\RRFLibraries\src/RTOSIface/RTOSIface.h:23:11: fatal error: FreeRTOS.h: No such file or directory
23 | # include "FreeRTOS.h"
| ^~~~~~~~~~~~
compilation terminated.
make: *** [src/Movement/Kinematics/Kinematics.o] Error 1
In file included from C:\Users\Tony\git\Duet3Expansion\src/Tasks.h:12,
from C:\Users\Tony\git\Duet3Expansion\src/Movement/DDA.h:12,
from C:\Users\Tony\git\Duet3Expansion\src/Movement/Move.h:17,
from ../src/Movement/Kinematics/LinearDeltaKinematics.cpp:10:
C:\Users\Tony\git\RRFLibraries\src/RTOSIface/RTOSIface.h:23:11: fatal error: FreeRTOS.h: No such file or directory
23 | # include "FreeRTOS.h"
| ^~~~~~~~~~~~
compilation terminated.
make: *** [src/Movement/Kinematics/LinearDeltaKinematics.o] Error 1
In file included from C:\Users\Tony\git\Duet3Expansion\src/Tasks.h:12,
from ../src/Movement/DDA.h:12,
from ../src/Movement/DDA.cpp:8:
C:\Users\Tony\git\RRFLibraries\src/RTOSIface/RTOSIface.h:23:11: fatal error: FreeRTOS.h: No such file or directory
23 | # include "FreeRTOS.h"
| ^~~~~~~~~~~~
compilation terminated.
make: *** [src/Movement/DDA.o] Error 1
'Finished building: ../src/Movement/StepperDrivers/DriverMode.cpp'
' '
'Finished building: ../src/Movement/StepperDrivers/TMC51xx.cpp'
'Finished building: ../src/Movement/StepperDrivers/TMC22xx.cpp'
' '
' '
'Finished building: ../src/Movement/Kinematics/ZLeadscrewKinematics.cpp'
' '
"make -j8 all" terminated with exit code 2. Build might be incomplete.

12:41:04 Build Failed. 9 errors, 0 warnings. (took 4s.179ms)

@dc42 OK so i think I am getting somewhere, the Master branch of the Duet Expansion is still 3.2 while the dev branch is the 3.3b2, but now when I attempt to compile it I keep getting an error about missing CoreIO.h which I cant seem to find in any of the source files.

Thanks.

May be noteworthy that I am using the debug version of the firmware loaded with the ICE tool.

HTH
Thanks,

MB6HC shows 3.3b2 but the Sammy's showed 3.1.0+

I have a machine running 3.3b2 on a MB6HC standalone and the only CAN connected devices are my 2 Sammy boards, also updated to the 3.3b2 firmware binaries with no special code added as I am only using them as external drivers. I have triple checked my wiring and I do have both Step + and Dir + tied to the 5V source of the Sammys and the Step- and Dir- to pins PA11 and PA10 respectively. Below are the M122 responses from all three boards.

console.txt

Whenever I send a command to test movement, I receive this following message along with zero movement.

Any thoughts?

Thanks

I do have my Z motors wired to the Mainboard but I have the Z-probe wired to a tool board, and all of the motors driven by the tool boards are using sensorless homing.

Thanks for the clarification @DC42

That's what I figured but wanted to make sure before I finish wiring up my lift axis.

Thanks for the quick response BTW

Just curious if it is currently possible in the tool board firmware to use the stepper driver to drive a non extruder stepper motor?

Just spitballing, is there a way to force a tool as active without running the tpre#.g files?

Running 3.1.1 on Duet 3 with 3 Tool boards and 2 external drivers

So I have a large scale toolchanger and I have been trying to get all of my tool selection gcode tweaked to work really well, and now when I tested a tool selection, the machine goes through the tpre0.g as it should but then it doesnt actually change the state of tool 0 to active, and if I send another T0, it reruns the tpre0.g ... not sure whats happening here.

tpre2.g tpre1.g tpre0.g tpost2.g tpost1.g tpost0.g tfree2.g tfree1.g tfree0.g homez.g homey.g homex.g homec.g homeall.g config.g cancel.g bed.g