Issues with Sammy in 3.3b2

R3D · 29 Mar 2021, 16:30

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

dc42 · 29 Mar 2021, 18:43

Have you used M115 to check that the MB6HC and both SAMMYC21 boards really are running 3.3b2 ?

R3D · 29 Mar 2021, 19:04

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

R3D · 29 Mar 2021, 19:09

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

HTH
Thanks,

R3D · 30 Mar 2021, 17:06

@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.

dc42 · 30 Mar 2021, 17:21

The CoreIO.h file is in the CoreN2G project.

I have just verified that the SAMMYC21 Debug configuration builds OK, using the [edited] 3.3-dev branch of all projects.

R3D · 30 Mar 2021, 17:43

@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)

R3D · 30 Mar 2021, 17:48

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

Thanks,

R3D · 30 Mar 2021, 17:58

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

dc42 · 31 Mar 2021, 08:05

@r3d, I haven't tested the external driver support on SAMMYC21 since I made major changes to the external driver code for the EXP1XD. So that code may be broken on the SAMMYC21.

The changes were to add the code enabled by macro definition USE_TC_FOR_STEP. When that is set to 0 (as it is for the SAMMYC21 build), the code should be essentially the same as it was previously.

R3D · 31 Mar 2021, 16:50

@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,

R3D · 31 Mar 2021, 19:47

@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 · 31 Mar 2021, 20:06

The CAN movement message has changed between RRF 3.2.x and 3.3. This means that RRF 3.2.x cannot cause movement on a SAMMYC21 running firmware 3.3.

R3D · 31 Mar 2021, 22:37

@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 · 12 Apr 2021, 10:30

@r3d, this is now fixed in the 3.3beta source code. I have put a binary at https://www.dropbox.com/sh/oxyezimiusnosxa/AAAgjLNKuTL8oEcXgihZqojXa?dl=0.