RepRapFirmware 3.0 first official beta is out

A Former User

Looks good at a glance, minor formatting glitch in the list way at the bottom, has visible [code] tags.

DuetPi.img 3.2G - this could probably be compressed to save some bandwidth and or time.

Edit:

You will need at least an 8Gb class 10 SD card.

If using a larger card you may wish to expand the filesystem to utilize the adittional space. Run sudo raspi-config nonint do_expand_rootfs to expand the filesystem to span the whole card.

One this is complete Windows may prompt you to format the disk. Do not do this, it is because Windows does not recognise one of the partitions on the image.

Once

Create a new file named “wpa_supplicant.conf” (exact naming is critical, do not have a ".txt" at the end of the file).

This file already exists in the image btw

In a text editor add the following:
country=GB
Replacing the SSID_OF_NETWORK with your wifi SSID and PASSWORD_OF_NETWORK with your password.
Save and safely eject the SD card

Might be obvious to some, but changing the country code for compliance with wifi certifications might be mentioned here. Which channel the driver will allow the wifi chip to use is dependent on this setting. Two letter country code from https://en.wikipedia.org/wiki/ISO_3166-1#Officially_assigned_code_elements

If none of these steps work see the Troubleshooting Duet 3 - SBC communications documentation.

dead link

Image Size and compression: DuetPi.img 3,447,717,888 vs DuetPi.img.bz2 864,099,605 - maybe not everyone is living in purgatory with a 4Mbit downstream. Also consider adding MD5/SHA1 signature files to help verify the download.

tdybare69

@bearer WHERE DO I GET THE DUET 3D REPOSITORY.

tdybare69

@tdybare69 said in RepRapFirmware 3.0 first official beta is out:

@bearer WHERE DO I GET THE DUET 3D REPOSITORY.

i got it working the hard way but it is missing files. i am going to try your way. then maybe i can get the bltouch to work
i keep getting a m280invalid servo index 5 in m280 command.

T3P3Tony

@tdybare69 can you start a new thread with the specific issue.

If by "missing files" you mean the printer configuration for your printer, you do need to generate that yourself, looking at the issues you are reporting i would start by checking.

https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_M280

and you will need to setup the specific pin you are using for the BL touch servo using M950.

tdybare69

@T3P3Tony i have plugged it in according to the diagram. black and white on the probe 2 right pins. the red on pin1 , brown on pin 2, and the orange on pin 8.

tdybare69

no i mean there is no override file,or deploy.g, or retaract.g. those r just the ones i know about. i am new to this.

tdybare69

@tdybare69 said in RepRapFirmware 3.0 first official beta is out:

no i mean there is no override file,or deploy.g, or retaract.g. those r just the ones i know about. i am new to this.
there is one guy at matter hackers that ben helping but they dont deal with bl touches alot.

tdybare69

@bearer said in RepRapFirmware 3.0 first official beta is out:

Looks good at a glance, minor formatting glitch in the list way at the bottom, has visible [code] tags.

DuetPi.img 3.2G - this could probably be compressed to save some bandwidth and or time.

