M500 Always Fails
-
It's also super comforting to know that I'M NOT DOING ANYTHING WRONG and there's nothing wrong with my setup that'll bite me later. That was my main concern.
-
@GoremanX said in M500 Always Fails:
I don't want to spend more money on an ethernet bridge
you can use the pi for that
-
@GoremanX said in M500 Always Fails:
@bearer Thank you!
That would've been nice to know right off the bat. Especially since none of the guides take it into account. Seems like I could've saved a whole lot of head-banging if that had been cleared up immediately.
Sorry about that. I should have clued into checking the unsupported list first. I hope the road to feature complete isn't much longer.
-
@GoremanX Thanks for the report, I could confirm this is a bug in DSF. It will be fixed in the next software version.
The reason it is happening is because you have configured heaters with gaps (i.e. for example heater 0, 1, 3, 5). You can work-around this problem by configuring the heaters sequentially.
-
@chrishamm Thank you for that clarification. I configured the heaters in the order that seemed logical to me to keep them organized compared with sensors and tools. I tried re-organizing the config file so that sensors and heaters are in numerical order (1,2,3), but it didn't seem to have fixed the issue.
I skipped heater 0 since I'm using an AC bed heater and the SSR doesn't need vast quantities of current so it's being powered by heater 2 instead, which simplifies wiring. But I did have a sensor 0 configured as a general purpose sensor that was purely informational. So I went ahead and created a heater 0 (that won't do anything) and assigned it to sensor 0, and now M500 works as expected.
-
@GoremanX said in M500 Always Fails:
I skipped heater 0 since I'm using an AC bed heater and the SSR doesn't need vast quantities of current so it's being powered by heater 2 instead,
Heater 0 doesn't need to be Out0. I have AC bed heater on an SSR on Out1, but it's heater 0 (and I don't have any problem with M500).
M308 S0 P"spi.cs1" Y"rtd-max31865" ; configure sensor 0 as PT100 via CS pin spi.cs1 M950 H0 C"out1" Q5 T0 ; create bed heater output on out1 and map it to sensor 0 M307 H0 A500 C1500 D12 S1 V0 B0 ; configure bed heater (since mains heater supply voltage is not relevant) M140 H0 ; map heated bed to heater 0 M143 H0 S150 ; set temperature limit for heater 0 to 150C -
@achrn That's all well and good, but it seems unnecessarily confusing. What I did isn't technically wrong, it just happened to run afoul of a bug. I like being able to reference heater, output and sensor by the same number to avoid any potential mistakes in the future when I haven't looked at the file in months and suddenly need to make changes, especially when using these boards on many different types of printers that have completely different physical configurations
