Topics created by gbiski

Cnc lathe using Duet as controller

https://forum.duet3d.com/topic/16992/cnc-lathe-using-duet-as-controller

Is the 15W/metre the total if you turn all three colours full on, or is it per colour?

If it's the total then you are OK. If it's per colour then the Duet is OK but you will overload the buck regulator if you turn 2 or 3 colours on simultaneously.

@Grudairian said in IFTTT:

Just a thought, would it be possible to setup the pinouts to fire on an event(print start, etc) and have something like a raspberry pi listen for a pin event? Then when the raspberry pi receives the pin out signal it could trigger an IFTTT event? I would prefer not to have to use a second board to make this work, but I am open to ideas.

Yes, that was the idea. RPi or ESP32 if you want cheaper. ESP32s are now about $4 or $5, even when bought through Amazon, purchased in small (four or five) batches. . If you need help scripting the ESP32, I'd be glad to help.

What firmware version?
What is your probe offset?
What is in your homeall.g?
Have you read this through? https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

@gbiski said in BL Touch not triggering on Duex2:

But when I run the home z procedure or the G30 command I receive the error Z probe already triggered at start of probing move.

Check the white wire.

@gbiski said in Short-to-ground problem:

So you think that most probably it was not the wiring but the current ?

It could have been BOTH. You need to check the motor before connecting it again, as I said above, or you may destroy another stepper driver. My guess is that it has short circuited internally and failed.

Do you think it is correct the following lines having assigned E1 to X (I assigned 600 mA to E0) ?
M584 X4 Y1 Z2:5:6 E0
M671 X0:165:330 Y165:330:165 S0.5
M350 X16 Y16 Z16 E16 I1
M92 X80.00 Y80.00 Z400.00 E830.00
M906 X1150 Y1150 Z1150 E600:1150 I30
M84 S30

You can specify them in any order in M584, so long as the physical motors are connected in the same order. The other motor settings will be applied to the stepper driver as defined. So yes, looks okay, except:

M906 X1150 Y1150 Z1150 E600:1150 I30

Remove one of the E numbers, you only need one, eg M906 X1150 Y1150 Z1150 E600 I30. But you'll need to set the current correctly for whatever stepper motor you connect.

Ian

Guys thanks a lot for your help !!!

Problem of motion solved now it homes correctly.
I think that i solved also the issue of non parallel belts. I swapped the stepper motors mount plates so now i think that the belts are parallel.
I hope that the tension is correct now as well ....

Oliof do you have any idea for the mount of the end stops ? I have them connected and tested but not mounted ....

IMG_1416.jpg

@gbiski said in Microbit read temp data from Duet:

@Danal Do I have to connect the arduino via usb to duet or I can do it via http ?

I was suggesting tapping into the cable to the Panel. Literally a "Y" in the wire from Duet TX to Panel RX. The Y would go to the incremental new controller's RX. A script would look at the incoming data... the Panel asks for temperatures every 1/2 second or so. The new controller could read the responses to that, parse out the temperatures, and do anything you want with the NeoPixels.

USB is not an option from any of the imbedded controllers I mentioned because they cannot be a host.

HTTP is an option... but... that is moving to Websockets with Duet 3. Depends on how much you want to tie to D2 or be able to move to D3. If you are D2 only, there are lots of things to adapt. If you want an HTTP based ESP8266 option that already connects, reads status and temps, etc, that you could adapt to also drive NeoPixels, here is one choice: https://github.com/DanalEstes/DuetMonitor

Hi,

I print PLA at 190/60.

Overall speed 90, first last speed 20%.

Part fan is 0 for first layer, increasing by 20 per layer.

My build surface is CCTREE and it works well.

I sometimes need to use baby-stepping to get the first layer "squish" right. I print a 5 perimeter skirt to allow making this adjustment.

Frederick

@deckingman Perfect. Thanks a lot for the help !!!

