Topics created by Proschi3D

@Proschi3D yeah I understand. Best way would be to break up the parts and call them as separate macros guarded by conditionals, but if you do that, you can use the built-in tool prep macros.

@droftarts it works 😉 !LED.jpg

@oliof Exactly. I will try to create a macro like this. I still have about 250mm of filament after the sensor, that should be enough

@Proschi78 said in Two Duet 3 Mini 5+ and two toolboards over CAN:

I think I have understood it now?! I go from my first Duet 5 to the first toolboard, then CAN L and H are simultaneously also the output to the 2nd toolboard. From the 2nd toolboard the same then to the endboard Duet 5.

That's correct.

@sebkritikel Thanks for the explanation. S3D seems to be doing it right.

I have the following code in start.g to visualize that the print has started.
I am using two Adafruit 8np for this.

M291 P"Start.g wird ausgeführt" S0 M98 P"/Macros/SUB/CheckDoor" ;Door open or closed M98 P"/Macros/LED/rot blau blinken" M561 M106 P3 S0 G4 S1 M106 P3 S25 G4 S1 M106 P3 S0 G4 S1 M98 P"/Macros/LED/grün" M290 R0 S0 M106 P3 S25 ;dimme LED for IR Probe M98 P"/Macros/LED/rot blau blinken" M98 P"/Macros/SUB/Preheat" ;Preheat for Loaded Filament if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed M150 R0 U0 B0 Y0 G28 G28 Z0 M98 P"/Macros/Buildplate" ;Load Hightmap for Buildplate and Filament M98 P"config_probe.g" M150 R255 S16 G4 P100 M150 Y0 S16 G4 P100 M150 R255 S16 G4 P100 M150 Y0 S16 G4 P100 M150 R255 S16 M150 Y0 S16 G4 P100 M150 B255 S16 G4 P100 M150 Y0 S16 G4 P100 M150 B255 S16 G4 P100 M150 Y0 S16 G4 P100 M150 R255 S16 G4 P100 M150 Y0 S16 G4 P100 M150 R255 S16

I also use the LED to visualize when the door is opened - 5 seconds of red when it's opened and 5 seconds of green when it's closed again.

@dc42 said in Idex second Z probe on the U axis:

@Proschi78 are the axes just shown incorrectly in the height map viewer, and the actual compensation applied is correct?
Please show the GCode commands that you are using to generate the height map.

I only use G29 K1

i have a Macro with the M557 U66:300 Y2:230
I start first, and then I give the G29 K1 command.
I haven't started printing yet to see if it's just rotated in the map.
I think it's better to have both on the same axis, unfortunately I don't have space on the x-axis for the additional BL touch.
Since I like to print on structured Pei, I need the Bl Touch.

@OwenD that would probably be easier.
job.filePosition

Current position in the file being processed (in bytes or null)

@oliof It works perfectly with 2 pieces. Thanks

@chrishamm said in object model aktiv extruder on an Idex:

I don't know what the value of your second gpIn port is but that script works OK on my setup if a tool is selected and if I remove the gpIn check.

it's just a magnetic switch. 0 and 1

@dc42 It was a G1 command in the intro line. The right extruder came too close to the left one. I shortened the movement by 5mm and the message disappeared. Thank you for your explanation

@Proschi78 some of the infrastructure (i.e. CAN message protocols) will be in place to support this in the 3.5.0 release, but the support for LEDs on expansion boards may have to wait a little longer.

@Proschi78 thanks for confirming that fix worked.

@OwenD I call the PID over M703. The code works as I posted it above

@achrn perfect thank you

@dc42 OK thank you
then I will solve it like this

S3D did refund my V5 without any hassle. I still use V4 sometimes, I have been using superslicer and prusaslicer 2.6 Alpha 0 with success. I need to play with a test model for a bit to see which gives me the best results. I did print some model plane parts with fair results. I think it's just a matter of dialing in settings. Once I got used to the differences in how Prusa/Super slicer works vs S3D, there are some aspects I like about them better than S3D. The only thing that is only slightly annoying is the lack of an easy way to change the part fan speed by layer. I wish it were an option in the height range modifier. As it is, you can change the part fan speed but inserting the gcode command easy enough with the insert feature. You just have to remember to change it back to the default or original value when done. I would think that could be handled automatically in the height range modifier.

Anyway, I think I have found something I like better than S3D. S3D is not horrible, but I think they have lost track of what is important and are falling behind.