hmm, i guess this is a stupid question, but I am unclear
- where to put these lovely scripts to load the file.
hmm, i guess this is a stupid question, but I am unclear
Yup, using only 120, increased it to 220, all is well, thanks
yes it is
the temperature shows up on the DWC associated with tool 0,
here is the code in the config file
M563 P0 D0 H1 F0 F1 ; tool 0 uses extruder drive 0 and heater 1
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
one more thing the unload will work but the load will not without the error about temperature
What about controlling part cooling fans?
Here is my printer - (with failing paneldue)
I have the config file more or less under control for the duet. I is the firmware file for simply3d. *.frm. There is an export/import option in S3d firmware configuration. (located under tools).
I have a 400x400x600 unfortunately all of my axis designs are a little different from any build out there. Looking at it, it looks like a corexy D bot build. However the x & y use a "zipper" belt drive. This is where 2 belts face each other in a raceway to provide rack and pinion type of control, only with belts. It is very fast and accurate over long distances and avoids, long complicated belts.
The z drive uses 3 12mm threaded rods driven by one motor to move and the plate is held on a frame that provides rigidity by 4 sets of wheels that run inside the post of the open builds v-slot frame. The open builds frame has panels attached to the outside to form an enclosure, with thermostatically controlled fans.
I am using E3d V6 hot end with bowden Bondtech QR extruder. One head at the moment, though I have a dual print head carriage. I have a part cooling fan also.
The error message says that the hot end is not hot enough. But according the web control panel, it is hot enough. What g-code could be confusing the extruder?
I am just trying to get started printing but I am lost in the weeds a bit, on the gillion setting and macros. Does anyone have firmware configuration file for the duet that is already tuned up that they would be willing to export for me, so I can import it.
thanks
I am not clear about the need for macros, for things like part cooling etc.
Also I forgot to mention be sure your motors are correctly wired, incorrect wiring will have the same symptoms as broken wires.
We had this issue, basically is one of these...
Don't forget to power everything off while plugging and unplugging!
Its the motor itself. - take the load off and see if the behavior continues, swap another motor to see if its the motor.
Its a break in the wire, probably direction. Use a continuity checker to confirm no breaks in the wires
its the driver, Hook the same motor wire to another axis and test. -- don't forget to change all the power and speed settings for the test axis.
In our case, we had one motor that was just plain bad, hard to imagine, but i guess occasionally it happens. We also had one case of a broken/loose wire.
I have a large 400x400 aluminum plate bed with a silicone heater run from an SSR.
I have autotuned my hotend, but my bed heater will not get above 80C. Then it stalls. It gets hot pretty fast but as it approaches 60 is slows down.
Here is the code from my config file
; Bed Heater H0
M301 H0 S1.00 P32 I0.1 D93 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 X150 ; Configure thermocouple for heater 0 - Bed heater
M143 H0 S140 ; Set temperature limit for heater 0 to 140C
I commented out the override from the overide config file.
; This is a system-generated file - do not edit
; Heater model parameters
; M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
; M301 H0 P10.0 I0.000 D200.0
M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M301 H2 P-1.0 I0.482 D51.4
M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0
Any ideas
The hot end heater will turn on when an auto tuning via g-code is issued. So I know my sensor and heater wiring all works okay. However it will not turn on when i put a number in the active window for the heater, regardless of what number I enter. The heater remains off.
Here is the code from my config file
; Hot End Heater H1
M301 H1 S0.7 P32.1 I1.036 D93 T0.4 W180 B30 ; Use PID
M305 P1 X202 ; Configure PT100 for heater 1 - 2nd daughter board 1st connector
M143 H1 S280 ; Set temperature limit for heater 0 to 280C
Here the result of the autotune
Heater 1 model: gain 312.5, time constant 232.7, dead time 4.1, max PWM 0.70, calibration voltage 23.9, mode PID, inverted no, frequency default
Computed PID parameters for setpoint change: P32.1, I1.036, D93.0
Computed PID parameters for load change: P32
Just in case here is the other config file updated by the M500 command.
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
M301 H0 P10.0 I0.000 D200.0
M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M301 H2 P-1.0 I0.482 D51.4
M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0
Any thoughts?
yep, that fixed it, guess I misread the page, thanks
I have 2 daughter boards, a thermocouple type K board as my 1st board and a PT100 board a thermocouple type k board. I can not get a reading from the PT100, just the 2000.
It is a 2 wire connections in pins 2&3, with the jumper between pins 2&3 in the right most positon, (middle pins). Here is the config file settings
; Hot End Heater H1
M301 H1 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P1 X202 ; Configure PT100 for heater 1 - 2nd daughter board 1st connector
M143 H1 S120 ; Set temperature limit for heater 1 to 120C
This is what we mean by "in combination".
The issue is the P? designation on thermocouples. Is it necessary? Or only ignored and only the X modifier is utilized? In your example above, you used P1. We could not issue a combination of commands which resulted in displays for 1 thermistor and 2 thermocouples in the Web Control interface.
So if P1 is a thermistor plugged into thermistor1 (E0) on the duet board and we are using 2 thermocouples on the daughterboard, which P designation do we use for the thermocouples? Do we start over with P1 (M305 P1 X150), go back to P0 (M305 P0 X150), or continue to P2 (M305 P2 X150)?
I also need to know:
What does a steady fault light mean vs. a slowly blinking fault light on thermocouple daughterboard?
Should I put this question on a different board on the forum?
I have read the wiki pages and have seen no indication about how the various sensors are to be numbered in combination. I can not find information about the blinking fault light etc. Thermisters and thermocouples are discussed separately but not in combination.
They are plugged in different places, do they use a combined numbering system or a separate sequence for each type of sensor. Ie do both thermisters and thermocouples start at 0? So if I have 1 thermister and 2 thermocouples, do I count up to 3 or do i have one 0 for a thermister and one 0 for a thermocouple.
Temperature sensors and heaters both start at zero. Bed heaters and thermistors are generally 0, with hotends at 1+.
I have tried various combinations but would prefer to work with known parameters to debug.
Thermocouple Daughterboard
What does a steady fault light mean vs. a slowly blinking fault light on thermocouple daughterboard?
Numbering system for heaters
It is unclear how the numbering system works between the vssa thermistor and the thermocouples.
Do the heater numbers start at 0 or 1? If I have one vssa thermistor and 2 thermocouples or 2 vssa thermistors, how should the M305 heater number be written in the config file? Are the Vssa thermistors plugged into E0, heater 0?
VSSA thermistor
The vssa thermistor is not showing up on the Duet Web Control when power is applied. I see 3 heaters briefly on reboot, but that is it.
I assume there is no polarity on these thermistors, is this correct?
The wire supplied with the E3D V6 hot end was not long enough, so we added a short piece which is plugged into the board. Is this a problem with thermistors?
We confirmed continuity on the new extended wire.
So, the bottom line is that the configurator can't configure thermocouples? I have to put lines of code in manually.
Just in case it makes any difference...our board is ethernet.
I was stepping through the configuration. I have made a config.g file. I got stopped at Step 7; both temperature sensors are reading 2000. This is documented as a wiring problem. There aren't that many different ways to connect 2 wires on the daughterboard.
Perhaps, I didn't pick the right options for the reprap firmware generator. How should a thermocouple be treated as opposed to a thermistor? Can you give any tips on this? Or refer me to somewhere this is already discussed?
Thank you,
Yes, we have received the new board and all the LED's are now working. Thank you.