@Veti Do you have a picture of your setup with the wing nuts on the gantry ?
In my start gcode i have G30 and then G29 S1.
The think s that i managed yesterday to get the 1st layers consistent in all 4 corners (without any bed mesh leveling) but after a while a get warping (on PLA) . Even if i lower the nozzle to the closest to the bed that i can go i still get warping after several layers.....
I cannot understand if it is the filaprint the issue (maybe i must take it of and install a buildtak)....
Warping 2.jpg Warping 1.jpg

This has become sort of spread out across a bunch of posts. Let me summarize, (I realize that probably a lot of people already know this... but for anyone trying to figure it all out):

Duet 2 can be on a WiFi or Ethernet network (depending on hardware model). Duet 3 can be on WiFi or Ethernet or anything else supported by the ribbon-cable-attached Single Board Computer (i.e. Pi) that is part of the Duet 3 architecture. (It is also possible to run a D3 'stand alone', meaning with no attached SBC. I'm going to ignore that for right now).

Once your Duet 2 or 3 is on a network, then anything that can run a browser can present DWC (the Duet Web Control) interface. This could be a PC, a Tablet, a Phone, etc, etc. This can be on a desktop, or attached to the frame of the printer, or wherever. With appropriate security and proxy setup, this could transit the internet and be anywhere on the planet.

A PanelDue can be plugged into a Duet 2 or 3; this is a "TTL Serial" connection and does not use any form of WiFi or Ethernet. As such, it can run on a few meters of cable, but not hundreds of meters. The PanelDue itself can have any of several sizes of touchscreen. The UI on a PanelDue is designed to operate the printer, and has several limitations as compared to 'full' DWC.

All above is the same (or very close) for D2 or D3.

A Duet 3 with attached Single Board Computer (that is, a Pi) offers one more option: The Pi will be running DWC on its HDMI terminal session. Therefore, any combination of mouse/pad, keyboard, display will present a 'full' DWC interface. This includes any of the many touchscreens already made for Pi that emulate mouse/keyboard via touch. Given that the Pi must be ribbon cabled to the Duet 3, and that the Touchscreen must be HDMI cabled + USB (typically) to the Pi, it makes most sense for this setup to be physically on the printer.

As long as the above is, it is still very summarized. Hopefully it is reasonably accurate; corrections are certainly welcome.

@gbiski said in Stepper motors and Duet 2 - Duet X2 compatibility:

@fcwilt Thanks for your reply. The current limit of 2.4a of the duet is per phase ? Because if not I cannot go over 50% for these stepper motors...

Well if is not per-phase I've been doing it all wrong.

But, to date, none of my boards have released the "magic smoke".

Frederick

@phaedrux said in Upgrading to 24v:

@makotosan the endstops aren't exposed to 12v or 24v. 3.3v only.

https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches

That's right. Thanks for the correction.

@gbiski said in BL touch help:

I mount a bltouch probe on the duet wifi. The bltouch is version 2.1.
Do I have to cut the copper line on the bltouch logic board to convert it to 3.3 logic or I can leave it as is ?

If it's a version 1.04 Duet WiFi then you don't need to cut that trace. If it's 1.03 or earlier, cut it.

@phaedrux said in Wiring a NF-A4x20 FLX Noctua:

Even the FLX should work with the Duet PWM.

It does. I'm using a NF-A4x20 FLX.
When I first installed it I had to up the M106 PWM frequency to F5000 to work at lower percentages.

Just connect the red and black and set M106 frequency to 5000.

Phaedrux,
tks a lot. I`ll check it out.

@phaedrux Thank you !!! ☺

@gbiski said in Ir probe results:

Can I ask what I do wrong ? I homed the Z with the Endstop. At the centre of the bed the distance was just equal to be able to drag a paper. So I guess the Endstop zeroed correctly.

Your Z homing s set up correctly if, when you home Z and then command the head to Z=0 and some suitable XY position, it just drags the paper. The position after homing is not necessarily Z=0, it depends on what you have in your homing files.

Try upgrading to main firmware 2.02RC4 and DWC 1.22.5. The automatic retries may solve the remaining 30%.