Posts made by Gaou

i ve managed to get some results working a bit with lightburn. i also noticed ( i have read it already) that both lightburn and laserweb can connect to the duet3d . I didn't try to control the the machine through them . i am using the web interface at the moment.

a short video

the upper right one is the clearest one but it still needs some more tweaking.

i am using both of the pwm fans output to control the laser ( FAN0) and the exhaust fan (FAN1) and the workaround for the second fan is to replace the M8 M9 from Lightburn to M106 P1 S1 or S0

@phaedrux

first of all thanks for ur insistense on my request.

there is no need for DC to step in the post. i think he has already too many things to care. I will qo on with the m106 command. It would do the job alright, it just would be safer for that kind of cnc ( laser beam) to act only on G1'sx.

if i send m450 i am getting a laser mode....

@phaedrux said in co2 Laser fire duet 0.85:

@gaou said in co2 Laser fire duet 0.85:

"bad p parameter"

So P20 is correct I think, but we may have missed the important step of freeing up the pin first by disabling the fan with M106 P0 I-1. So give that a try.

Look at my first post. I have already tried it and didn't get anything.

@phaedrux said in co2 Laser fire duet 0.85:

@gaou said in co2 Laser fire duet 0.85:

@phaedrux

if i send M452 p20 s1 the firmware says "bad p parameter"

Sorry, I think I may have been looking at the wrong logical pin number section.

Here's the one for the 0.85 board. Which of those listed pins are you using? Keep in mine, I have zero familiarity with the older pre-Duet2 boards.
https://duet3d.dozuki.com/Wiki/Using_servos_and_controlling_unused_IO_pins#Section_Duet_0_6_and_0_8_Num_5

i cant understand how are these connected to fan0 . all of these seems to be at the expansion header.

@o_lampe said in co2 Laser fire duet 0.85:

@gaou
I've played with diode laser on older RRF versions, but never use M571 or M452. There was a plugin raster2gcode and others in inkscape, that allowed me to use M106 P0 Snnn to switch power on and M107 (or M106 P0 S0) to power off.
What concernes me are the high currents you run your 40W? laser tube with. I'd never go above 12mA, better stay around 10mA for cutting.

I keep that in mind but i would prefer to do this by the lightburn way....! I was thinking of writhing a macro and change the gcode on notepad++ .
I knew that inkscape can write gcode for the lasers but because of my job i am very addicted to lightburn that comes with the big lasers. I am so addicted to duet also....! ANyway this is probably the way to go and thanks that bringing this up...

I cant remember what exactly was the power range of this tube and it is the second i own ( sold the first) but during the tests i am using a test resistor that is intended for that job. it can stand up to 100w power ..

Thanks a lot for replying.

@phaedrux

if i send M452 p20 s1 the firmware says "bad p parameter"

@phaedrux said in co2 Laser fire duet 0.85:

Looking at the release notes it looks like M452 should be supported farther back than 1.26.1

So what is the syntax of your M452 command?

With access to laser mode, you wouldn't need to use M571 anymore as long as your laser gcode generation software can output G1 S commands to set laser power.

M452 P"FAN0" S1 . i also tried P0 instead P"FAN0"

please keep in mind that if i send M106 P0 S255 the laser fires.

@phaedrux said in co2 Laser fire duet 0.85:

M452 would be more desirable if your firmware version supports it. Which I'm not certain.

What happens if you send M452?

https://docs.duet3d.com/User_manual/Reference/Gcodes#m452-select-laser-device-mode

i am sending M452 and didn't got any responce. I have a m452 in my config file .

@phaedrux said in co2 Laser fire duet 0.85:

What is the syntax of your M571 command?

https://docs.duet3d.com/User_manual/Reference/Gcodes#m571-set-output-on-extrude

It is "M571 P0 S1". but i ve read that since there is an M452 in mt config an M3 is the proper command for getting the laser on. I am very confused...

@phaedrux said in co2 Laser fire duet 0.85:

What firmware version are you currently on? The latest firmware for that board is 1.26.1 I believe.

yeap this is what i am using....

edit: i still cant get the M571 to work, although i send a M106 P0 I-1.

@alankilian said in co2 Laser fire duet 0.85:

@gaou I haven't ever use a LASER, but maybe THIS page can help you figure it out.

thanks for replying . this page is for the newer versions of duet so i dont think it is suitable for my duet.

for now i need only to fire it up and no control over the power.

Guys i need some guidance for my small laser to get fire when it moves.

I ve put in my gcode an M106 with a I-1 to get the fan0 able to use M571 but i am getting an error saying "Logical pin 0 is already in use or not available for use by M571".

I am able to fire the laser when M106 P0 S1(0-1) which is give me around 17mA or S255 (0-255) where i am getting more than 20mA, but i dont know what to do to make it fire when it is moving.

This is my config.g

Any help would be very much appreciated.

@phaedrux said in Delta Z triggered height:

Can you share your config, homedelta, bed.g, M122, etc?

config.g bed.g

@phaedrux said in Delta Z triggered height:

Do this test at multiple points on the bed. Test each point multiple times.

https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Calibrate_the_Z_probe_trigger_height

This is the procedure i follow. done this hundered times on each of my printers.

Do you have variance over multiple probings at the same spot?

Yeap....

Do you have variance between different XY points on the bed?

Yes

@phaedrux said in Delta Z triggered height:

Have you actually measured a variance in trigger height based on XY location?

i am not sure i got what you asked. in every bed point of my 10's i got a different triggered height.. even in one spot ( let's say the center i got a different triggered height every time . on the X0Y0 there is a variation of one thousand of a milimeter no matter what i do ...!

@t3p3tony said in Delta Z triggered height:

@gaou said in Delta Z triggered height:

procedure to measure triggered heights by smart effector.

part of the benefit of using a smart effector is that the nozzle is the probe so you should not need to set individual trigger height offsets for each probe point.

i am trying to fine tune my deltas and as far as i know i have to go trough the process that documentation says. i am printing alright but i want to go after for that perfect thing.

@phaedrux said in Delta Z triggered height:

@gaou said in Delta Z triggered height:

On the documentation is says that i need to specify the triggered height for the center of the bed and then every point on my bed config.

Can you point me to the page you're seeing this please?

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

Guys i need some help for tweaking my deltas.

First of all i was wondering about the procedure to measure triggered heights by smart effector. So my question is a mathematics one sort of.

On the documentation is says that i need to specify the triggered height for the center of the bed and then every point on my bed config.
So the H parameter says it is triggered height at a point minus the triggered height on the center of the table .

That means that if i have a triggered height -0.10 on the X0Y0 and -0.30 at a specific point X0Y128 the nnn is -0.40 ? Am i doing it right or i am on a wrong path ?

@dougal1957 why ?

ok my mistake . my dive height is 10 at this moment .

video: effector slipping.mp4
i think i ve found the problem. one of my magballs carriage was tilting a little. fix that and everything is back in order now...

thanks anyway guys.