New RepRapFirmware 3.0 early beta

martink

The SAME70 configuration include paths for FreeRTOS include src/portable/GCC/ARM_CM0. Changing that to src/portable/GCC/ARM_CM7/r0p1 helps. I haven't tried using the resulting firmware binary.

wilriker

@martink Thanks for spotting that! This fixes linker errors. And it flashs fine so far.

dc42

@martink said in New RepRapFirmware 3.0 early beta:

The SAME70 configuration include paths for FreeRTOS include src/portable/GCC/ARM_CM0. Changing that to src/portable/GCC/ARM_CM7/r0p1 helps. I haven't tried using the resulting firmware binary.

Thanks, fixed in latest commit.

gtj0

@dc42 said in New RepRapFirmware 3.0 early beta:

@martink said in New RepRapFirmware 3.0 early beta:

The SAME70 configuration include paths for FreeRTOS include src/portable/GCC/ARM_CM0. Changing that to src/portable/GCC/ARM_CM7/r0p1 helps. I haven't tried using the resulting firmware binary.

Thanks, fixed in latest commit.

@dc42 Any idea on the homing issues?

dc42

@gtj0 said in New RepRapFirmware 3.0 early beta:

@dc42 said in New RepRapFirmware 3.0 early beta:

@martink said in New RepRapFirmware 3.0 early beta:

The SAME70 configuration include paths for FreeRTOS include src/portable/GCC/ARM_CM0. Changing that to src/portable/GCC/ARM_CM7/r0p1 helps. I haven't tried using the resulting firmware binary.

Thanks, fixed in latest commit.

@dc42 Any idea on the homing issues?

I'm sorry, this thread has got so long that it's difficult to track the different issues raised in it. Please start a new thread for that issue.

smoki3

@dc42 said in New RepRapFirmware 3.0 early beta:

@smoki3 said in New RepRapFirmware 3.0 early beta:
@dc42
It was definitely not like this on 2.02 and the older 3.0.

And its a really wired behaviour. Because I use:
; tfree0.g
; called when tool 0 is freed
;
; generated by RepRapFirmware Configuration Tool on Wed Sep 19 2018 21:12:53 GMT+0200 (Mitteleuropäische Sommerzeit)
G91
G1 Z10 F7200
G90
G53 G1 X0 F25000 ;XPOS
G53 G1 Y190
G53 G1 Y195 F5000
M400
M98 P"/macros/Toolhead/1. Toolhead unlock"
G4 P320
G53 G1 Y207 F5000
M400
G53 G1 Y165 F25000
M400
; tpre1.g
; called before tool 0 is selected
;
; generated by RepRapFirmware Configuration Tool on Wed Sep 19 2018 21:12:53 GMT+0200 (Mitteleuropäische Sommerzeit)
G1 X76 F25000
M400
G1 Y192
M400
M98 P"/macros/Toolhead/1. Toolhead unlock"
G4 P400
G1 Y207 F5000
M116 P3
M400
M98 P"/macros/Toolhead/2. Toolhead lock"
G4 P260
G1 Y150 F15000
The I only expect that only a X movement is done while the start of the tpre1.g but it first moves in X and Y.
@smoki3, I am looking into this but I need your config.g file, also the toolhead unlock files that you call from the tool change files.

I uploaded my config files and my tool changer macros:

Config:
https://drive.google.com/file/d/1xQ5j9E2WvJNFzIum62W02iligk8rOv4T/view?usp=sharing

Macros:
https://drive.google.com/file/d/1QcHqPQBpafr3AlDOjGM3XtQ7nB4VcalO/view?usp=sharing

smoki3

@dc42 have you downloaded the files?

dc42

Sorry, I've no time to look into it this week - I'm working on a very tight deadline for Duet 3. I expect to have time next Tuesday/Wednesday.

Marco Bona

Is it possible to have an example of the parameter m308 connected to the pt100 sensor board?

dc42

M308 S1 Y"rtdmax31865" P"spi.cs1"

Marco Bona

Perfect, work with Y"rtd-max31865".
Thanks

blt3dp

I had a question about RRF3 on a Duet 3 Pre-Release 0.6 board. Is there an inbuilt fan behavior like the Duet 2. For example, Fan1 was "kind of specified" as the heatsink fan and was configured to power on the fan when the Duet was powered up just in case the temperature was above the set theromstatic threshold. Then when config.g kicked in it would actually begin checking if it were at the threshold or not and decide what to do with the fan.

dc42

No. https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Default_pin_assignments

blt3dp

Gotcha, so it could be plugged in anywhere on out4-out9, be defined as fan1 using M950. M106 can be used somewhere after that M950 to set that fan to thermostatic? The feature to turn that fan on full at power on I'm guessing isn't possible or needed because the fan won't be defined until config.g is loaded as well as config loads so quick that it doesn't matter if that fan is on at power up cause it's only a fraction of a second that it might not be.

deckingman

@blt3dp Sort of. But because nothing is defined by default, then before you can use a fan in thermostatic mode, you first have to define a sensor, then a heater that you can associate the fan with.

So starting with the sensor and assuming that you have already defined S0 to be the bed sensor, and if you want to replicate the behaviour of Duet 2, you would probably elect to use S2 as the hot end sensor. So you would have something like:

M308 S1 A"Hot End Temp" P0.temp1" Y"thermistor" Tnnn Bnnn C etc....

Then you define the heater so something like:

M950 H1 C"0.out1" T1 .

You might find that a little confusing because in M308 the sensor is referred to by the "S" parameter but in M950 the sensor is referred to be the "T" parameter.

Then for you fan you'd have something like

M950 F1 C"0.out6"
followed by something like:

M106 P1 S255 H1 T60 C "Hot End Fan". (where T is the value that you want the fan to turn on at). Here "P" is the fan number ad "H" is the heater number.

Substitute your own pin numbers in the above.

blt3dp

Thanks for clarifying, I was going off the assumption that I had already defined sensors and heaters.