• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login
  1. Home
  2. RandyL
  3. Posts
  • Profile
  • Following 0
  • Followers 0
  • Topics 2
  • Posts 5
  • Best 0
  • Controversial 0
  • Groups 0

Posts made by RandyL

  • RE: Problem with Magnetic Sensor

    @dc42,

    Thanks for the advice. I will try increasing the measurement length as you suggest. My sensor is mounted ~20mm above a direct drive extruder and was flexing around a lot. I added a brace which helped a lot but am still having issue. I will try increasing the measurement length as you suggest.

    posted in Filament Monitor
    undefined
    RandyL
    29 Nov 2019, 06:25
  • RE: Problem with Magnetic Sensor

    I seem to be having a simmer issue. I installed the mag sensor about a week ago recently purchased from Filastruder as well. It was working okfor a couple of prints then all of a sudden it started overrunning the set parameters of R60:130 L24.8 E3.0. When I swapped out the filament to Ninja Flex ( a very soft TPU) I stated seeing under runs of ~ 30 to 35%. I adjusted the "R" value accordingly and the remainder of the TPU prints finished off ok. I then swapped out my .04 nozzle for a .8mm nozzle with PLA+ and things went south. I'm now seeing under runs down to 10% and over runs up to 330% My last print was like so:

    Duet3D rotating magnet filament monitor v2 on input 3, enabled, sensitivity 25.05mm/rev, allow 10% to 370%, check every 3.0mm, current pos 259.8, measured sensitivity 25.27mm/rev, min 94% max 179% over 9348.6mm

    I replaced the the cable between the sensor the E1 stop input with a twister trio to cancel out any interference but this did not make any difference.

    My diag output:

    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-917DA-G4MSJ-6JTF0-3S86M-T9NMA
    Used output buffers: 1 of 24 (12 max)
    === RTOS ===
    Static ram: 25680
    Dynamic ram: 94232 of which 16 recycled
    Exception stack ram used: 540
    Never used ram: 10604
    Tasks: NETWORK(ready,524) HEAT(blocked,1236) MAIN(running,1668) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 01:22:56 ago, cause: software
    Last software reset at 2019-11-18 13:58, reason: User, spinning module GCodes, available RAM 10652 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 12.1ms, max retries 0
    MCU temperature: min 28.5, current 29.3, max 31.9
    Supply voltage: min 23.9, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 0/1023
    Driver 1: standstill, SG min/max 0/1023
    Driver 2: standstill, SG min/max 0/117
    Driver 3: standstill, SG min/max 0/1023
    Driver 4: standstill, SG min/max 0/107
    Date/time: 2019-11-18 15:21:31
    Cache data hit count 4294967295
    Slowest loop: 59.42ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 169, MinFreeDm: 121, MaxWait: 1366776ms
    Bed compensation in use: mesh, comp offset 0.373
    === DDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.1
    Heater 1 is on, I-accum = 0.6
    === GCodes ===
    Segments left: 0
    Stack records: 3 allocated, 0 in use
    Movement lock held by null
    http is idle in state(s) 0
    telnet is idle in state(s) 0
    file is idle in state(s) 0
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 25.93ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.23
      WiFi MAC address ec:fa:bc:01:e0:39
      WiFi Vcc 3.32, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 25464
      WiFi IP address 192.168.1.19
      WiFi signal strength -53dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0
      === Filament sensors ===
      Extruder 0: pos 250.31, ok, measured sens 25.28mm/rev min 94% max 179% over 10057.0mm, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
      3:06:28 PMFinished printing file 0:/gcodes/rEX.gcode, print time was 0h 46m
    posted in Filament Monitor
    undefined
    RandyL
    18 Nov 2019, 23:26
  • Creailty CR 10S PRO / Duet WiFi Signal strength concern

    I'm considering replacing the stock board in my CR10 Pro with a Duet WiFi. I have a Duet in by BLV Cube and love it! I am a little concerned that the CR10 Pro's all metal enclosure will block /effect the wifi reception. I have a spare Duet with with the onboard WiFi module and am hoping not to have to buy one with the external antenna option. It is an all steel case, not alumanum.

    Has anyone had luck with full metal enclosures like this?

    posted in Duet Hardware and wiring
    undefined
    RandyL
    10 Oct 2019, 23:00
  • RE: Multiple independent Z motor Z sync issue

    Veti,

    Added E0, did the trick...

    Many Thanks!👍

    posted in General Discussion
    undefined
    RandyL
    8 Apr 2019, 01:45
  • Multiple independent Z motor Z sync issue

    I'm trying to convert my Duet Wifi to use independent Z drivers so I can auto level the gantry. I followed the instructions here: https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors#Section_Example_for_2_motors

    When I boot up the board and try to move the Z axis, the side connected to the Z stepper moves faster (farther) than the motor connected to the E1 extruder stepper. I verified this by flipping the motor connections. If I flip the connections the issues moves to the other side so I know it's the board. If I go back to connecting the two motors in series they move in parallel.

    I'm running firmware version:2.02(RTOS) (2018-12-24b1). My config looks like so:

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

    ; Gantry Leveling
    M584 X0 Y1 Z2:4 ; two Z motors connected to driver outputs Z and E1
    M671 X-20:335 Y0:0 S0.5 ; leadscrews at left and right of X axis
    M208 X0:315 Y0:315 z0:400 ; X carriage moves from -5 to 205, Y bed goes from 0 to 200
    Drives
    M569 P0 S0 ; Drive 0 goes backwards
    M569 P1 S0 ; Drive 1 goes backwards
    M569 P2 S1 ; Drive 2 goes forwards
    M569 P3 S1 ; Drive 3 goes forwards
    M569 P4 S1 ; Drive 3 goes forwards

    M350 X16 Y16 Z16 I1 ; Configure microstepping with interpolation
    M350 E32 I1 ; Configure microstepping with interpolation

    M92 X80.00 Y80.00 Z408.00 E835.50 ; Set steps per mm - was 400, E837

    M566 X600.00 Y600.00 Z24.00 E300.00 ; Set maximum instantaneous speed changes (mm/min)
    M203 X12000.00 Y12000.00 Z600.00 E1500.00 ; Set maximum speeds (mm/min)

    M201 X500.00 Y500.00 Z100.00 E5000.00 ; Set accelerations (mm/s^2)
    M906 X800.00 Y800.00 Z800.00 E800.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    Any advice will be most welcome!

    posted in General Discussion
    undefined
    RandyL
    7 Apr 2019, 19:05
Unless otherwise noted, all forum content is licensed under CC-BY-SA