Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. Aitor
    • Profile
    • Following 4
    • Followers 0
    • Topics 39
    • Posts 181
    • Best 17
    • Controversial 0
    • Groups 0

    Aitor

    @Aitor

    24
    Reputation
    62
    Profile views
    181
    Posts
    0
    Followers
    4
    Following
    Joined Last Online

    Aitor Unfollow Follow

    Best posts made by Aitor

    • RE: [3.4b3] Homing to negative Y doesn't work

      Good morning @diamondback

      https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta-&-RC#reprapfirmware-340beta2
      Where a GCode parameter accepts multiple values, you can no longer use a mixture of literals and expressions (which was previously supported in standalone mode only). However, the whole parameter can now be an array expression. For example, M92 E{var.e1}:400:{var.e3} will no longer work and must be replaced by M92 E{var.e1,400,var.e3}.

      In your case this is how it should be:

      M208 X-150:160 Y{global.minY,global.maxY} C0:250 Z0:270     ; set axis minima & maxima
      

      Check if you have any more

      I don't know if this will be the solution for your problem.

      Best regards

      posted in Beta Firmware
      Aitorundefined
      Aitor
    • RE: How to get the result of a M command

      Good morning @siam ,

      Check the object models, in version 3.2 onwards DWC has a plugins to display them, you can also check this section https://duet3d.dozuki.com/Wiki/Object_Model_of_RepRapFirmware#main

      in your case it would be this: heat.heaters[0].avgPwm

      Best regards

      posted in Gcode meta commands
      Aitorundefined
      Aitor
    • RE: In Duet3: Z does not respond as expected

      Good morning @fcwilt , you're right, that would work anyway, but from experience, if you miss an endstop, it will try to get to it for all that extra run and it's annoying, but yes, it would work anyway.

      Anyway, I installed firmware 3.4beta3 and it doesn't fail me anymore, and from what I've read in the fixes, it's fixed since 3.4beta1, now I just need to test the rest of the stuff XD

      Best regards and thanks to all

      posted in Duet Hardware and wiring
      Aitorundefined
      Aitor
    • RE: Single Axis multiple stepper with different steps/mm possible?

      Good morning @jay_s_uk

      Ok, that's clear, a pity because it would have been a good solution for @NORDLE

      And you are right, because I couldn't avoid doing a test, and although it doesn't show error when putting M92 Y100:150 it only keeps M92 Y100 and the axes move correctly.

      Thanks for the clarification

      posted in Firmware installation
      Aitorundefined
      Aitor
    • RE: A fifth option for M291: Display message / wait for response

      Good morning,

      Since I have seen this post, I would like to add my idea that I have had for a long time.

      It would be to add a M291 S4 message that would give the option of "Yes" or "No" and on the other hand that you could add for example a C parameter, for example C "global.reply" and that this would make a: set global.reply = ("yes" or "no") or (true or false)

      It would also be interesting that "this parameter C" in the formats S2 and S3 with X1 Y1 Z1 would save the value of these in the variable, I do not know if in this particular case, which has been requested to show more than one axis, maybe it should be something like this C"{global.xpos,global.ypos,global.zpos}" or maybe the ideal is to request them separately.

      I think these options would open many possibilities to interact with the user.

      Let's see what you think of my idea

      Best regards

      Sorry if something is not well understood, it is very difficult for me to write in English.

      posted in Firmware wishlist
      Aitorundefined
      Aitor
    • RE: [3.5.0-beta.3] Duet2-wifi + Duex5

      Good morning @HERVE_SMITH and @PHAEDRUX,

      I greatly appreciate your response, as it allowed me to solve my problem. The truth is that I was unaware of many of the parameters offered by M569. Thank you again.

      Best regards,
      Aitor

      posted in Firmware developers
      Aitorundefined
      Aitor
    • RE: How can I verify that a file exists

      Good morning @phaedrux @dc42 @owend @oozebot

      When I deleted the double quotes it didn't give me an error, but it generated a blank file, I realised it was because I was trying to run M916 but it didn't exist yet, so I solved it this way.

      M911 S22 R23 P "M913 X0 Y0 Z0 E0 M28""0:/sys/runonce.g"" M98 P""run1.g"" M29"

      in run1.g I typed M916 and this did work as expected

      only that runonce.g is not deleted, something that is good for me because I thought that if I had two blackouts in a row without having recovered this would be deleted and would not work as I wanted, when I finish printing is not deleted either, only to restart again, this makes some errors appear, so I added to my final script and my cancel.g a M30 to delete it.

      This was my solution and it works fine so far:

      config.g I added:

      M911 S22 R23 P "M913 X0 Y0 Z0 E0 M28""0:/sys/runonce.g"" M98 P""run1.g"" M29"
      ; Global Variables
      global delete = 0
      

      run1.g contains:

      set global.delete = 1
      M916
      

      resurrect-prologue.g contains:

      var temp = heat.heaters[1].active
      
      M116 ; wait for temperatures
      G28 XY ; house X and Y, hope Z hasn't moved
      G10 P0 S0
      M291 R "Recovery" P "Want to recover the part" S2 T0
      G10 P0 S{var.temp}
      M116 P0
      

      final script I added: (resurrect.g if automatically deleted)

      if global.delete = 1
      	M30 "/sys/runonce.g"
      	set global.delete = 0
      

      cancel.g I added:

      if global.delete = 1
      	M471 S"/sys/resurrect.g" T{"/sys/resurrect1.g"} D1 ; I rename it in case I want to use it later on.
      	M30 "/sys/runonce.g"
      	set global.delete = 0
      

      I hope you find this solution useful and if you think of any improvement I will be happy to hear it.

      Best regards and thanks for your support.

      posted in Using Duet Controllers
      Aitorundefined
      Aitor
    • echo commands

      Good morning to all,

      I would like to request a new function for echo commands.

      Currently echo>> writes to a new line of the specified file, but I would like to be able to write to the end of the last line for example using echo>>>, this way I would have no problem writing longer lines and I think it would consume less resources than increasing the number of characters allowed in a single line.

      This could be used to write comments or in my case to generate a superlicer profile automatically from the machine.

      By the way I love the new features of the M291.

      Best regards
      Aitor

      posted in Firmware wishlist
      Aitorundefined
      Aitor
    • [3.5.0-beta.3] Problems found with this version

      Good morning @DC42,

      Currently, I am using stepper motors with brakes that have been configured as follows:

      M569.7 P0.2 S100 C"out3"
      

      However, I have noticed that the brake does not activate when executing the M84 command. This is different from what happened in version 3.4.0 of the firmware. Additionally, I have also observed that the brake does not activate immediately when using the emergency stop on the DWC control panel. It is possible that both situations are related.

      If you need more information or if my explanation is unclear, please do not hesitate to ask.

      Regards,
      Aitor

      posted in Firmware developers
      Aitorundefined
      Aitor
    • RE: WIFI without Password

      Good morning @engikeneer,

      Yes, that's how they are working so far, thanks for your input.

      Good morning @dc42,

      Perfect, it worked correctly, I wouldn't have thought that it could work like that. 😂

      I would recommend adding a note in the documentation, I've been thinking for 2 years that it wasn't possible, until I thought to ask. 😂

      Thank you very much to all of you

      Best regards

      posted in Using Duet Controllers
      Aitorundefined
      Aitor

    Latest posts made by Aitor

    • RE: How to Monitor MCU Temperature on 3HC?

      Thank you very much, @dc42. I’ll try it out next time. Wishing the whole team a Merry Christmas!

      posted in General Discussion
      Aitorundefined
      Aitor
    • How to Monitor MCU Temperature on 3HC?

      Good morning everyone,

      I’m trying to set up two thermostatic fans to ventilate the MCU and electronics, based on the MCU temperature, using the following code:

      M308 S10 Y"mcu-temp" A"MCU"                                   ; Set or report sensor parameters  
      M950 F13 Q500 C"1.out4"                                       ; Configure MCU fan  
      M950 F14 Q500 C"1.out5"                                       ; Configure MCU fan  
      M106 P13 S1 T25:70 C"MCU Fan" H10                             ; Set fan configuration  
      M106 P14 S1 T25:70 C"MCU Fan" H10                             ; Set fan configuration
      

      The issue I’m facing is that I don’t have any available outputs on the Duet 6HC, so I have no choice but to use the last two outputs on the Duet 3HC. I understand that the problem is that since I’m monitoring the MCU temperature of the Duet 6HC, I should be using outputs from the 6HC and not the 3HC.

      So, my question is: how can I monitor the temperature of the 3HC instead of the 6HC? I’ve tried M308 S10 Y"1.mcu-temp" A"MCU", but, as expected, it didn’t work.

      Best regards,

      posted in General Discussion
      Aitorundefined
      Aitor
    • RE: Issues with Intermittent Stopping of the Z-Axis Motor

      Good morning @dc42,

      The endstop cables run close to the stepper motors, and they are also the longest cables on the setup. After the tests I conducted over the weekend, I’ve concluded that the issue is indeed signal interference, likely caused by the motors. Unfortunately, I can’t change the wiring at this time, so I’ll only be able to make this adjustment later on.

      As a workaround, is there any way to make all the independent motors stop upon detection by any endstop sensor? If not, could this option be added as G0 H5?

      Best regards,

      posted in Duet Hardware and wiring
      Aitorundefined
      Aitor
    • RE: Issues with Intermittent Stopping of the Z-Axis Motor

      Good morning @droftarts,

      In my case, the sensors.endstops[2].triggered object model shows true whenever any endstop is triggered, and I haven’t found an alternative to monitor them individually.

      An alternative solution I thought of was to stop all motors whenever any endstop is detected. I tried using the G0 H4 command, hoping it would work this way, but it didn’t. My idea was to send G0 H4 repeatedly and then keep the Z homing as is. My approach would look something like this:

      ; homez.g
      ; Homing for the Y-axis
      
      G91                              ; Set to relative positioning
      G1 H4 Z{move.axes[2].max} F3000  ; Move
      G4 S1
      M400
      G1 H4 Z{move.axes[2].max} F3000  ; Move
      G4 S1
      M400
      G1 H4 Z{move.axes[2].max} F3000  ; Move
      G4 S1
      M400
      G1 H1 Z{move.axes[2].max} F3000  ; Move
      G1 H2 Z-5 F6000                  ; Move
      G1 H1 Z{move.axes[2].max/2} F360 ; Move
      G90                              ; Set to absolute positioning
      M400                             ; Wait for current moves to finish
      

      The pause was just to check if it would work and give me time to react, but H4 did not stop all motors. If it had worked this way, I could avoid any false trigger, and it would only be noticeable in cases where it actually occurred, preventing issues with the Z-axis.

      I know my circuit has many connections, but this shouldn’t be an issue. Moreover, I haven’t noticed this behavior in XYU, where X and U have even more connections (two more than Z), so I’d like to think that’s not the case.

      Best regards,

      posted in Duet Hardware and wiring
      Aitorundefined
      Aitor
    • RE: Issues with Intermittent Stopping of the Z-Axis Motor

      Good morning @droftarts,

      I activated the internal pull-up resistor, as I mentioned earlier, and it seemed to work well; I completed a cycle of 100 without any issues. To be sure, I then ran a cycle of 1000, but this time it failed on cycle 115 out of 1000. This time, it was Z2 again, but I can confirm that both Z1, Z2, and Z3 have failed at different times. I think it’s unlikely that this is due to the connections. I also checked that the endstop isn’t getting stuck, and it isn’t. So, I’m not sure where this error might be coming from. I also ran this macro for over 12 hours and didn’t get the error message, though the machine was completely stationary during that time.

      while true
          if sensors.endstops[2].triggered == true
              break;
      M400
      M291 R"Final de carrera Z" P"Final de carrera Z pulsado" S2
      

      Best regards,

      posted in Duet Hardware and wiring
      Aitorundefined
      Aitor
    • RE: Issues with Intermittent Stopping of the Z-Axis Motor

      Good morning @droftarts,

      @droftarts said in Issues with Intermittent Stopping of the Z-Axis Motor:

      Does the motor stop before any of the motors have hit an endstop? If so, I'd guess the problem was a poor/loose connection in the endstop wiring. Check the wiring to all the endstops. I don't think a pullup helps here, because they are wired NC.

      Exactly, my motor stops before reaching the endstop. Before writing this, I checked all my Z-axis connections and replaced all the relevant cables. To give you an idea of how it's connected, my endstop is connected to a custom-designed PCB; from this board, via a flat cable, it goes to another PCB, and from there, two of the motors (Z1 and Z2) connect to another PCB through a different flat cable. From here, the system connects to the Duet3hc, while Z3, due to its location, goes directly to this last PCB.

      Today, I am running tests after modifying the Z homing routine, which I changed this way following your recommendation.

      ; homez.g
      ; Homing for the Y-axis
      
      G91                              ; Set to relative positioning
      G1 H1 Z{move.axes[2].max} F3000  ; Move
      G1 H2 Z-5 F6000                  ; Move
      G1 H1 Z{move.axes[2].max/2} F360 ; Move
      G90                              ; Set to absolute positioning
      M400                             ; Wait for current moves to finish
      

      I'm running this testing macro while writing this message, and the Z3 motor failed on loop 53 out of 100. I re-ran the macro, and this time Z2 failed on loop 71 out of 100. In each case, it always fails during homing, never with regular movement commands. Yesterday, I ran this same cycle, moving the Z axis up and down 1000 times without homing, just moving it from position Z0 to Z{move.axes[2].max-1}, and there were no failures, so I can rule out a mechanical cause. As for the error itself, it happened while I was present, and I could see that the motor that stops does not even attempt to move, while the other two, which are always positioned lower, keep trying to move. This is logical since none of them have reached their endstop.

      if state.status = "processing" || state.status = "paused"
      	M118 S{"Cannot use during "^state.status}
      	M99
      
      var cycle = 0
      var count = 0
      M291 R"Number of Cycles" P"Enter the number of cycles you want to perform" S5 L1 F10
      set var.cycle = input
      M400
      while var.count <= var.cycle
      	M118 S{var.count^" of "^var.cycle}
      	G28 Z
      	G0 Z{move.axes[2].max-20} F{move.axes[2].speed}
      	set var.count = var.count+1
      

      On another note, if I wanted to test enabling the internal Pull Up, would it be safe to configure it like this in my case?

      M574 Z2 S1 P"^1.io2.in+^1.io1.in+^1.io0.in"                      ; Endstop configuration
      

      Best regards,
      Aitor

      posted in Duet Hardware and wiring
      Aitorundefined
      Aitor
    • RE: Issues with Intermittent Stopping of the Z-Axis Motor

      Good morning @droftarts,

      I have reviewed my circuit and can only implement a Pull-Up connection. My intention is to place a 220-ohm resistor from my 5V to io#in. Do you see this as correct?

      Best regards,

      posted in Duet Hardware and wiring
      Aitorundefined
      Aitor
    • Issues with Intermittent Stopping of the Z-Axis Motor

      Good morning @droftarts,

      I am experiencing issues with my new equipment using DUET3. The error generally occurs on the Z-axis, which has 3 independent motors, each connected to a different driver and with its respective endstops. Most of the time, it works correctly, but occasionally one of the motors (not always the same one) stops, causing the other two to descend, bending my print bed and preventing further movement.

      My NC endstops are two-wire: one connected to GND and the other to io#in. Here is my configuration:

      M584 X0.4 Y0.3:0.1 Z1.0:1.1:1.2 U0.5 E0.0:0.2                 ; Set drive mapping
      M574 Z2 S1 P"1.io2.in+1.io1.in+1.io0.in"                      ; Set endstop configuration
      

      As you can see, both the endstops and motors are connected to Duet3hc.

      My home Z configuration is as follows:

      ; homez.g
      ; call to home the Y-axis
      
      G91                                            ; Set to Relative Positioning
      G1 H1 Z{move.axes[2].max*2} F3000              ; Move
      G1 H2 Z-5 F6000                                ; Move
      G1 H1 Z{move.axes[2].max/2} F360               ; Move
      G90                                            ; Set to Absolute Positioning
      M400                                           ; Wait for current moves to finish
      

      I believe the configuration is correct since it works properly most of the time. However, as I’m experiencing this type of interference, could a pull-up or pull-down connection help? Additionally, I find it odd that on the Y-axis, which also has two independent motors (but connected to Duet6hc), I have not encountered this type of interference.

      I would appreciate any input you can provide.

      Best regards,

      posted in Duet Hardware and wiring
      Aitorundefined
      Aitor
    • RE: Possible object model error

      @droftarts said in Possible object model error:

      I'm sorry, but you'll have to ask @chrishamm why it works! I think it changes the data type to a string.

      ok 😂

      posted in Gcode meta commands
      Aitorundefined
      Aitor
    • RE: Possible object model error

      Good morning @droftarts,

      Your solution worked correctly, but I don't quite understand why. You didn't really add anything by including ^"", did you? What would that be adding here?

      Regarding spaces and tabs, I only use tabs, but something might have changed when translating or copying and pasting. My version of the code is in Spanish.

      And as for the Panel Due, I was kind of expecting that, but I thought there might be something I didn’t know. It wouldn't be the first time 😂 .

      Best regards,

      posted in Gcode meta commands
      Aitorundefined
      Aitor