Posts made by vandermeulen

@engikeneer Okay, I hadn't found the M143 command. Let me try.

@stephen6309 But that's an impossible user interface design. Just cannot be in a commercial product.

@zapta Is this really the case? In the config file you set the extruder temperature limit to eg. 250°C, but then the user is allowed to use 250°C? Is it even possible to set limits in a slicer below the values allowed by the printer?

@t3p3tony The issue is that the user can set the bed to the maximum and then receive an error. Maybe until now nobody has gotten into this situation and I'm just experiencing it during testing.
It feels strange not allowing the maximum temperature. In a car you run against the rev limiter, but the engine doesn't require a restart.

@t3p3tony This is hardly a solution for a printer I professionally sell. And how can it be different from the previous three? I don't get it and want to know what is going on.
Maybe this all sounds a bit grumpy but after hours fiddling and customer pressure I'm not happy.

@t3p3tony The limit in the config is set to 90. Setting the temperature to 89 works fine. Only when the setting is identical to the limit, the fault occurs. Heater is strong enough, rises 60 degrees in a few minutes, and the curve is smooth. I've replaced the sensor and cabling, no change. Playing with the safety limits with the M570 command didn't seem to change behavior, not did it help.

@t3p3tony Ah of course. The "...x.x°C/s" type is displayed.
And I have made and sold three identical printers, where the problem never occurred. The same settings and config's. Only difference is maybe that we updated this last printer to firmware 2.05.1.

Sorry to bother with this topic again, but after days of testing I still keep getting heater errors when touching the limit of 90°C.

Heating up goes perfectly in a straight line to the max.. Any value below 90°C and the control works. Only at the max. the heater fault is called.

Changed the sensor and cable, ran autotune, checked previous versions that worked, but no progress.

The 1.800W bed is switched with a solid state relais.

Firmware is 2.05.1 (no time to change to 3.3)

Desperately trying to get the 16-bit program bmp2c-escher3d.exe to run on my 64-bit Windows, without luck so far.

Can someone compile it for me? Or is there a 32-bit version of the bmp2c-escher3d.exe program?

@dc42 The graph is very helpfull, but for longer prints I cannot babysit the printer.
For now I will try if better ground between power supply and heater block will improve the situation. And I will bypass / solder the E3D Molex connector, to eliminate a failure point.

Hmmm, seems it's not so easy after all. Had another failure today.
Wondering if there is a debugging method, like logging temperature.

@dc42

After your message I went to look again for all possible electrical interruptions, and found the sensor wire or the E3D connector to be faulty. Probably it just had too much of a beating from assembling it many times.

Capacitors removed. All set. Thanks again!

Michiel

@dc42 said in heater fault troubles:

VSSA

Thanks David, I will review your mail and test asap.

I can't get a grip on heater faults.

SITUATION DESCRIPTION
We have two printers, each with two extruders, some V6, some Volcano's.
Standard thermistors from E3D, connected with the E3D Molex connector.
Separate shielded extruder motor wires.
1,5m long, 0,25mm^2 wire to the sensors.
Duet3D board and PanelDue interface. No extension boards.
Heated bed via solid state relay.
Quality power supply.
Months of testing behind us. Read every page on the Duet website concerning heater faults.

ERROR DESCRIPTION
Sometimes getting errors, sometimes not. Prints during three days can go perfectly, and the next job having a heater fault after minutes, or after an hour. With or without print fans makes no difference.
Temperature graph is flat, but suddenly can have a dip, not related to anything like print fans or other influences.

MEASURES
Autotuned extruders with / without print fans.
Socks on the heater blocks.
Checked voltages, cable resitance.
Checked and changed connectors thoroughly.
Printing without fans.
Installed 40W heaters (instead of 30W).
Direct cable from sensor to DUET board.
Earthed the extruder with a separate wire.
Added 10nF filter capacitors on the sensor inputs.

NEXT STEPS
Even though we've got errors on at least 3 extruders, I think we need to replace the thermistors again.
Change the Duet boards?
Switch to pt100's?
I'm really stuck now...

The pin fan speed was new to me, but it's perfectly ok. Maybe in the future make the option available on the Panel Due, but consider it problem solved.for now.

Fan speed can be changed when printing, but as soon as the print G-code sets a fan speed, the change is undone. Is there an option to let the manual override become leading?

Our printer has a coreXY movement system with a special type of IDEX system. The Z-endstop is at Z-max. Our bed does not need leveling, but of course we need to be able to set the Z=0. Right now we are just changing the Z-axis limit in the config file with M208. But a nozzle or hot-end change would require this to be done by the customer, what we don't want.

We would like to create a macro that does the following:

• Home all axis.
• Move the bed up to Z=5mm.
• On the PanelDue move the bed up to touch the nozzle (or a caliber with a know thickness).
• Store the actual Z-axis limit or an offset by pressing a button on the PanelDue.

Steps 1 to 3 are straightforward, but is there a way to program step 4?

How do you, in case there is a bed probe, adjust the height difference between nozzle and probe? We couldn't find this in the G30..G32 description.

We are a new 3D-printer manufacturer using DuetWifi and PanelDue. We would like to limit the access to firmware files, to prevent customers creating problems by making incorrect changes.

Is this possible?