RepRapFirmware 3.01-RC1 released

spllg

unsure if this is related to 3.01-rc1but i feel, it might:

tried to configure my ed3 v6 as

M308 S1 P"temp1" Y"thermistor" B4725 C7.06e-8

which resulted in a displayed temperature of -273.1C.

M308 S1 P"temp1" Y"thermistor"

seems to result in a temperature reading which is ~20C too high around 200C - at least i'm unable to print pla at temperature < 215 because it would not flow.

what should i do?

dc42

@spllg said in RepRapFirmware 3.01-RC1 released:

unsure if this is related to 3.01-rc1but i feel, it might:

tried to configure my ed3 v6 as

M308 S1 P"temp1" Y"thermistor" B4725 C7.06e-8

which resulted in a displayed temperature of -273.1C.

M308 S1 P"temp1" Y"thermistor"

seems to result in a temperature reading which is ~20C too high around 200C - at least i'm unable to print pla at temperature < 215 because it would not flow.

what should i do?

After sending that first command, send M308 S1 to see whether it reports the correct parameters.

dc42

@SpoonUnit said in RepRapFirmware 3.01-RC1 released:

Any thoughts on the chamber issue? Can I just allocate any random pin to the heater or will there be a check on whether it can actually perform as a heater?

I can't remember whether you can use any pin or it has to be PWM-capable. But your alternative is to use conditional GCode. Don't create a dummy heater, just a sensor. Then loop until the sensor temperature is high enough, e.g. within 5C of the temperature you have set for the bed heater (if your sensors agree that closely).

Sotidii

Items "t" do not work.

SpoonUnit

@dc42 said in RepRapFirmware 3.01-RC1 released:

But your alternative is to use conditional GCode.

OK. Definitely interested in trying that, though the benefit of the chamber definition is lost (i.e. I can see the sensor temp displayed clearly in DWC - but maybe there's another way to add the sensor to the UI?).

Here's what I tried:

echo "starting"
while true
	if heat.sensors[6].lastReading < 30
		echo heat.sensors[6].lastReading
		break
echo "bed temp reached"

I tried this as a macro and a gcode file, and neither work. In fact, I think adding the additional echo within the if body and then running the job caused DWC to go into an infinite-reboot-loop. If this isn't the right way to test code, is there an alternative?

I realise the logic is upside down by the way. I've been flipping the >/< while testing.

Just to confirm this is the right sensor to test:
alt text

dc42

I think what's happening is that the loop is taking up all the processor time. I'll fix this in RC2. Meanwhile, try putting a 1 second delay (G4 P1000 command) in the loop body.

jay_s_uk

Is there an update for the expansion board as well?

dc42

@jay_s_uk said in RepRapFirmware 3.01-RC1 released:

Is there an update for the expansion board as well?

Try the one at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0. You might need to use the copy of RRF there too.

SpoonUnit

@dc42 said in RepRapFirmware 3.01-RC1 released:

try putting a 1 second delay

Yep. Sorted. Thanks!. I did wonder whether it was just going to get stuck that way. So, the second pause does fix it, and perhaps that's sensible anyway. You're in control about how much to wait between cycles. I guess if you're going to fix it at some value, that value could be set by another GCODE before entering the loop perhaps.

The short piece of code does generate an interesting result on the progress bar

SpoonUnit

Actually, now I'm a bit confused ...

This was where I (stupidly) put the pause ...

while true
	if heat.sensors[6].lastReading > 30
		G4 P1000
		break

But it worked anyway (?), so it paused even without the sensor having the right value.

Also PrusaSlicer isn't terribly excited about the GCODE ..

!!!!! Failed to process the custom G-code template start_gcode
Parsing error at line 18.
if heat.sensors[6].lastReading > 65

SpoonUnit

It seems Slic3r uses [] to denote variables, so if they're found, it immediately tried to process and then fails. I wonder if an alternate form can be made available along the lines of:

heat.sensors.6.lastReading

This then doesn't trip the error. For now I can post process to just put the [] back in.

A Former User

@SpoonUnit said in RepRapFirmware 3.01-RC1 released:

Also PrusaSlicer isn't terribly excited about the GCODE ..

why not use the macros provided by RRF to do start/stop stuff?

spllg

@dc42
send M308 S1 P"temp1" Y"thermistor" B4725 C7.06E-8
send M308 S1

response is

Sensor 1 type Thermistor using pin temp1, reading -273.1, last error: sensor open circuit, T:100000.0 B:4725.0 C:7.06e+0 R:2200.0 L:0 H:0

and the tool fan starts spinning - it should start @50C

dc42

@spllg said in RepRapFirmware 3.01-RC1 released:

@dc42
send M308 S1 P"temp1" Y"thermistor" B4725 C7.06E-8
send M308 S1

response is

Sensor 1 type Thermistor using pin temp1, reading -273.1, last error: sensor open circuit, T:100000.0 B:4725.0 C:7.06e+0 R:2200.0 L:0 H:0

and the tool fan starts spinning - it should start @50C

There's your answer, the firmware can't detect the thermistor. Maybe a bad crimp connection?

spllg

@dc42

send M308 S1 P"temp1" Y"thermistor" B4725
send M308 S1

results in

Sensor 1 type Thermistor using pin temp1, reading 20.6, last error: success, T:100000.0 B:4725.0 C:0.00e+0 R:2200.0 L:0 H:0

no, i did not change anything except leaving out C7.06E-8 in the first m308 - did not even touch the printer.

SpoonUnit

@bearer It's a good idea. I can write a few different macros for the few variations I would typically have for startup. Thanks for the suggestion.

A Former User

@SpoonUnit if you need variety you could still control it from the slicer and have M98 execute the file of your choosing. (not sure if parameters are implemented yet, but think it on the to-do list)

SpoonUnit

@bearer Yep. That's exactly what I was thinking once you suggested using macros. I already store retraction settings in retraction.g, so this is just an extension of that type of thinking.

SpoonUnit

@bearer said in RepRapFirmware 3.01-RC1 released:

not sure if parameters are implemented

Oh, you mean parameters for running a macro!. That would be nifty.

spllg

@dc42 connected the thermistor to temp2 - same result.

further info:

M308 S2 P"temp2" Y"thermistor" B4725 C.000001

results in

M308 S2

returning

Sensor 2 type Thermistor using pin temp2, reading 12.8, last error: success, T:100000.0 B:4725.0 C:10.00e-7 R:2200.0 L:0 H:0

the same holds true if the thermistor is connected to temp1.