Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    need help with config.g for cr touch and swiss drive

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    8
    252
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Flynbrdundefined
      Flynbrd
      last edited by

      System - Ender 3 v1 with duet2 wifi, swiss direct drive extruder, CR touch,

      I changed the setting in config.g for swiss direct drive and CR touch. Does this look correct?

      Original
      ;Z-Probe
      M574 Z1 S2 ; Set endstops controlled by probe
      M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
      M307 H4 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
      M558 P9 H2.5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
      G31 P25 X-48 Y-10 Z1.240 ; Set Z probe trigger value, offset and trigger height
      M557 X15:185 Y50:220 S35 ; Define mesh grid

      Modified
      ; Z-Probe
      M574 Z1 S2 ; Set endstops controlled by probe
      M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
      M307 H4 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
      M950 S0 C "io7.out"
      M558 P9 C "Io7.in" H5 F120 T6000
      G31 P1000 X-48 Y-10 Z2.5 ; Set Z probe trigger value, offset and trigger height
      M557 X15:185 Y50:220 S35 ; Define mesh grid

      Swiss direct drive changes

      original
      M92 X80.00 Y80.00 Z400 E90 ; Set steps per mm

      to

      M92 X80.00 Y80.00 Z400 E135

      original config.g file anything out of place?

      ; Configuration file for Duet WiFi (firmware version 1.21)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool on Thu Sep 06 2018 21:21:12 GMT-0700 (Pacific Daylight Time)

      ; General preferences
      G90 ; Send absolute coordinates...
      M83 ; ...but relative extruder moves

      ; Network
      M550 Pe3 ; Set machine name
      M552 S1 ; Enable network
      ;*** Access point is configured manually via M587
      M586 P0 S1 ; Enable HTTP
      M586 P1 S0 ; Disable FTP
      M586 P2 S0 ; Disable Telnet

      ; Drives
      M569 P0 S0 ; Drive 0 goes backwards
      M569 P1 S0 ; Drive 1 goes backwards
      M569 P2 S1 ; Drive 2 goes forwards
      M569 P3 S0 ; Drive 3 goes backwards
      M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
      M92 X80.00 Y80.00 Z400 E135 ; Set steps per mm
      M566 X1000 Y1000 Z100 E30000 ; Set maximum instantaneous speed changes (mm/min)
      M203 X6000 Y6000 Z500 E1500 ; Set maximum speeds (mm/min)

      M201 X300 Y300 Z100 E5000 ; Set accelerations (mm/s^2) was 500 you changed it to 300 for stall guard
      M906 X500 Y500 Z500 E1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
      M84 S300 ; Set idle timeout

      ; Axis Limits
      M208 X0 Y0 Z0 S1 ; Set axis minima
      M208 X235 Y235 Z250 S0 ; Set axis maxima

      ; Endstops
      M574 X1 Y1 S1 ; Set active high endstops

      ; Z-Probe
      M574 Z1 S2 ; Set endstops controlled by probe
      M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
      M307 H4 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
      M558 P9 H2.5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
      G31 P25 X-48 Y-10 Z1.240 ; Set Z probe trigger value, offset and trigger height
      M557 X15:185 Y50:220 S35 ; Define mesh grid

      ; Heaters
      M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
      M143 H0 S120 ; Set temperature limit for heater 0 to 120C
      ;M305 P1 X150 T"K" ; Set THERMOCOUPLE parameters for heater 1 X150 is the right channel (terminal block) on the daughterboard. X151 is the left channel.
      M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
      M143 H1 S345 ; Set temperature limit for heater 1 to 345C

      ; Fans
      M106 P0 S0 I0 B0.5 F250 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
      M106 P1 S1 I0 B0.5 F500 L255 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Minimum Speed is 1/3 aka 87 Thermostatic control is turned on triggered at nozzle temp 45;
      M106 P2 S0 I0 B0.5 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

      ; Tools
      M563 P0 D0 H1 ; 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

      ; Automatic power saving
      M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

      ; Custom settings
      M591 D0 P5 C3 R10:300 E3.0 S1 ; Duet3D laser sensor for extruder drive 0 is connected to endstop input 3 (E0), tolerance 10 to 120%, 3mm comparison length

      0
      

      1 out of 1

      1 Reply Last reply Reply Quote 1
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Please send M122 and M98 P"config.g" in the gcode console and copy and paste the results here. Would like to check your firmware version because your config is using old syntax.

        Z-Bot CoreXY Build | Thingiverse Profile

        Flynbrdundefined 1 Reply Last reply Reply Quote 0
        • Flynbrdundefined
          Flynbrd @Phaedrux
          last edited by

          @Phaedrux Thank you for the quick reply, I keep trying to post but it's getting flagged as spam. going to try to break it up.

          = RTOS ===
          Static ram: 28380
          Dynamic ram: 96224 of which 0 recycled
          Exception stack ram used: 332
          Never used ram: 6136
          Task NETWORK ready, free stack 396
          Task HEAT blocked, free stack 1256
          Task MAIN running, free stack 3568
          === Platform ===
          Last reset 00:01:13 ago, cause: power up
          Last software reset at 2020-04-10 15:57, reason: User, spinning module GCodes, available RAM 6060 bytes (slot 2)
          Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
          Error status: 0
          Free file entries: 10
          SD card 0 detected, interface speed: 20.0MBytes/sec
          SD card longest block write time: 0.0ms
          MCU temperature: min 19.7, current 20.1, max 20.1
          Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0
          Driver 0: standstill, SG min/max not available
          Driver 1: standstill, SG min/max not available
          Driver 2: standstill, SG min/max not available
          Driver 3: standstill, SG min/max not available
          Driver 4: standstill, SG min/max not available
          Date/time: 2023-01-26 20:51:20
          Slowest loop: 9.78ms; fastest: 0.08ms
          === Move ===
          Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
          Scheduled moves: 0, completed moves: 0
          Bed compensation in use: none
          Bed probe heights: 0.000 0.000 0.000 0.000 0.000
          === Heat ===
          Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
          === GCodes ===
          Segments left: 0
          Stack records: 1 allocated, 0 in use

          === Network ===
          Slowest loop: 201.94ms; fastest: 0.01ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
          HTTP sessions: 1 of 8

          === Filament sensors ===
          Extruder 0 sensor: position 0.00, ok, framing errors 0, parity errors 0, no calibration data

          M98 P"config.g"

          HTTP is enabled on port 80
          FTP is disabled
          TELNET is disabled

          1 Reply Last reply Reply Quote 1
          • Phaedruxundefined Phaedrux moved this topic from Gcode meta commands
          • Phaedruxundefined
            Phaedrux Moderator
            last edited by

            It looks like the top half of the M122 results are missing.

            Can you send M115 to get the firmware version summary?

            Z-Bot CoreXY Build | Thingiverse Profile

            Flynbrdundefined 1 Reply Last reply Reply Quote 0
            • Flynbrdundefined
              Flynbrd @Phaedrux
              last edited by

              @Phaedrux yeah the spam filter kept me from posting all of it , let me try again,
              M115
              FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.0(RTOS) ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-06-05b3

              M122 part1

              Static ram: 28380
              Dynamic ram: 96224 of which 0 recycled
              Exception stack ram used: 332
              Never used ram: 6136
              Task NETWORK ready, free stack 324
              Task HEAT blocked, free stack 1256
              Task MAIN running, free stack 3568
              === Platform ===
              Last reset 00:02:19 ago, cause: power up
              Last software reset at 2020-04-10 15:57, reason: User, spinning module GCodes, available RAM 6060 bytes (slot 2)
              Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
              Error status: 0
              Free file entries: 10
              SD card 0 detected, interface speed: 20.0MBytes/sec
              SD card longest block write time: 0.0ms
              MCU temperature: min 16.1, current 20.1, max 20.4
              Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0
              Driver 0: standstill, SG min/max not available
              Driver 1: standstill, SG min/max not available
              Driver 2: standstill, SG min/max not available
              Driver 3: standstill, SG min/max not available
              Driver 4: standstill, SG min/max not available
              Date/time: 2023-01-26 22:13:08
              Slowest loop: 24.13ms; fastest: 0.07ms
              === Move ===
              Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
              Scheduled moves: 0, completed moves: 0
              Bed compensation in use: none
              Bed probe heights: 0.000 0.000 0.000 0.000 0.000

              Phaedruxundefined 1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator @Flynbrd
                last edited by

                @Flynbrd said in need help with config.g for cr touch and swiss drive:

                FIRMWARE_VERSION: 2.0

                Your board is quite old and the firmware is from 2018.

                This would be a good time to update.

                If you still have access to DWC. Upload these zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
                https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
                https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
                https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
                https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.5.zip

                That will get your firmware and DWC up to date.

                You can see the change logs here:
                https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

                For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
                https://configtool.reprapfirmware.org/Start

                Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

                These documents will come in handy during the conversion.
                https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
                https://docs.duet3d.com/en/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3
                https://docs.duet3d.com/en/User_manual/Reference/Gcodes

                Z-Bot CoreXY Build | Thingiverse Profile

                Borgtribbleundefined 1 Reply Last reply Reply Quote 1
                • Borgtribbleundefined
                  Borgtribble @Phaedrux
                  last edited by

                  @Phaedrux Thanks again, I didn't realize that the firmware had to be done in steps. I original ran the most current firnware weeks ago and called it a day. Last night I got it all updates done with no issue, now to work on the setting for the mc touch and direct extruder. Thank for all the info provided

                  Phaedruxundefined 1 Reply Last reply Reply Quote 1
                  • Phaedruxundefined
                    Phaedrux Moderator @Borgtribble
                    last edited by

                    @Borgtribble It depends where you start in the upgrade path. If you're already on 3.x it's a lot more straightforward. The order I've given just ensures you have all the files needed in case you want to go back and forth between versions at some point. I include 3.3 because the firmware folder was added in that release.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 1
                    • First post
                      Last post
                    Unless otherwise noted, all forum content is licensed under CC-BY-SA