Topics created by Iamturbo1978

@alex-cr That was the problem... Thank you

@garyd9 See... I knew I was missing something.

Thank you so much, that is what I was missing, and it totally worked.

would it be better to go back to FW 2.05? from the mecatronic switch to duet I have not yet printed anything, I'm curious to see how it works

@Phaedrux this is great information. Thank you.

I Made a Post about this ! With Pictures and a method to desolder without hotair

@Phaedrux said in Cant change from V3.0 to V2.05. Missing file:

@dc42 Will RRF3 releases include the single zip file option like recent RRF2 releases do?

Yes.

@Danal said in Delta printer advice:

That's the main reason I chose to do this. 600mm borosilicate and 600mm aluminum are not cheap. In fact, 600mm borosilicate is extremely hard to find. My tabletop was ordered from Amazon for about $40 USD. Very replaceable.

You don't need borosilicate. Ordinary float glass is fine if it is on top of a heat spreader (some people even use it directly on top of a PCB bed heater).

I think a good approach would be to devide 3D printing into it's tasks and decide which hard- and software shall fulfill it:

Overall plan with one or multiple printers is not time critical and can be done in advance, but is complex => high power CPU, no realtime necessary.

Stepper movements: must be exact and is time cirtical, realtime OS needed => near hardware, realtime OS like the Duet 3 core.

Heater, Fan, Heatbed Calibration etc. not time ciritical => delegate to low power MCU, but with high priority interrrupt power to stop printing in case of emergency.

Quality assurance with camera, measure dimensions (e.g. control every layer quality) => good image processing hardware like Raspberry and maybe some GPU for neuronal network for image classification.

GUI for user interaction and visual control need to be able to manage html 5 => powerful enough hardware running a web server, like the Raspberry or a Tablet/PC/....

I would then assemble the hardware (modulize) by good interfaces. The Firmware on the different components need not to be the same language/OS, only the protocols of the interfaces. There needs to be a central realtime clock.
I would not use an integrated hardware, because I loose flexibility. Using a good interface is IMHO better.

@dc42 that would be awsome, I am guessing that the encoder will be used primarily for position/movement verification.
I have a stepper driver that supports the use of an encoder for position verification and commutating the stepper motor as high pole count bldc to run a control loop on the curent of being applied to maintain rotor position. It can help quite the stepper down versus the standard noisier position verification mode but I don't think there is much to be gained over the existing silent nature of the trinamic drivers using that approach. One advantage it does provide is the ability to momentarily over drive the motor to overcome a high torque demand that would normally cause a stepped to miss a step.

All in all really exciting news

@dc42 that is only what I was suggesting. Thank you for the work you do.

@nhof cool.. thank you

@supraguy said in Prusa style display:

Doesn't work.

The 20 X 04 (They're 20 columns, not 16) controllers are not supported on any Duets so far as I know. It's a pity, because I have 4 of the things.

After I made my post I remembered that they are 20*4 display.

The 12864 full graphic controllers are supported (more or less) on the Maestro, but not on the Duet Ethernet/Wifi.

There has been some talk from some people on making a hardware interface that would allow you to plug in the other controllers, kind of like the board that let you plug it into the original RAMPS boards, but the 2004 controller apparently has the highest demands in terms of I/O pins. It's probably easier to get the SD card slot working than the display itself.

For the basic parallel dot matrix display (like the 20*4) it can interface with a 3.3v system. The displays are TTL logic, so no "drivers" or "level translators" are needed. A 120 ohm to 240 ohm (depending on various things like io diode current) resister in series with the data bus would be the only thing needed to protect the Duet Incase there is a bus conflict. I've done it many times before, using a 3.3v microprocessor to control a standard dot matrix display.

I have been looking at hacking together a solution where I just use an 8-bit Arduino to talk to the Duet and run the controller, because I have a pile of Arduino Mega 2560 boards and RAMPS 1.4 boards, with a couple of the interface boards to the 2004 controller, but I haven't got very far.

That would be an interesting idea.

I will have to figure out how to do the programming to get one to work.

@3mm If you want to try it out, I would be willing to give you a heatsink to do the proper thermal investigation. I have 2 more heatsinks, since they come in a 3 pack.

I Just added M703 into the start gcode of my slicer. Now it works. Thank you.

Best richtige
Cai

@iamturbo1978 If you wanted to add 0.15mm to your z height you could add that to the 0.425 in your custom G31.

Alternatively you could try adding a baby stepping command M290 S0.15

@dc42 thank you so much for the information. Now I will have to re-tune my extruder.

After a couple hours of trying to tune PA, I noticed my speed dropped a lot. I'm requesting 60mm/s but I could only get 35mm/s. So I bumped up my jerk from 10mm to 30mm. That worked a little, but I started to skip steps. So I changed my stepper motor from a 0.9 deg 1.2A, to a 1.8 deg 2.0A motor. I have not calibrated the steps yet, and the print is looking a little better.

I did notice something that I need a little better understanding on. With my PA set to 1.5, my extruder pulls the filament back slowly, even though I have the settings through the roof. The extruder can move filament (no hotend, just PTFE tube) at 120mm/s, and during printing, the extruder doesn't look like it is getting close to its limit. is there something I am missing? I am using a true E3D titan extruder, are the settings for the extruder what the filament sees, or what the motor sees? should my extruder values be 3x the standard value (3:1 gearing)?

Here are my current stable settings. I still have to fine tune the extruder settings, they could go up;

M350 X16 Y16 Z16 E16 I1 S2
M92 X80 Y80 Z640 E418.599302 <-- still have to work on steps per mm
M566 X1800 Y1800 Z120 E1400
M203 X24000 Y24000 Z900 E9600 <-- printer can travel at 400mm/s
M201 X3000 Y3000 Z75 E3000
M204 P500 T3000
M906 X1600 Y1600 Z1300 E1500 I20
M84 S30