here is my config.g file.
; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.0.4 on Tue Sep 17 2019 19:45:33 GMT-0400 (Eastern Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Turnigy" ; set printer name

M667 S1 ; select CoreXY mode

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E97.00 ; set steps per mm
M566 X600.00 Y600.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z180.00 E1500.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E10000.00 ; set accelerations (mm/s^2)
M906 X950 Y950 Z950 E950 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X330 Y330 Z400 S0 ; set axis maxima

; Endstops
M574 X1 Y1 Z1 S0 ; set active low and disabled endstops

; Z-Probe
M307 H3 A-1 C-1 D-1 ; disable heater on PWM channel for BLTouch
M558 P5 H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X73 Y35 Z2.5 ; set Z probe trigger value, offset and trigger height
M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters
M557 X15:215 Y15:195 S20 ; define mesh grid

; Heaters
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Fans
M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H-1 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 S"HotEnd" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

kraegar

A bit over 20 hours of printing later I'm reporting back that things have been very stable since getting the correct version running. No issues to report!

dc42

@tdybare69 said in RepRapFirmware 3.0 first official beta is out:

; Z-Probe
M307 H3 A-1 C-1 D-1 ; disable heater on PWM channel for BLTouch
M558 P5 H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds

Those are settings for RepRapFirmware 2. They (and maybe other things in config.g) need to be changed for RepRapFirmware 3. See https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview.

T3P3Tony

@kraegar said in RepRapFirmware 3.0 first official beta is out:

A bit over 20 hours of printing later I'm reporting back that things have been very stable since getting the correct version running. No issues to report!

Thanks for the update.

Dougal1957

@T3P3Tony I have run the update SW Stuff but mine is still reporting 1.0.3.1 and won't go to 1.0.3.3 or whatever it's supposed to is there any other steps that need to be done first and please KISS for this very uninformed new LINUX User?

Doug

A Former User

@Dougal1957 said in RepRapFirmware 3.0 first official beta is out:

is still reporting 1.0.3.1 and won't go to 1.0.3.3 or whatever it's supposed to

1.0.3.3 is in the unstable repo, which are you using?

(
Official image uses stable repo, so thats limited to 1.0.3.1 until Duet3D put 10.3.3 in that. Or you could add the unstable repo:

sudo bash -c "echo deb https://pkg.duet3d.com/ unstable armv7 >> /etc/apt/sources.list.d/duet3d-unstable.list"
sudo apt update
sudo apt upgrade duetsoftwareframework

)

smoki3

@Marco-Bona said in RepRapFirmware 3.0 first official beta is out:

With this build I encounter problems with heater mapping. The values found are -273 with the exception of the heated chamber which is correct.

; 9 _ HEATERS

M308 S0 P"bed_temp" Y"thermistor" A"Bed thermistor" T100000 B3950
M308 S1 P"spi.cs1" Y"rtd-max31865" P"spi.cs1" A"RTD1"
M308 S2 P"spi.cs2" Y"rtd-max31865" A"RTD2"
M308 S3 P"e2_temp" Y"thermistor" A"Chamber thermistor" T100000 B4725 C7.06e-8

M950 H0 C"bed_heat" T0
M950 H1 C"e0_heat" T1
M950 H2 C"e1_heat" T2
M950 H3 C"duex.e2heat" T3

@smoki3 said in RepRapFirmware 3.0 first official beta is out:

I have problems with the thermistors on this build on my Duet2Wifi. T0,T1 and Bed shows -273 °C. The thermistors on the duex5 are fine. They are defines as:

; Thermal Sensors
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 R4700                    	; Set thermistor + ADC parameters for heater 0
M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 1
M308 S2 P"e1_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 2
M308 S3 P"e2_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 3
M308 S4 P"e3_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 4

; Hardware
M950 H0 C"bed_heat" T0
M950 H1 C"e0_heat" T1
M950 H2 C"e1_heat" T2
M950 H3 C"!exp.heater3" T3
M950 H4 C"!exp.heater4" T4

If I ask for the Statuts with M308 S1I get correct values:

M308 S1
Sensor 1 type Thermistor using pin e0temp, reading 22.1, last error: success, T:100000.0 B:4725.0 C:7.06e-8 R:4700.0 L:0 H:0

Is there any solution to fix thermistor on Duet 2 Wifi?

Dougal1957

@bearer said in RepRapFirmware 3.0 first official beta is out:

@Dougal1957 said in RepRapFirmware 3.0 first official beta is out:

is still reporting 1.0.3.1 and won't go to 1.0.3.3 or whatever it's supposed to

1.0.3.3 is in the unstable repo, which are you using?

(
Official image uses stable repo, so thats limited to 1.0.3.1 until Duet3D put 10.3.3 in that. Or you could add the unstable repo:
sudo bash -c "echo deb https://pkg.duet3d.com/ unstable armv7 >> /etc/apt/sources.list.d/duet3d-unstable.list"
sudo apt update
sudo apt upgrade duetsoftwareframework
)

Thankyou that's the bit I was missing now sorted

smoki3

@smoki3 said in RepRapFirmware 3.0 first official beta is out:

@Marco-Bona said in RepRapFirmware 3.0 first official beta is out:

With this build I encounter problems with heater mapping. The values found are -273 with the exception of the heated chamber which is correct.

; 9 _ HEATERS

M308 S0 P"bed_temp" Y"thermistor" A"Bed thermistor" T100000 B3950
M308 S1 P"spi.cs1" Y"rtd-max31865" P"spi.cs1" A"RTD1"
M308 S2 P"spi.cs2" Y"rtd-max31865" A"RTD2"
M308 S3 P"e2_temp" Y"thermistor" A"Chamber thermistor" T100000 B4725 C7.06e-8

M950 H0 C"bed_heat" T0
M950 H1 C"e0_heat" T1
M950 H2 C"e1_heat" T2
M950 H3 C"duex.e2heat" T3

@smoki3 said in RepRapFirmware 3.0 first official beta is out:
I have problems with the thermistors on this build on my Duet2Wifi. T0,T1 and Bed shows -273 °C. The thermistors on the duex5 are fine. They are defines as:
; Thermal Sensors
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 R4700                    	; Set thermistor + ADC parameters for heater 0
M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 1
M308 S2 P"e1_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 2
M308 S3 P"e2_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 3
M308 S4 P"e3_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 4

; Hardware
M950 H0 C"bed_heat" T0
M950 H1 C"e0_heat" T1
M950 H2 C"e1_heat" T2
M950 H3 C"!exp.heater3" T3
M950 H4 C"!exp.heater4" T4
If I ask for the Statuts with M308 S1I get correct values:
M308 S1
Sensor 1 type Thermistor using pin e0temp, reading 22.1, last error: success, T:100000.0 B:4725.0 C:7.06e-8 R:4700.0 L:0 H:0
Is there any solution to fix thermistor on Duet 2 Wifi?

since this commit :

commit

the temp sensors on duet 2 wifi are broken. The sensors on the duex5 are still working

dc42

@smoki3 said in RepRapFirmware 3.0 first official beta is out:

@Marco-Bona said in RepRapFirmware 3.0 first official beta is out:

With this build I encounter problems with heater mapping. The values found are -273 with the exception of the heated chamber which is correct.

; 9 _ HEATERS

M308 S0 P"bed_temp" Y"thermistor" A"Bed thermistor" T100000 B3950
M308 S1 P"spi.cs1" Y"rtd-max31865" P"spi.cs1" A"RTD1"
M308 S2 P"spi.cs2" Y"rtd-max31865" A"RTD2"
M308 S3 P"e2_temp" Y"thermistor" A"Chamber thermistor" T100000 B4725 C7.06e-8

M950 H0 C"bed_heat" T0
M950 H1 C"e0_heat" T1
M950 H2 C"e1_heat" T2
M950 H3 C"duex.e2heat" T3

@smoki3 said in RepRapFirmware 3.0 first official beta is out:
I have problems with the thermistors on this build on my Duet2Wifi. T0,T1 and Bed shows -273 °C. The thermistors on the duex5 are fine. They are defines as:
; Thermal Sensors
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 R4700                    	; Set thermistor + ADC parameters for heater 0
M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 1
M308 S2 P"e1_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 2
M308 S3 P"e2_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 3
M308 S4 P"e3_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 4

; Hardware
M950 H0 C"bed_heat" T0
M950 H1 C"e0_heat" T1
M950 H2 C"e1_heat" T2
M950 H3 C"!exp.heater3" T3
M950 H4 C"!exp.heater4" T4
If I ask for the Statuts with M308 S1I get correct values:
M308 S1
Sensor 1 type Thermistor using pin e0temp, reading 22.1, last error: success, T:100000.0 B:4725.0 C:7.06e-8 R:4700.0 L:0 H:0
Is there any solution to fix thermistor on Duet 2 Wifi?

Strange, it's working on my Duet WiFi-powered delta. The hot end uses a PT100 but the bed uses a thermistor.

If you run M98 Pconfig.g do you get any error messages?

smoki3

@dc42 Just warnings for overpowered heaters.

I compiled a build before the mentioned commit. There everything workings as it should. starting with this commit it's broken.
Oddly all my duex5 thermistors are working.

EDIT:
I get this on the new build:
@dc42

Error: M307: Heater 1 not found
Error: M307: Heater 2 not found
Warning: M307: heater 3 appears to be over-powered. If left on at full power, its temperature is predicted to reach 741C.

Warning: M307: heater 4 appears to be over-powered. If left on at full power, its temperature is predicted to reach 592C.

dc42

I've just remembered, someone else reported a bug whereby if you get an over-powered message warning then it fails to set the heater model. I thought I fixed this before the beta 10 release not after, but I could be wrong.

smoki3

@dc42 I found the issue:

I have to declare the heaters with

M950 H0 C"bedheat" T0

instead off

M950 H0 C"bed_heat" T0

But according to documentation both should work