Topics created by toddel

@toddel DSF on the Pi has an API suitable for programs such as Octoprint to send the data through. Octoprint would need to be modified to use it. There is a version of Repetier Server that already supports this interface.

@toddel Da musst Du Dir vieles zusammensuchen. Im dozuki steht schon mal ziemlich viel. Z.B. über PA.
Im Forum nach Stichworten suchen ist die beste Möglichkeit.

Beim Motorstrom würde ich nicht über 85% des max. Stroms vom Schrittmotor gehen (muss natürlich im Range des max. Stroms vom Board sein). Ich persönlich fahre mit 75% des Maximalwerts. Den max. Strom des Schrittmotors kann man seitlich am Schrittmotor ablesen. Im Betrieb zeigt sich dann ja ziemlich schnell ob der Strom passt. Werden die Motoren sehr heiss, ist der Strom sicher zu hoch. Hast Du Schrittverluste, eher etwas höher gehen. Da sollte dann aber auch kontrolliert werden ob die Mechanik leichtgängig ist!

Für Input shaping brauchst Du ein Accelerometer... da bin ich mir jetzt aber nocht ganz sicher. Hab mich noch nicht damit beschäftigt.

@toddel there are some notes here:

https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#unstable-package-feed

That said if you don't have an issue with the stable 3.3 firmware then its often better to wait until the next stable release unless you are happy beta testing firmware!

@paulhew

Got it working! Thank you all!!!

I have it printing! Nice and sweet...

I created a macro (PrintInCopyMode)

M563 P2 D0:1 H1:2 X0:3 F1:1 ; tool 2 uses both extruders and hot end heaters, maps X to both X and U, and uses both print cooling fans G10 P2 X0 Y0 U-150 S0 R0 ; set tool offsets and temperatures for tool 2 M567 P2 E1:1 ; set mix ratio 100% on both extruders

I have Tool 0, 1 and then the new one here... Is it possible to delete T0 and 1 before? So i could switch between both modes...

Edit:
Found it:
M563 P0 D-1 H-1
M563 P1 D-1 H-1

So a Macro with:

M563 P0 D-1 H-1 M563 P1 D-1 H-1 M563 P0 D0:1 H1:2 X0:3 F1:1 S"CopyMode"; tool 2 uses both extruders and hot end heaters, maps X to both X and U, and uses both print cooling fans G10 P0 X0 Y0 U-150 S0 R0 ; set tool offsets and temperatures for tool 2 M567 P0 E1:1 ; set mix ratio 100% on both extruders

would create just the CopyTool with a click on this macro... Vice Versa from CopyMode to normal...

M563 P0 D-1 H-1 M563 P1 D-1 H-1 M563 P2 D-1 H-1 M563 P3 D-1 H-1 M563 P0 D1 H1 F0 S"E1" ; Tool0 uses Extruder0, Heater1 and Fan0 M563 P1 D0 H2 X0 F2 S"E2" ; Tool1 uses Extruder1, Heater2 and Fan2. X-axis is mapped to U G10 P0 X0 Y0 Z0 R0 S0 ; Set Tool0 axis offsets and temperatures G10 P1 X0 Y0 Z0 R0 S0 ; Set Tool1 axis offsets and temperatures

Works as it should... Nice!

As @Phaedrux says, it would likely be quicker and cheaper to go the Pi Zero route. I have found that motionOS can be a bit heavy and use lots of CPU although this does seem to vary a lot between users. I had that experience and instead use this as a lightweight streaming solution with the Pi camera. Of course - I run other things on the Pi. If you are just using it for serving up images then it will not matter.

http://picamera.readthedocs.io/en/latest/recipes2.html#web-streaming

Another alternative is an RTSP to MJPEG "converter". Depending on your platform, programing experience, and tolerance for time (noting that almost nothing works as described in google searches 🙂 ) - something like one of these approaches may be interesting.

https://stackoverflow.com/questions/43953966/rtsp-to-http-mjpeg-transcoding-embedded-in-website

https://gist.github.com/n3wtron/4624820

This is the problem:

@toddel said in IDEX U Homing?:

G1 H1 U370 F6000 ; Move U-axis to the endstop and stop (first pass)
G1 H2 U-5 F6000 ; Go back a few mm
G1 H1 U10 F700 ; Move U-axis to the endstop once more (second pass)

Stall detection doesn't work at slow speeds. So the G1 H1 U10 F700 command doesn't detect a stall, and the firmware attempts to drive the U carriage against the physical stop until it has commanded 10mm of movement. See https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing#Section_Minimum_recommended_speed_for_stall_detection.

Thats it! Thank you 😄

Hotend Fan should be named as Heatbreak Fan... Radial is the part cooling fan

@toddel said in Duet3 SBC not connecting "DCS is not available":

Thanks for that input....

Which Firmware should i flash? All are RCx....

https://github.com/dc42/RepRapFirmware/releases

the easiest is probably to the file in /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin (when the apt package for repraprfirmware is up to date it should be the correct file).

but the latest stable release to go with the latest stable dsf is RRF 3.0.

I have been searching around the forum tonight leading me to several "indirect filament sensor" threads. I believe the answer to my question above is yes. The sensor detects movement and not presence.

The laser filament sensor does have an input for a micro switch but most of the mods do not use it. I must just have an unusual use case in wanting to take advantage of the static state of knowing if filament is loaded. I was using this information to automate startup and printing.