Posts made by rzi

@JuKu In my post I've added so the motors don't idle. At the end of the program I change it back to default.

@gloomyandy

Thanx for all the comment. I'm always amazing how fast things get sorted out when you guys kicks in.

It's generated by Fusion 360 and as it breakt with the gcode spec I just fix it in the post prosessor.

Best regards
Rickard

Hello

When using Fusion 360 and I copy an operation or setup, Fusion adds a (n) to the name of the operation. For example the copy of Contour1 is named Contour1 (2) and so on.

The gcode Fusion generates looks like:

(Contour1 (2))

This results in:

(Contour1 (2))
Error: Bad command: )

And that the line(s) right after are ignored.

I know that I could edit my post prosessor to fix this. But I guess that if this is a parsing issue is should be address in the firmware.

I'm running v3.3 (both firmware and dwc).

Best regards
Rickard

@chrishamm One caveat is that the machine will not pause until the buffer is empty.

@bmeun96 When you telnet to the controllet you get the same functionality as you do with the console in DWC. Connect to the duet with telnet and send some basic gcode to get it up and running. M114 return the current position for example. You have to dive into the wiki.

You can telnet to the duet and basically do what you want. Before the firmware had variables I made a bunch of. Net apps for various tasks.

@phaedrux You can still press a jog button.

This is actually a quite dangerous behaviour. I'm running 2 CNC machines, and on two occasions I've accidentally homed one machine while the other was running. The last time it could have ended quite bad due to the material setup. Now I'm using two different laptops to avoid any incidents. Maybe a checkbox in DWC or a M code to allow or disable manual gcode (or any other source) while the machine is procession a gcode file. With the exception of M112 etc.

@fma said in Using stepper currrent to detect a tool is loaded:

@rzi said in Using stepper currrent to detect a tool is loaded:

@dc42 CNC user here. Is it possible to add. I'm using two free drivers for a motorised vise. Would be super to have a mean of applying same force on each part I'm machining.

You could set the current of the vise motor to set the wanted force (torque). Then, just turn the motor until it stalls (using stallGuard feature, through a homing procedure, for example), and you should get roughly the same force each time.

Ah yes, going to test that. A much more straight forward approach. Thanx

@dc42 CNC user here. Is it possible to add. I'm using two free drivers for a motorised vise. Would be super to have a mean of applying same force on each part I'm machining.

I'm starting to get ERR_CONNECTION_TIMED_OUT from time to time. Wondering if it is time to get another one to replace it. I mean, it's living in a quite harsh environment and 2 years in a dirty workshop with high temp in the summer and damn cold in the winter may take its toll.

I'm able to connect to with over usb. Included is the M122 result.

Anything else I could check before I buy a replacement?

M122

=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet Ethernet 1.02 or later<LF>Board ID: 08DGM-917NK-F2MS4-7JKD2-3SN6K-TGU4G<LF>Used output buffers: 1 of 24 (9 max)<LF>=== RTOS ===<LF>Static ram: 25712<LF>Dynamic ram: 92904 of which 0 recycled<LF>Exception stack ram used: 424<LF>Never used ram: 12032<LF>Tasks: NETWORK(ready,652) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:13:26 ago, cause: power up<LF>Last software reset at 2020-12-03 08:07, reason: User, spinning module GCodes, available RAM 12064 bytes (slot 0)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 10<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 385.6ms, max retries 0<LF>MCU temperature: min 12.3, current 14.9, max 16.4<LF>Supply voltage: min 23.7, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0,[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]

Maybe a parameter to the M453 command to set if it should be affected by an error or not.

@Phaedrux It was a user error. I have two CNC machines. On my old machine I also control the dust extractor. with the M106 command autogenerated from my postprocessor. My new machine has nothing connected so it hits an error, naturally. Still, you pushed me in the the right direction by mentioning other config files, so thanx.

My config-override.g looks like this

; config-override.g file generated in response to M500 at 2020-10-15 12:01
; This is a system-generated file - do not edit
; Heater model parameters
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X496.10 Y227.62 Z63.78
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

