Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order
    1. Home
    2. fulg
    • Profile
    • Following 1
    • Followers 1
    • Topics 7
    • Posts 87
    • Best 8
    • Groups 0

    fulg

    @fulg

    9
    Reputation
    10
    Profile views
    87
    Posts
    1
    Followers
    1
    Following
    Joined Last Online
    Location Montreal, QC (Canada)

    fulg Follow

    Best posts made by fulg

    • RE: Missing Steps - Cant Print SpreadCycle StealthChop tuning help

      Just another data point: I am having a similar problem on a CoreXY setup, Mini5+ and 0.9 motors. The printer worked perfectly with a Duet2 but will randomly (and loudly!) skip steps with a Mini5+.

      I have raised the motor amps and lowered jerk a lot (M566), reduced travel & print speed in the slicer, forced spreadCycle mode all the time on XY but still I get skipping, exactly like @carcamerarig describes (suddenly a loud "thump" and then there is a major layer shift). It is random, sometimes I can finish a small print but usually not.

      I see this in the M122 dump, could it be related? Write errors, timeouts, failedOps...

      Driver 0: position 99200, standstill, SG min/max 0/54, read errors 0, write errors 1, ifcnt 59, reads 53605, writes 19, timeouts 184, DMA errors 0, failedOp 0x41
      Driver 1: position 0, standstill, SG min/max 0/52, read errors 0, write errors 1, ifcnt 59, reads 53758, writes 19, timeouts 31, DMA errors 0, failedOp 0x72
      Driver 2: position 5755, standstill, SG min/max 0/56, read errors 0, write errors 1, ifcnt 58, reads 53596, writes 18, timeouts 194, DMA errors 0, failedOp 0x6f
      Driver 3: position 0, standstill, SG min/max 0/56, read errors 0, write errors 1, ifcnt 58, reads 53650, writes 19, timeouts 138, DMA errors 0, failedOp 0x6f
      Driver 4: position 0, standstill, SG min/max 0/62, read errors 0, write errors 1, ifcnt 41, reads 53792, writes 13, timeouts 3, DMA errors 0, failedOp 0x01
      Driver 5: position 0, standstill, SG min/max 0/510, read errors 0, write errors 1, ifcnt 55, reads 53598, writes 18, timeouts 192, DMA errors 0, failedOp 0x72
      Driver 6: position 0, standstill, SG min/max 0/496, read errors 0, write errors 1, ifcnt 55, reads 53787, writes 18, timeouts 3, DMA errors 0, failedOp 0x41
      

      I tried upgrading from 3.2.2 to 3.3b2 and that made no difference, skipping is still random.

      posted in Tuning and tweaking
      fulg
      fulg
    • RE: [RRF3.3b2] Possibly incorrect behavior when homing Z

      @pkos Ok, I can reproduce this here on my VORON Zero if I replace the Z endstop with a Z probe connected to the same spot (so I can use G30 Z-99999 in my homing sequence instead of G1 H1 Z-125).

      When using a single probing speed, Z=0 is established on the first probe, so the move to the dive height is small.

      When using dual probing speeds, Z=0 is not established until after the second probe, so the move to the dive height is "power up position + dive height".

      posted in Beta Firmware
      fulg
      fulg
    • Fysetc Mini12864 V2.1 on Duet3 Mini5+ in SBC mode

      Hello,

      I was trying out my new Mini5+ in SBC mode and one of the first things I did was to try and make my Fysetc LCD work, and had a surprisingly hard time doing so.

      After some messing about, I found out that the LCD does not seem to work correctly in SBC mode only. I have zero issues with the same config snippet when the Mini5+ is in stand-alone mode:

      M918 P2 R6 C30 E4 F200000
      M150 X2 R255 U255 B255 S3
      

      In SBC mode it looks like the Contrast control is not working, because I can faintly see the display when looking at an edge. There are no issues setting the color of the backlight with M150 (in 3.2.2 anyway, I know about the M150 X bug in 3.3b2).

      I am currently running RRF 3.2.2. I tried the latest 3.3b2 and at one point had it working (I could adjust the contrast and see the display just fine with 3.3b2) but after powering off the Mini5+ and powering it back up (keeping the Pi powered), the LCD didn't work anymore in 3.3b2 until I went back to stand-alone mode with the same config.

      Perhaps I will hold off to using SBC for now...

      posted in General Discussion
      fulg
      fulg
    • RE: Missing Steps - Cant Print SpreadCycle StealthChop tuning help

      @sputnikoc3d Motors are 17HM19-2004S bought directly from OMC StepperOnline.

      It seems not everyone with a Mini5+ and these motors is affected, I am talking with another VORON user who has the same Mini5+ setup with the same motors and he has no issues at any speed, with the "default" M569 parameters (i.e. no need to increase current, force spreadCycle mode or anything special). I believe he has a 0.5 board though (mine is 1.0).

      He also sees similar errors reported from the drivers in M122 but it works for him so it's probably unrelated. He is also running 3.3b2.

      Note that I am not using any of the sensorless features, I have real endstops on my machine and do not care about tuning hybrid mode (it was unusable on Maestro, I had to disable it over there too on a different printer).

      I really wish we can get to the bottom of it because I am contemplating going back to Duet2, this Mini5+ is completely unusable.

      posted in Tuning and tweaking
      fulg
      fulg
    • RE: V_Fan does not match V_In

      @steppenleguan It doesn't help that you've used the black wire for the positive side of the fan connector, but I know it doesn't really matter. 🙂

      If you look at the schematic for the Duet2 PCB, there are no components between V_IN at the screw terminal and the V_FAN jumper (not even a fuse on 1.02). Similarly, it is a straight path between the middle pin of the V_FAN jumper and the various V_FAN pins on the fan ports, and also for the GND side of the always-on ports.

      This makes no sense to me, the voltage has to match unless the board is damaged somehow.

      posted in Duet Hardware and wiring
      fulg
      fulg
    • RE: Fysetc Mini12864 V2.1 on Duet3 Mini5+ in SBC mode

      @Phaedrux I did many times, it did not. Contrast adjust does not work in SBC mode.

      There is a random element to this problem, because as I said it did work once in SBC mode (and contrast adjustments worked then) but the next time I power-cycled the Mini5+, the LCD went back to not working and I could not adjust the contrast anymore.

      posted in General Discussion
      fulg
      fulg
    • RE: Duet sometimes really slow? - I2C error or?

      So I have changed my wiring from 20AWG to a single 16AWG pair (connected exactly like the documentation, a single pair from the PSU and short wires from the Duet to the Duex). The behavior has not changed, the wiring was not to blame.

      Reproducing this is easy, leave the printer with the motors energized for 24-48 hours. Then eventually the I2C timeouts will take over and pause movements during a print, essentially ruining it. After that I get the random driver failures, which are likely caused by the I2C timeouts and not the root cause of the problem.

      One thing that might be important, my printer uses 4 motors for Z, and all four are on the Duex. XYE are on the Duet, the rest are unused. So at any given time, 7 steppers are energized. Perhaps the recent rewrites in 2.02/2.03 have some unintended side effects?

      The printer is not a new build, I have been printing for hundreds if not thousands of hours with RRF without problems. I will try going back to earlier RRF releases...

      I have attached the new diagnostics output:
      diagnostics.txt

      You can find a complete copy of my config here.

      posted in Other control boards
      fulg
      fulg
    • RE: Missing Steps - Cant Print SpreadCycle StealthChop tuning help

      @dc42 The requested info was already posted but unfortunately everything is scattered about in this thread, so here are direct links:

      M122 reports:
      https://forum.duet3d.com/post/224293 (only the driver bits)
      https://forum.duet3d.com/post/224581

      I always see these timeout errors, it is quite worrisome...

      Full config + repro file:
      https://forum.duet3d.com/post/224661

      @droftarts I was running RRF 3.2.2 but upgraded to 3.3b2 to see if it would help, no difference.

      posted in Tuning and tweaking
      fulg
      fulg

    Latest posts made by fulg

    • RE: Missing Steps - Cant Print SpreadCycle StealthChop tuning help

      @dc42 said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

      More generally: is anyone else apart from @carcamerarig still having this issue, using this firmware?

      Initially I could also reproduce the issue at will. I won't be able to confirm for a couple of weeks as I no longer have a working Mini5+ to test with (amazingly my replacement was dead on arrival, this is being handled separately by @T3P3Tony I believe).

      This will of course be one of my first tests once I get a working board in my hands again.

      posted in Tuning and tweaking
      fulg
      fulg
    • RE: Constant "connection interrupted" problems

      @t3p3tony It is unfortunate that I don't have a hot air reflow station yet. I could take this opportunity to get one but I doubt I would have the skills required to fix this properly, surely I would send that capacitor flying. 🙂

      Unfortunately the pins are just way too small on the 1624Z IC for me to reliably check if there is continuity between the socket pins and the IC.

      If it helps, the sticker on the underside of the board says Mini 5+ V1.0, 202101-0237.

      posted in General Discussion
      fulg
      fulg
    • RE: Constant "connection interrupted" problems

      @T3P3Tony The replacement is a V1.0, as was the original that was sent back.

      I took a picture of the SD card socket, looks good to me but I guess I should break out the multimeter to be sure. I did use compressed air inside the socket to make sure nothing was stuck in there, and no luck.

      IMG_1621.jpg

      posted in General Discussion
      fulg
      fulg
    • RE: Constant "connection interrupted" problems

      @phaedrux Today I received my replacement Mini5+ board. This one is much much worse, it does not even boot!

      At first I thought it was just shipped with old firmware so I upgraded it to 3.3b2 via the Mass Storage mode (pressing reset twice when connected via USB). This allowed me to see the following when I connect with a serial terminal:

      RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2
      Warning: Cannot initialise SD card 0: Card is unusable
      Ethernet is disabled.
      RepRapFirmware for Duet 3 Mini 5+ is up and running.
      

      The new board does not boot with the SD card that shipped with it (unmodified), nor with the one I used with my original Mini5+. I have tried reformatting the SD cards and refreshing their content from a backup, but the problem persists... 😞

      EDIT: downgrading to 3.2.2 does not help either:

      RepRapFirmware for Duet 3 Mini 5+ version 3.2.2
      Warning: Cannot initialise SD card 0: Card is unusable
      Ethernet is disabled.
      RepRapFirmware for Duet 3 Mini 5+ is up and running.
      
      posted in General Discussion
      fulg
      fulg
    • RE: Missing Steps - Cant Print SpreadCycle StealthChop tuning help

      @dc42 The requested info was already posted but unfortunately everything is scattered about in this thread, so here are direct links:

      M122 reports:
      https://forum.duet3d.com/post/224293 (only the driver bits)
      https://forum.duet3d.com/post/224581

      I always see these timeout errors, it is quite worrisome...

      Full config + repro file:
      https://forum.duet3d.com/post/224661

      @droftarts I was running RRF 3.2.2 but upgraded to 3.3b2 to see if it would help, no difference.

      posted in Tuning and tweaking
      fulg
      fulg
    • RE: Missing Steps - Cant Print SpreadCycle StealthChop tuning help

      Hello @droftarts, one interesting data point we seem to have found, the problem is apparently much much more likely to happen if you use bed mesh compensation. Even @oc_geek who was quoted earlier as not having isssues, enabled a bed mesh and instantly started having the same layer shifts issue.

      I looked at the start of the thread and @carcamerarig is also using a bed mesh (as shown in his M122 dump). So am I.

      So perhaps that is the key to reproduce this issue. Personally I use a 11x11 mesh to correct a 0.1mm variation in my bed (not a lot but more than enough to ruin prints!)...

      posted in Tuning and tweaking
      fulg
      fulg
    • RE: Missing Steps - Cant Print SpreadCycle StealthChop tuning help

      @carcamerarig I had the problem with M566 X600 Y600 ... and only reduced it to troubleshoot this issue by reducing instant direction changes, which I thought were causing the problem. I can go ahead and reduce acceleration too.

      posted in Tuning and tweaking
      fulg
      fulg
    • RE: Missing Steps - Cant Print SpreadCycle StealthChop tuning help

      @droftarts I only set low jerk to try and work around this issue. If you are somehow saying that low jerk and high accel could cause this, IMO this means RRF is broken (at least on Mini5+) because while it may not be ideal, this always worked before with previous Duet boards.

      One thing that was suggested to me (outside of this forum) is that I am not doing M17 and G4 P100 before moving motors the first time, reading the docs this seems to say that the required stealthChop/spreadCycle calibration of the TMC2209 will not occur. I would have expected RRF to do this implicitly, but perhaps it does and I am misunderstanding.

      There are several fixes that have been made recently that specifically target the Duet3 mini, maybe 3.3b3 will help resolve this.

      posted in Tuning and tweaking
      fulg
      fulg
    • RE: [RRF3.3b2] Possibly incorrect behavior when homing Z

      @pkos Ok, I can reproduce this here on my VORON Zero if I replace the Z endstop with a Z probe connected to the same spot (so I can use G30 Z-99999 in my homing sequence instead of G1 H1 Z-125).

      When using a single probing speed, Z=0 is established on the first probe, so the move to the dive height is small.

      When using dual probing speeds, Z=0 is not established until after the second probe, so the move to the dive height is "power up position + dive height".

      posted in Beta Firmware
      fulg
      fulg
    • RE: [RRF3.3b2] Possibly incorrect behavior when homing Z

      @pkos My printer is down at the moment but as far as I remember this works for me? Granted I did not run 3.3b2 for long, but the first trigger of the probe should establish Z=0 (you should see the "Home Z" button turn blue in DWC as soon as the probe is triggered), then the gantry rises by the dive height and the 2nd probe occurs...

      posted in Beta Firmware
      fulg
      fulg