Thanks guys I'll check with Idris he set up the product page. Also, I don't yet have one of the production units myself.
EDIT so just checked against my sample units which are the same sensor but in a 10mm cartridge (production units are 20mmx3mm cartridge) a Precision Piezo PT1000 sensor thermally connected to a type K thermocouple probe at 20.0 degC has a resistance of 1071 Ohms. Product page updated. Good catch.
I tried sending G32 but since my bed.g does not contain discreet points to probe, it does nothing, but I regularly run a G29, save the mesh and then use G28, then G30 as above and print and get very nice first layers each time. I have no extra axes defined, just X, Y and Z and E0.
ohhh!: Can I update the PanelDue firmware from the DWC yet?
No. It will eventually be possible, but only for PanelDue v3 control boards.
Any other advantages to the v3 board over the v1.1?
It's faster, which makes the redrawing a bit snappier
It can be connected to a generation 2 Duet revision 1.01 or later using just a 10-way ribbon cable, which is easier to make than the 4-way cable - but then the cable length is more limited
It has more flash memory and RAM, but we're not making use of that yet, except to allow OEMs to have a custom splash screen.
IMO it's not worth upgrading an older PanelDue at present, but that may eventually change if we find that we can't fit new features into the memory of the older versions.
3C isn't much overshoot and is unlikely to affect the print significantly. But if you want to reduce it, increase the A parameter in the M307 command for that heater a little. Try increasing it about 2%.
Yes, M584 must come before M208 and M574. Otherwise any new axis names created by M584 are ignored in the M208 and M574 commands.
The S2 commands means do a raw motor move. On a Cartesian printer the main effect is to ignore any X or Y axis mapping specified in the definition of the current tool.
Great! 🙂 After positioning the M584 in the right place, above all other definitions, it works.
Had to change the S2 to the S1, as it caused issues now the axes are defined properly. I had the S2 from my original source, who used it. Even though I didn't know what it did, I ended up doing the same, as it didn't work without it. Now I know why!
The stop sign above Home U also went away!
I'll be updating my Blog-post on 2x Z axis and write a new one when doing it using 3 motors 🙂
Fan 1 is the recommended fan for cooling the heatsink, because it defaults to being on at power up. This means that if you decide to update the firmware while the hot end is hot, the heatsink fan will keep running during the firmware update process.
In an attempt to offer assistance, I heated my nozzle and unloaded the filament from my 3 colour Diamond that was fitted on the machine. Then I uploaded my config.g file for the 5 colour version. This I then edited to give the same mixing ratios that you were using. Then I ran a series of tests before re-installing the 3 colour config.g and posting my findings. I guess I spent about an hour in total. So I was rather expecting your response to be appreciative or at least neutral. I wasn't expecting what seems like a rant starting with " I know/knew all that …......"
Then you go on to say "You say "as I mentioned before" a couple of times.. where did you mention these things as if they were supposed to be common knowledge? "
Actually if your read my post properly you see that I used that term only once here........... "Also the numbering is really annoying as it uses 1 to 5 and tools are defined as starting at 0 (so 0 to 4). This really is a pain as I have mentioned before !!!. "
So I was referring to the fact that I have previously mentioned (in other posts) that the numbering system is a pain as it is inconsistent. You later agree with this sentiment so why the rant?
You will understand why I feel disinclined to offer you any further assistance.
Hi Morten, best of luck with this setup.
Let us know if you made any progress.
Subscribed, I'm also interested.
Wahh, found out what was wrong.. AFTER I spend a day rewiring to move all Extruderst to the Duex5 and so had to solder in extensions to the wires etc…
As I had been using the Z driver to drive both motors at first, I had removed the jumpers back in january.. I thought nothing off it as Ramps doesn't populate the pins when not in use... and I hadn't noticed it either... untill I for the 100th time looked over the diagram to check up on drive numbers and noticed the "jumpers" written on the diagram if you only use 1 Z motor.
After I put in the jumpers everything works perfectly.
I am going to write a blogpost about it, but for now:
My Config.g and homez.g is as follows Description:
My XY for CoreXY AB. All 5 extruders on Duex5 and the 2 Z-drivers on Z and Ex0
; Define Drives
; Physical Drive conention
M569 P0 S1 ; Drive 0 A
M569 P1 S0 ; Drive 1 B
M569 P2 S0 ; Left z-motor (original Z)
M569 P3 S0 ; Right z-motor (Ex0)
; M569 P4 S0 ; EX1 - unused
M569 P5 S0 ; Extruder0 - Physical Tool 0
M569 P6 S0 ; Extruder1 - Physical Tool 1
M569 P7 S0 ; Extruder2 - Physical Tool 2
M569 P8 S0 ; Extruder3 - Physical Tool 3
M569 P9 S0 ; Extruder4 - Physical Tool 4
; Motor remapping for dual Z
M584 X0 Y1 Z2:3 U3 E5:6:7:8:9 P3 ; Driver 0 For X, 1 for Y, Z=2:3 U=3, Extruder 5-9 - P3 is number of visible axes XYZ = U is hidden
; Configure Drives
M350 X16 Y16 Z16:16 U16 E16:16:16:16:16 I1 ; Configure microstepping with interpolation
M92 X160 Y160 Z800:800 U800 ; Steps per mm for XY and Z2:3 +U3
M92 E1025:1025:1025:1025:1025 ; Set steps per mm for 5x physical Extruders
M566 X900 Y900 Z12:12 U12 E120:120:120:120:120 ; Maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z1000:1000 U1000 E3000:3000:3000:3000:3000 ; Maximum speeds (mm/min)
M201 X500 Y500 Z250:250 U250 E250:250:250:250:250 ; Accelerations (mm/s^2)
M906 X1000 Y1000 Z800:800 U800 I0 ; Motor currents (mA) and motor idle factor % for XYZ
M906 E1000:1000:1000:1000:1000 I50 ; Motor currents (mA) and ide factor % for Extruder motors
M84 S30 ; Set idle timeout
G91 ; Relative mode
M584 Z2 ; Split Z into 2 (Z+U)
G1 Z250 U250 F2000 S1 ; Move up to 250mm in the +Z direction. Stop if endstop is triggered
G1 Z-3 U-3 F600 S2 ; Move 2mm in the -Z direction - S2 = If containing axis letters: offset will be added to the pause coordinates
G1 Z3 U3 F100 S1 ; Move slowly 5mm in the +Z direction, stopping at the homing switch
M584 Z2:3 ; Join U to Z again - Driver 8+9
G1 Z-5 F3000 ; Move back again 5mm in the -Z direction
G90 ; Back to absolute mode
We used to be able to click a macro-file in the webgui and choose run, edit or delete but not anymore. Now we can only select run it. We can't even delete it from inside the webinterface, but has to put the SD card into a computer.
You can right-click the files. I was confused at first, too, but now I kinda like it…
G10 was originally defined by the NIST GCode standard as "Set coordinate system", meaning set offsets from an origin
Adrian Bower chose to use G10 to set tool offsets from the origin (I presume because it is a similar function) and documented this in the wiki at reprap.org, and also to set tool temperatures
Some other developers (probably Marlin or Repetier devs) ignored that allocation, and chose to use G10 for firmware retraction, which I find completely illogical
Some slicers started supporting G10 to do firmware retraction
Eventually someone documented the alternative use of G10 to do firmware retraction in the reprap.org wiki
In order to support slicers that send G10 to command firmware retraction, RRF supports both uses of G10.
So in RRF, G10 with no parameters means do a retraction, and G10 with any recognised parameters means set tool parameters (i.e. set tool offsets and/or temperatures).
AFAIK, no other firmware has adopted G10 to set tool offsets and temperatures. But no other firmware supports multiple tools anything like as well as RRF does either. Neither does any other firmware provide automatic support for using separate active/standby temperatures for tool heaters.
Heaters in RRF can be in the following states: off, standby, active, fault, and tuning:
Off means what it says. Sending M0 turns all heaters off, except if the print is paused and there is a cancel.g file.
Active means that the heater is heating up to/maintaining the temperature of a tool that uses that heater.
Standby means that the heater is not used by the current tool, but was previously used by a selected tool, so it is maintaining the standby temperature for that tool. This is especially useful in printers with more than one nozzle, because you can keep the inactive nozzle warm ready for printing, but at less than printing temperature to prevent oozing.
On a Diamond hot end you have only one physical nozzle, so I don't think standby temperatures are relevant to you.
In order to print, you need to have a tool selected. Selecting a tool automatically sets its heaters to their active temperatures.
So the recommended sequence for the slicer start gcode is:
1. Start heating the bed using M140 S[bed_temperature].
2. Set tool active temperatures (and standby temps if they are relevant) e.g. for tool 0 use G10 P0 S[first_layer_temperature].
3. If desired, use M116 to wait for the bed to reach temperature. You can swap #2 and #3 if you like.
4. Select the tool e.g. T0
5. M116 to wait for all temperatures
7. To change tool, just send the appropriate T command. No need to mess with temperatures.
8. At the end of the print, use M0 to deselect all tools and turn all heaters off.
Actually it's only necessary to put M82 in the slicer start gcode to use absolute extrusion.
Absolute extrusion is a huge pain in the butt from a firmware development perspective. It bears no direct relation to the amount of movement made by the extruder stepper except in the simple case of a machine with only one extruder drive, the extrusion factor set to 1.0, and no G92 E0 received since starting to extrude. So all the calculations have to be done after converting to relative extrusion anyway. OTOH the firmware code for pause/restore, resume after power fail and filament change procedures all needs to have unnecessary complications added to handle incoming gcode with absolute extruder coordinates.
It looks like Cura will support relative extruder coordinates in the near future, at which point the advice and documentation can be just to set your extruder to use relative extruder coordinates.