On my Duet 3 MB6HC with Ffrmware: RepRapFirmware for Duet 3 MB6HC 3.1.1 (2020-05-19b2) I get Error: M106 : Fan 2 not found. I'm not sure where this originates from. Any config jedi that can take a quick look at my confg.g?

code_text


; Communication and general
M111 S0                            		; Debug off
M550 PDuetTest					; Machine name and Netbios name (can be anything you like)
M551 Preprap                   			; Machine password (used for FTP)
G90 ; Set absolute coordinates

M453 ; Put the machine into CNC Modes

*** Ethernet networking: The following lines are used for factory testing - PLEASE REMOVE THEM
;M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED		; MAC Address
M552 P192.168.3.14				; IP address
M554 P192.168.3.1				; Gateway
M553 P255.255.255.0				; Netmask

;*** End of factory test lines to be removed

M564 S1 H0

; Drives

M569 P0.0 S1                                 ; physical drive 0.0 goes forwards
M569 P0.1 S0                                 ; physical drive 0.1 goes forwards
M569 P0.2 S0                                 ; physical drive 0.2 goes forwards
M569 P0.3 S0                                 ; physical drive 0.3 goes forwards
M584 Z0 Y1:2 X3                     ; set drive mapping
M350 X4 Y4 Z4  I1                      ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z100.00            ; set steps per mm
M566 X500.00 Y500.00 Z12.00          ; set maximum instantaneous speed changes (mm/min)
M203 X4000.00 Y4000.00 Z2000.00      ; set maximum speeds (mm/min)
M201 X150.00 Y150.00 Z50.00          ; set accelerations (mm/s^2)
M906 X3500 Y3500 Z3500 I10                ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                      ; Set idle timeout





;*** Networking
M552 S1						; Turn network on

M555 P2						; Set output to look like Marlin
G21						; Work in millimetres
G90						; Send absolute coordinates...
M83						; ...but relative extruder moves




; Configure Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X596 Y810 Z94 S0 ; Set axis maxima



; Tool definitions
;M563 P0 S"Psycho"					; Define tool 0
;G10 P0 S0 R0					; Set tool 0 operating and standby temperatures
;*** If you have a single-nozzle build, comment the next 2 lines
;---M563 P1 D1 H2					; Define tool 1
;---G10 P1 S0 R0					; Set tool 1 operating and standby temperatures
;---M92 E80:80					; Set extruder steps per mm





T0						; select first hot end
; M117 Use https://configurator.reprapfirmware.org/ to set up your printer config

M574 X1 S1 P"!io7.in"
M574 Y1 S1 P"io6.in+io3.in"
M574 Z1 S1 P"io0.in"


M564 H0 						  ; Enable jog commands when not homed
M140 H-1						  ; Disable heated bed
M501    						  ; Load Stored Parameters 

Thanx! woprks very well now. This is what I ended up with.

M558 K0 P5 C"!io2.in" F100; create probe #1 for use with M585, active low

G38.2 X596 P0
G10 P2 L20 X0
G0 X{move.axes[0].userPosition-1}
G38.2 X0 P0
G0 X{move.axes[0].userPosition/2}
G10 P2 L20 X0


G38.2 y810 P0
G10 P2 L20 Y0
G0 Y{move.axes[0].userPosition-1}
G38.2 Y0 P0
G0 Y{move.axes[1].userPosition/2}
G10 P2 L20 Y0

I'm trying to make a hole probe macro with RRF 3.1.1

Is it possible to read current axis work position and divide it by 2?

The below does not work: move.axes[0].userPosition=move.axes[0].userPosition/2
but is it possible to achieve this in some other way?

::Rickard::

@dc42 I decided to use G38.2 and it was straight forward.

I'm having a similar issue. I got a Duet2 up and running on my old machine. And a Duet3 on my new machine and I want to run a similar set up. But I can't for my life get the xyz probe to work. Did you find the answer?

Best regards
Rickard