Posts made by pgoellner

I tested the "better" BuildInstructions.md but there are 5 errors left.

The branches i use according the instruction:

Error screenshot:

Full errorlog:
RRF3.11 Duet3 build errorlog.txt

Futhermore i try build the latest development according the instruction with the RRF build configuation "Duet3" which builds without errors.

But i would like use a stable release. Are there any other recommendations?

Hello everyone!

I am trying to build the RepRapFirmware Release 3.1.1 based on the BuildInstructions.md of the related branch. At the last step (13) where building the components and the RepRapFirmware i've got various errrors.

Might you please let me know the related tags / branches of the depending repostories to build the RepRapFirmware in version 3.1.1.

Also let me know about additional information, e.g. build order, in case it's relevant.

Thank you

P.S.: I am using a Duet3 Mainboard 6HC v1.0 with a ATSAME70Q20 chip which means for me that i must use the "SAME70" build configuration at CANlib, CoreNG, RRFLibearies & RepRapFirmware.

@dc42 Thanks, that solve my Problem . This should perhaps be covered by a "DEBUG-BUILD-FLAG".

Now with attachments

Duet3Firmware.7z.002_.g Duet3Firmware.7z.001_.g Duet3Firmware.bin_.g config.g

Hello everyone!

My second post here and got some stochastic “SoftwareResetReason::stackOverflow” when my robot moves (See attached screenshot).

-> RepRapFirmware: v3.01-dev [Debug-Build] (Commit hash 5dda6c9d5aaa24ea94f9246db73e702580e5d0dc).

In the function stackOverflowDispatcher(pulFaultStackAddress, pcTaskName) in Tasks.cpp I got the values pulFaultStackAddress= 0x2045ffac and pcTaskName= TMC.

So thinking that there is maybe an issue in Stepper Drivers at TMC, but actually I don’t know exactly.

Does anyone know this problem or how to fix it?

Thanks in advance,
Best Peter

Hardware

• Duet 3 Board (ATSAM70Q20)

Duet 3 Firmware

• RepRapFirmware: v3.01-dev [Debug-Build] (Commit hash 5dda6c9d5aaa24ea94f9246db73e702580e5d0dc).
• RRFLibraries: dev
• CoreNG: dev
• FreeRTOS: master
• DuetWiFiSocketServer: master

[4_1593442677965_Duet3Firmware.bin](Uploading 100%) [3_1593442677965_Duet3Firmware.7z.002](Uploading 100%) [2_1593442677965_Duet3Firmware.7z.001](Uploading 100%) [1_1593442677965_config.g](Uploading 100%) 

@Phaedrux Thanks for that respone.

Hi everyone,

I´m new here and try to set up a new kinematics.
For that reason my axis have to be in a “(continuous-) rotation-mode” which means that all angles must be in 0..360° (-> Angle%360).
From my transformation I got values from between 0° and 360° (or +-180°).
If I will do a move from 0° to 350° the axis should not move +350°, instead the axis should take the “short” path with -10°.

I enable in my kinematics class the function “IsContinuousRotationAxis(){… return = true;}”.
In my opinion this should solve this problem but it don’t.
Did I something wrong, or do I miss a setting?

Thanks in advance, Best Peter

Duet 3 Firmware (RepRapFirmware: v3.01-dev; RRFLibraries: dev; CoreNG: dev; FreeRTOS: master; DuetWiFiSocketServer: master)