Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. vali3d
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 26
    • Best 2
    • Controversial 0
    • Groups 0

    vali3d

    @vali3d

    2
    Reputation
    1
    Profile views
    26
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    vali3d Unfollow Follow

    Best posts made by vali3d

    • RE: Duet 3 Expansion looses Connection

      @bot https://www.dold-mechatronik.de/AE-Kompakt-Schaltschrank-Abmessung-waehlbar

      posted in Duet Hardware and wiring
      vali3dundefined
      vali3d
    • RE: Duet 3 Expansion looses Connection

      Hi,

      I have checked the M122 B1/2 comand. The firmeware update I installed in September, didn´t install the firmeware to the expansions, only to the mainboard. Now I manualy installed the 3.2beta to expansions (with the M997 B1/2) an the mainboard. I keep you updated.

      posted in Duet Hardware and wiring
      vali3dundefined
      vali3d

    Latest posts made by vali3d

    • RE: M915 won´t accept R2 or R3

      I don´t think that there is a Problem with the file. The Problem is that the R3 cant be set. When I do M915 X S3 R3 and then M915 the configuration of the axis is on the default settig.

      posted in Beta Firmware
      vali3dundefined
      vali3d
    • RE: M915 won´t accept R2 or R3

      @dc42 all relevant drivers are on the MB6HC

      posted in Beta Firmware
      vali3dundefined
      vali3d
    • RE: M915 won´t accept R2 or R3

      @jay_s_uk MB6HC+2x EXP3HC (see https://forum.duet3d.com/topic/18329/duet-3-expansion-looses-connection)

      posted in Beta Firmware
      vali3dundefined
      vali3d
    • RE: M915 won´t accept R2 or R3

      @jay_s_uk The M569 looks like this:

      M569 P0.0 S0                                                    
      M569 P0.1 S1                                                    
      M569 P0.2 S0                                                    
      M569 P0.3 S1                                                    
      M569 P0.4 S1                                                    
      M569 P0.5 S1                                                   
      M569 P2.0 S1
      M569 P2.1 S1
      M569 P1.2 S1
      M569 P2.2 S1                                                    
      M584 V0.3 W0.4 X0.5 Y0.1 Z0.0 A0.2 R0 S0 E1.2:2.0:2.1:2.2  
      
      posted in Beta Firmware
      vali3dundefined
      vali3d
    • RE: M915 won´t accept R2 or R3

      @dc42 I now created that file with some contents. Sadly that did not solve the Problem.

      posted in Beta Firmware
      vali3dundefined
      vali3d
    • RE: M915 won´t accept R2 or R3

      @jay_s_uk when I set a R1 it log them in the console

      posted in Beta Firmware
      vali3dundefined
      vali3d
    • RE: M915 won´t accept R2 or R3

      @jay_s_uk I should be able to set both modes, when testet it does not detect the crash at R2/3.

      posted in Beta Firmware
      vali3dundefined
      vali3d
    • M915 won´t accept R2 or R3

      Hello,

      I have problems getting the crash detection to work again. Since upgrading to any of the 3.4 versions the crash detection won´t trigger (see https://forum.duet3d.com/topic/26051/3-4-0-beta6-crash-detection-problems). Recently I noticed that the M915 command does not accept an R2 or R3, which might be the cause of the problems. The configuration with R1 works fine and log the crashes.

      11.2.2022, 11:44:43	M915
      Driver 0.0: stall threshold 1, filter off, steps/sec 200 (4.0 mm/sec), coolstep threshold 234 (4.0 mm/sec), action on stall: none
      Driver 0.1: stall threshold 3, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log
      Driver 0.2: stall threshold 1, filter off, steps/sec 200 (72.7 mm/sec), coolstep threshold 234 (72.8 mm/sec), action on stall: none
      Driver 0.3: stall threshold 3, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log
      Driver 0.4: stall threshold 3, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log
      Driver 0.5: stall threshold 3, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log
      11.2.2022, 11:44:36	M915 V W X Y S3 R1
      

      But any configuration with R2 or R3 results in the defult state.

      11.2.2022, 11:46:29	M915
      Driver 0.0: stall threshold 1, filter off, steps/sec 200 (4.0 mm/sec), coolstep threshold 234 (4.0 mm/sec), action on stall: none
      Driver 0.1: stall threshold 3, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none
      Driver 0.2: stall threshold 1, filter off, steps/sec 200 (72.7 mm/sec), coolstep threshold 234 (72.8 mm/sec), action on stall: none
      Driver 0.3: stall threshold 3, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none
      Driver 0.4: stall threshold 3, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none
      Driver 0.5: stall threshold 3, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none
      11.2.2022, 11:46:25	M915 V W X Y S3 R3
      

      Any idea what might be wrong?

      posted in Beta Firmware
      vali3dundefined
      vali3d
    • RE: 3.4.0 Beta6 Crash Detection Problems

      @dc42 it didn´t fix the rehoming, but I found somting interesting. I experimeted with the R parameter an it does won´t accept R2 or R3. This is the firmeware you gave me.

      17.1.2022, 14:27:37	M915
      Driver 0.0: stall threshold 1, filter off, steps/sec 200 (4.0 mm/sec), coolstep threshold 234 (4.0 mm/sec), action on stall: none
      Driver 0.1: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log
      Driver 0.2: stall threshold 1, filter off, steps/sec 200 (72.7 mm/sec), coolstep threshold 234 (72.8 mm/sec), action on stall: none
      Driver 0.3: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log
      Driver 0.4: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log
      Driver 0.5: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log
      17.1.2022, 14:27:32	M915 V W X Y S4 R1
      17.1.2022, 14:27:23	M915
      Driver 0.0: stall threshold 1, filter off, steps/sec 200 (4.0 mm/sec), coolstep threshold 234 (4.0 mm/sec), action on stall: none
      Driver 0.1: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none
      Driver 0.2: stall threshold 1, filter off, steps/sec 200 (72.7 mm/sec), coolstep threshold 234 (72.8 mm/sec), action on stall: none
      Driver 0.3: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none
      Driver 0.4: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none
      Driver 0.5: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none
      17.1.2022, 14:27:17	M915 V W X Y S4 R3
      

      When it is configured to R1 log, it does log a crash.
      On 3.3 I can configure it to rehome.

      posted in Beta Firmware
      vali3dundefined
      vali3d
    • RE: 3.4.0 Beta6 Crash Detection Problems

      @t3p3tony nothing working 😄 . I switched between log and pause, no response/pause. Then I configured one axis by M915 X R0 F0 and M574 X2 S3 to home by stall detecion, the motor stalled but ist was not detectet.

      posted in Beta Firmware
      vali3dundefined
      vali3d