Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. tobias_munich
    3. Posts
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 68
    • Best 6
    • Controversial 0
    • Groups 0

    Posts made by tobias_munich

    • RE: "how-to" mesh.g for G29 SBC setup

      @droftarts that’s why i am asking the question in this firmware-beta category my friend

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: "how-to" mesh.g for G29 SBC setup

      @PCR i know, that’s my workaround

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • "how-to" mesh.g for G29 SBC setup

      As is understood G29 on an SBC setup needs a /sys/mesh.g because the command will be handled by the DWC .

      I am using a SBC setup, therefore it would be great to understand how the mesh.g should be used.

      I didnt found any doc's or infos.

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: DWC 3.1.1: mesh will not be saved (SBC version)

      @chrishamm i am using a piezo and i had never used deployprobe/retracprobe.

      the mesh-grid size in this config is only for testing because of the described issue.

      ;M550 P"hypercube" ; set printer name
      ;M552 S1 ; enable network
      ;M586 P1 S1 ; Enable FTP
      ;M586 P2 S1 ; Enable Telnet

      ; General preferences
      M555 P2 ; Set Marlin-style output
      G21 ; Set dimensions to millimetres
      G90 ; Send absolute coordinates...
      M83 ; ...but relative extruder moves
      M667 S1 ; select CoreXY mode

      ; Debugging
      ;M111 S0 ; Debug off
      ;M929 P"eventlog.txt" S1 ; Start logging to file eventlog.txt

      ; Drives
      M569 P0.0 S1 ; physical drive 0.0 goes forwards
      M569 P0.1 S1 ; physical drive 0.1 goes forwards
      M569 P0.2 S1 ; physical drive 0.2 goes forwards
      M569 P0.3 S1 ; physical drive 0.2 goes forwards
      M569 P0.4 S1 ; physical drive 0.4 goes forwards
      M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping

      M671 X-50:330 Y150:150 F2 S2 ; leadscrews at left and right of X axis
      M208 X0:290 Y0:275

      M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation

      M92 X80.00 Y80.00 Z400.00 E2700 ; set steps per mm (E1800 für Nimble v")
      M566 X500.00 Y500.00 Z400.00 E100.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X18000.00 Y18000.00 Z2000.00 E6000 ; set maximum speeds (mm/min) (E100 war gut)
      M201 X500.00 Y500.00 Z500 E500.00 ; set accelerations (mm/s^2)
      M906 X900 Y900 Z750 E500 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X-10 Y-30 Z0 S1 ; set axis minima
      M208 X280 Y280 Z350 S0 ; set axis maxima

      ; Endstops
      ;M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io0.in
      ;M574 Y1 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io1.in
      M574 X1 S3
      M574 Y1 S3

      M574 Z1 S2 ; configure Z-probe endstop for low end on Z

      ; Z-Probe
      M558 P5 I0 R1 C"!io3.in+io3.out" H5 F320 T3000 ; set Z probe type to effector and the dive height + speeds
      G31 P1000 X0 Y0 Z-0.05 ; set Z probe trigger value, offset and trigger height (old Z-0.15)
      M557 X45:235 Y45:235 S190 ; define mesh grid

      ;M557 X15:265 Y15:265 S250 ; define mesh grid

      ; Heaters
      M140 H0 ; map heated bed to heater 0
      M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
      M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
      M143 H0 S95. ; set temperature limit for heater 0 to 120C
      M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit

      M308 S1 P"temp1" Y"thermistor" T100000 B4725 ; configure sensor 1 as thermistor on pin temp1
      M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
      M143 H1 S260 ; set temperature limit for heater 1 to 260C
      M307 H1 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit

      M308 S10 P"spi.cs1" Y"dht22" A"Chamber Temp" ; define DHT22 temperature sensor
      M308 S11 P"S10.1" Y"dhthumidity" A"Chamber Hum[%]" ; Attach DHT22 humidity sensor
      M308 S2 A"MCU-Temp" Y"mcu-temp" ; Create Sensor for MCU-Temp

      ; Fans
      M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
      M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
      M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

      ; Tools
      M563 P0 D0 H1 F0 ; define tool 0
      G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
      G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

      ; Miscellaneous
      M915 X Y S2 F0 R0 ; stall detection on X,Y
      M302 S150 R150 ; Allow extrusion

      M575 P1 S1 B57600 ; PanelDue

      M501
      T0
      ;G29 S1 ; load saved parameters from non-volatile

      posted in DSF Development
      tobias_munichundefined
      tobias_munich
    • DWC 3.1.1: mesh will not be saved (SBC version)

      Hi,
      @chrishamm

      after updating to DWC/RRF 3.1.1 the height map will not be saved if you use the menu item from the DWC.
      I have to enter G29 S3 in the console in addition to save the map.
      ....bug or feature?

      posted in DSF Development
      tobias_munichundefined
      tobias_munich
    • RE: ESP8266 Color Touchscreen Print Monitor

      this is going in a similar direction

      https://forum.duet3d.com/topic/14134/duet-buddy-a-proof-of-concept-remote-monitor

      posted in General Discussion
      tobias_munichundefined
      tobias_munich
    • RE: RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0: Heater Fault

      @dc42 yep we can close it, thanks

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0: Heater Fault

      @dc42 seems my problem was the config-override.g. My parameters out of the config-override where not loaded.

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0: Heater Fault

      @dc42 yes it has

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0: Heater Fault

      @gtj0 yep

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0: Heater Fault

      @gtj0 the print on the standalone system including DWC 2.1.2 was successful!

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0: Heater Fault

      @gtj0 its still still running, will report the final result..

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0: Heater Fault

      @gtj0 as requested new thread...

      SBC Version
      Tool: Heater Error after a couple of minutes print. I tried 3 prints, any every print fails with the following message

      Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault

      Edit: Made a new PID run for booth heaters, but the issue still exists. new test is still running now in standalone mode RC8, DWC 2.1.2

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RRF 3.01-RC8, DWC 2.1.3 and DSF 2.0.0 released

      SBC Version
      Tool: Heater Error after a couple of minutes print. I tried 3 prints, any every print fails with the following message

      Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RRF 3.01-RC8/DWC 2.1.3/DSF 2.0.0: DWC state after emergency stop

      same issue after emergency stop with DWC 2.1.3.

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RepRapFirmware 3.01-RC7 available

      I made 2 print with 5 hours print time each, with the SBC connected.

      the system is updated to the RC7 and the new DSF Framework, DWC

      the system runs stable, no reconnects anymore.

      looks good so far for me.

      have to test some macros and other topics were i had issues...

      thanks to @dc42 , @chrishamm

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: Incident report: RRF 3 RC6 DWC 2.1.0 Lockup during print.

      @Danal have exactly the same issue...

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RepRapFirmware 3.01-RC6 released

      @jmjcoke the problem is not RC6, it’s the Duetframework.
      if you run RC6 in stand-alone mode you shoudnt have issues.

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: RepRapFirmware 3.01-RC6 released

      RC6 works for me in standalone mode and is stable.
      SBC mode is still unstable.
      think the reason is still the current version of the duet framework.

      posted in Beta Firmware
      tobias_munichundefined
      tobias_munich
    • RE: DSF 1.3.1 (unstable) released

      @chrishamm @dc42 thank you guys,

      after updating via apt upgrade the system is running again.
      a new test print is running.

      Update: After 1h of printing DCS lost the connection again

      posted in DSF Development
      tobias_munichundefined
      tobias_munich