okay I was ready to swap the wifi module but before that I tried to just "extend" the antenna... believe it or not it worked. I hadn't a single disconnect since

Basically cut the onboard antenna and soldered a new one. The antenna must be of a very specific length (check 2.4 antenna length) but apart from that it's a 5 minutes hack.

Now, I don't suggest to anyone doing that... but it worked for me.

I have 2 part fans connected together and 1 thermally controlled tool fan, they are all 12v connected to the duex5. I'm in a corexy setup and thinking of reducing the number of wires that go from the head to the duetwifi/duex5.

It is my understanding that the positive lead is shared with all fans. My idea was to use just 1 pos and 2 negs. On the duet side I'm connecting the 2 part fans together to one header (+ and -) and the tool fan to another header (just the negative since the positive is shared on the other header). Does it make sense? Does that impact on the total max amperage? Just wanted to check this config with you before burning my duet Thanks!

PS: I wanted to add that both this forum and the wiki are an incredible source of knowledge, I was able to go from zero to full functioning corexy by just RTFM so thanks guys!

okay so I'm not a complete idiot, it is indeed a bug

@droftarts thanks for checking, can you try to set M109 == M143 ?

I'll try to update to 2.05 or 3 at this point

I didn't remember I actually set M143, it was an initial configuration and it was set to a very conservative value. I've set it to 290C now.

@droftarts said in Erratic M109:

Not sure why you didn't get a warning message. I'll test tomorrow.

you get a warning but so generic that it was of little use to me. Also the docs put me off a little.

@dc42 it's a warning regarding a faulty thermistor, it would be nice that if the maxtemp is reached the duet would just say so

okay... I'm a bit ashamed but in my defense the docs are not completely clear

the wiki for M143 says "S Maximum permitted temperature". Apparently the maximum permitted temperature is actually what you define in the S parameter minus 1 (I guess you should give it a good +5 margin anyway).

If you set the temp (with 109) to the max temperature the duet just ignores the command but keeps executing the following gcode. Shouldn't the machine just stop or maybe give an error that tells you we reached a soft temperature limit?

It took me more time than I'd like to admit... my bad... I'll see myself out... sowwy.

@droftarts

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.04 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2019-11-01b1

apparently it's not the latest but close enough

if I set M109 manually it seems to be working... I'm pretty confused... I swear it was working before.

@droftarts said in Erratic M109:

Watch what happens to the tool in DWC when you run the start gcode. What happens if you insert T0 after G32, but before M109 S260?

I tried with T0 after G32 but didn't work. From web interface I can see temp and standby temp set to 130C but not to 260C. When it reaches the second layer the temps are updated.

I'm on duetwifi latest 2.x firmware. I have a very weird temperature issue. I initially set the tool temp to 130C, then probe and finally set the temp to the final temp for printing.

Something like this

M140 S85 ; bed temperature
M109 S130 ; set tool temp and wait. 130°C to prevent ooze and damage to the print bed while probing
M190 S85 ; wait for bed temperature

G28 ; home all axes
G32 ; true bed leveling

M109 S260 ; set initial tool temp and wait

what is happening is that the temp is correctly set to 130C, but the second M109 is completely ignored and the print starts with a warning in the console. As soon as it reaches the second layer where I have a third M109 (I'm lowering the temp at second layer) the temp is correctly set to the new temp.

I'm a little confused... I use a mosquito with a Slice heater and slice thermistor. Any idea? I noticed just now that M109 is deprecated on RRF but I guess internally it converts it to the appropriate commands.

@Danal they are indeed smaller than I thought!

I got used to crimping, that wouldn't be a big issue. Still not sure if I want to go with a more polished solution (like the one posted by @littlehobbyshop ).

I've also found connectors with dedicated pins for power, but let's not go overboard

thanks for your report btw!

@littlehobbyshop that is very close that what I was planning to do, with less fancy PCB and more DIY The cable is from a local supplier but I believe they can be easily found. They are sold as "security/alarm cables" they come in many variants.

@zapta at the moment I'm only sharing the positive leads of the fans, that's all I need but I'll check what else I could share. thanks!