RepRapFirmware 3.0 first official beta is out

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

dc42

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

@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

Thanks, I found the problem in the source code. Will be fixed in next commit.

PS - the same bug was present when using M950 to declare a fan.

tdybare69

@dc42 I AM USING 2.03

A Former User

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

@dc42 I AM USING 2.03

You did read the title of this thread before posting right?

tdybare69

@CaLviNx YOU MUST HAVE MISSED THE PART OF I AM NEW TO ALL THIS.

T3P3Tony

@tdybare69 please open a new thread to discuss your issue.

A Former User

@tdybare69

Well to be brutally honest if you don't even have the cognitive power to read the title of a thread, you are in for a long hard road trying to get a Duet to work.

Also little bit of advice on Internet etiquette. Capital letters are considered "shouting" there is no need for it.

And as has been said please open a thread where you can can request assistance for the particular issue that you are encountering.

Someone "might" be willing to take on the monumental task of trying to help you.

kraegar

I've had multiple days of completed prints, thought I was out of the woods, but then had another stop and report it's 100% only part way through the file. Checked the file's gcode, and it did upload all 100mm of the print, but it stopped at 41.6mm. No error or heater fault reported, both heaters shut off when it stopped.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 v0.5 version 3.0beta10 running on Duet 3 prototype v0.5
Board ID: 08DGM-9T66A-G63SJ-6J1FJ-3SD6M-KS0BA
Used output buffers: 1 of 32 (6 max)
=== RTOS ===
Static ram: 67696
Dynamic ram: 133764 of which 60 recycled
Exception stack ram used: 592
Never used ram: 191104
Tasks: NETWORK(ready,2044) HEAT(blocked,1208) CanReceiv(suspended,3804) CanSender(suspended,1496) CanClock(blocked,1432) TMC(blocked,456) MAIN(running,2060) IDLE(ready,196)
Owned mutexes:
=== Platform ===
Last reset 01:05:56 ago, cause: power up
Last software reset at 2019-09-19 17:50, reason: Unknown, spinning module Platform, available RAM 191596 bytes (slot 2)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
MCU temperature: min 44.0, current 57.2, max 57.4
Supply voltage: min 22.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, reads 22271, writes 23 timeouts 0, SG min/max 0/1023
Driver 1: standstill, reads 22273, writes 23 timeouts 0, SG min/max 0/1023
Driver 2: standstill, reads 22270, writes 27 timeouts 0, SG min/max 0/184
Driver 3: standstill, reads 22271, writes 27 timeouts 0, SG min/max 0/1023
Driver 4: standstill, reads 22272, writes 27 timeouts 0, SG min/max 0/178
Driver 5: standstill, reads 22281, writes 19 timeouts 0, SG min/max 0/1000
Date/time: 2019-09-20 14:10:57
Slowest loop: 176.43ms; fastest: 0.19ms
=== Move ===
Hiccups: 94892, FreeDm: 375, MinFreeDm: 297, MaxWait: 177311ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 6, completed moves: 6, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file* is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon* is ready with "M122" in state(s) 0
queue is idle in state(s) 0
lcd is idle in state(s) 0
spi is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 16.40ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

Ethernet -
State: 0
Socket states: 0 0 0 0 0 0 0 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 88ms ago
RX/TX seq numbers: 6056/6056
SPI underruns 0, overruns 0
Number of disconnects: 1
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v1.0.3.3
File:
Pending code: G1 X126.818 Y131.288 E0.04478
Pending code: G1 X126.235 Y131.602 E0.02226
Pending code: G1 X125.637 Y131.893 E0.02236
Pending code: G1 X125.026 Y132.161 E0.02243
Pending code: G1 X124.417 Y132.399 E0.02199
Pending code: G1 X123.431 Y132.722 E0.03487
Pending code: G1 X122.487 Y132.975 E0.03285
Pending code: G1 X121.843 Y133.113 E0.02213
Pending code: G1 X121.189 Y133.225 E0.02230
Pending code: G1 X120.536 Y133.307 E0.02213
Pending code: G1 X119.204 Y133.394 E0.04488
Pending code: G1 X118.802 Y133.387 E0.01352
Pending code: G1 X98.914 Y113.500 E0.94545
Pending code: G1 E-0.56250 F3300.00000
Pending code: G1 F9600
Buffered code: G1 F3793
Buffered code: G1 X115.759 Y101.174 E0.91349
Buffered code: G1 X114.852 Y101.362 E0.03114
Buffered code: G1 X114.289 Y101.516 E0.01964
Buffered code: G1 X113.138 Y101.895 E0.04072
Buffered code: G1 X112.018 Y102.359 E0.04074
Buffered code: G1 X111.501 Y102.608 E0.01929
Buffered code: G1 X110.442 Y103.191 E0.04066
Buffered code: G1 X109.428 Y103.848 E0.04062
Buffered code: G1 X108.961 Y104.191 E0.01946
Buffered code: G1 X108.029 Y104.957 E0.04056
Buffered code: G1 X107.601 Y105.350 E0.01955
Buffered code: G1 X106.745 Y106.225 E0.04114
Buffered code: G1 X106.503 Y106.503 E0.01238
Buffered code: G1 X129.437 Y129.437 E1.09030
Buffered code: G1 X128.490 Y130.200 E0.04089
Buffered code: G1 X127.949 Y130.584 E0.02231
=> 732 bytes
Code buffer space: 2048
Configured SPI speed: 1000000 Hz
Full transfers per second: 312.28
Processing print job /opt/dsf/sd/gcodes/joel-new-and-improved-without-additional-stuff-in-his-head2_0.16mm_PLA__2h14m.gcode

tdybare69

@CaLviNx caps were on due to working in gcodes with web control. its not that i dont have the inteligance, i just work all day, outside in the heat. am tired at the end of the day, no need to be rude.

A Former User

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

@CaLviNx caps were on due to working in gcodes with web control. its not that i dont have the inteligance, i just work all day, outside in the heat. am tired at the end of the day, no need to be rude.

The word is intelligence, and trust me, for me I was being extremely nice.

T3P3Tony

@kraegar please try DSF 1.0.3.5 when you get a chance.

kraegar

This post is deleted!

kraegar

Updated, then had the thought to check M122. Once again it's showing I'm running 1.0.3.3 even though the pi reflects 1.0.3.5.

apt list 2>/dev/null | grep duet | awk -F'[/ ]' '{print $1" "$3 }'
duetcontrolserver 1.0.3.5
duetruntime 1.0.3.5
duetsd 1.0.2
duetsoftwareframework 1.0.3.5
duettools 1.0.3.5
duetwebcontrol 2.0.0-4
duetwebserver 1.1.0.0

=== Duet Control Server ===
Duet Control Server v1.0.3.3
Code buffer space: 2048
Configured SPI speed: 1000000 Hz
Full transfers per second: 220.03

I'll force the full update.

T3P3Tony

@kraegar stupid question but you are stopping the service and then restarting it?

kraegar

I did not stop the service manually when I updated. If that's in the instructions I apologize, I winged it since I recall you'd said you were adding stopping the services to the apt scripts.

kraegar

For clarification, I'm doing an sudo apt-get update; sudo apt get upgrade

Perhaps something odd is happening that's preventing it from upgrading for me?

kraegar

Just checked, doesn't look like that's in the instructions, so I didn't skip it

I can provide more info on my pi, but literally the only thing I've installed has been the duet software. I've left it completely "stock" other than that. It's a pi4 running the "lite" install of Buster.