Posts made by chernogorsky

undefined

To anyone like me stacked with SBC and 3.5
my way of resotoring stable version (after changing /etc/apt. ... to stable)

sudo apt install duetcontrolserver/stable duetpimanagementplugin/stable duetpluginservice/stable duetsd/stable duetsoftwareframework/stable duettools/stable duetwebcontrol/stable duetwebserver/stable reprapfirmware/stable duetruntime/stable

undefined

@dc42
I have multiple Y axis, leveled by multiple end-stops
but Z is single axis

It's a CNC mode

undefined

@dc42
#1 - I had multiple lines like
if exists(param.X)
set var.dirX = param.X
and they works before 3.5b1

in 3.5b1 I have to switch to
if {exists(param.X)}
set var.dirX = param.X

I remeber that it was mentioned somethere, but it was not emphisized (ASFAIK) as breaking changes in 3.5b1

undefined

Few issues on CNC / d3-6xd / SBC
Switched back to 3.4.5 after a broken bit (

it starts enforcing {} rules in IF condition (I know that its in doc somethere)
38.2 38.3 return non zero result quite often. Wich may lead to broken probe. (Im using same probing script for few months on 3.4.5 without any false positive. Only overprotective movement saved me that time)
M291 S2 in a programm does not continue by M292 P0/M292/pressing OK. After the widown closed it still in processing state with no window/reaction to M292. M292 P0/M292/pressing OK works fine with M291 S3.
Unknown movement issue. On a test milling it hangs on some Z, one time it just hangs there, one times it hangs on Z-3.708 (I see that number in GUI/object model (pendant) ) and continue to press downards with slow pace (probably with the same of the last command) without any update to GUI/object model, nor getting next command in line (gcode attached). Was stopped by pause button (GUI).

Last one is the most disturbing

Gcode: VertAluDrill.cnc.gcode

undefined

Create a separate ticket. Movement issue + some minors

undefined

Declimer: its not quite Question / need for help topic. Mostly its for sharing info

Im in the middle of conversion of my cnc into ATC cnc,
and probing is one of the feature I start the ATC at the first place

Im using "JINNI Post for RepRap w/Tool Change & Backlash Compensator" post processor from https://github.com/BruceRoyce/UltimateRepRapPost as a start point, and modify it to my need

In additional to some general changes, like:

start script
end script
tool config script

Im currently working on probing.
Idea is the following: use a "standard" RENISHAW gcoding / post processor parts and than workaround it through custom Gcodes + scripts

https://quagmirerepair.com/files/mazak/Spindle_Probe_Manual.pdf

example:

F360 probing-z
would be converted to

G54
G0 X0 Y0
G0 Z25
G17
;CYCLETYPE PROBING-Z
;CYCLETYPE PROBING-Z A1 NEGATIVEA2 NEGATIVE PC 4
G65 P9810 C3 Z1.5 F300
G65 P9811 A3 Z-2.5 Q10 S1
G80
G0 X0 Y0 Z25

Then, I'll create
g65.g custom gcode, which would recognize
P9810 as a safe move (something like /macros/probing/p9810.g)
and
P9811 as a signle surface probing

With that approach hopfully we would be able to reuse all /macros/probing/p*

Current points I have to keep in mind:

speed of executing macros from macros (i find some unpredicted delays 1-2 seconds from time to time)
needs of m400 if I want to use object model position reading
no array (hopefully till 3.5) to store all the tool data. workarounded by stored_on_flash_array

Any ideas/thoughts would be appriciated

undefined

@Jengland I do have it
I use the following method:

I set the machine zero with setter and spindle without the tool / collet / nut
I install the tool
I test the tool and set tool height

If I change the tool, I just redo p2 and p3

It does require additional step on the machine enable (p1), but It happend that my setter is +- 0.01, and Z endstop about +- 0.1-0.3

My script

M208 Z8 S1

G53 G90 G0 X321.0 Y0.0

if !exists(global.MGlobalsLoaded)
	M98 P"/macros/Measuring/globals.g"
	
;M558 P1 C"io7.in" H23.258 F{global.MSpeedFast,global.MSpeedLow}	

M558 F{global.MSpeedFast} K1

M300 S300 P1000
if state.currentTool = -1
    M291 S0 T5 P"Probing the spindle zero height"
else
	if global.HSpindle <= -9999
		abort S"Please set the spindle zero first"
	M291 S0 T5 P"Probing the tool " ^ state.currentTool ^" offset"


M558 F{global.MSpeedFast} K1

G30 S-1 K1
G53 G1 Z{move.axes[2].machinePosition+2} H4

M558 F{global.MSpeedLow} K1
G30 S-1 K1


if state.currentTool = -1
  G92 Z{sensors.probes[1].diveHeight}  
  set global.HSpindle = sensors.probes[1].diveHeight
  set global.MResultZ = sensors.probes[1].diveHeight
  M208 Z30 S1
else
	M400
	echo "Probe triggered at Z:" ^ move.axes[2].machinePosition ^" Sensor height: " ^ sensors.probes[1].diveHeight
	var ToolLen = move.axes[2].machinePosition - sensors.probes[1].diveHeight
	set global.MResultZ = - var.ToolLen
	M98 P"/sys/tool_set.g" T{state.currentTool} O{global.MResultZ}
	
	; Set soft limit to 0 plane
	M208 Z{var.ToolLen} S1
	


M558 F{global.MSpeedFast} K1
G53 G1 Z{move.axes[2].max - 10} H4

undefined

Hi,
I have a complex (CNC) wiring with multiple layers of E-Stops
And I have a question, does duet3 (6xd, 3hc) can be set up as an NC relay in E-Stop line
I thought of opto out, but not sure if Im in a right direction

undefined

I have not seen any issue with a printer (and ASFAIK it utilizes g2/3 at some points)
but as you can see from the pictures with CNC it looks different

It may be still post processor issue, but g2/g3 code looks ok-ish

undefined

@3dpmicro Hi, not shure I follow
I attached c-inner_failed (which is with arc, g2/g3) and c-inner (which is g0/g1 only)

undefined

Hi,
I found some curios bug if Im using G3 operation with f360 + universal pp 1.5 + enabled arc/circle

It creates oval (X axis is the most affected one)

The greater cutting feed the worse the "circle". That one on a picture if I remember correctly was made with 2400 mm/min

And here the result when I disabled arc movements (same feed rate)

c-inner_failed.gcode c-inner.gcode

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6XD FIRMWARE_VERSION: 3.4.1 ELECTRONICS: Duet 3 MB6XD v0.1 FIRMWARE_DATE: 2022-06-01 21:10:05

undefined

@t3p3tony syntax, im talking about syntax
the idea is (same as it in programming)
you creating your own template system, you are using standard
you creating your own variant of the language, you are using same as a bigger project (so you can grab parts from there without modification)

undefined

@catalin_ro Im using 6xd, so no direct drivers
direct one - I had many issues with d2, with d3 not so much, but I rarely push the limits

overheating - not sure its an issue - used to run d3 in 45-50 outside

rest - donno,
I just foresee that due to limited numbers of users that env would not be able to grow naturally (not only create something required, but also support it for prolonging period of time)

example: I can create (and I did) cnc pendant, will probably code it till some finished module
but in case I switch to another project it most likely would be abandoned

same for all "not critical / not mainstream" parts

With 3d its easier (its more general in terms), but still linear adv, ....

at the moment it not limit me a lot, but will see how its go

undefined

I have issue with G3. it looks like something is wrong within the duet itself, it looks good in gcode viewers, but created an oval

will check and probably open a d3 issue
at the moment I back to thousands of segments

undefined

So I'll not be able to reuse code for other env, we have to create and SUPPORT owr own

undefined

@droftarts Im not talking about clear gcode
Im talking about gcode flavor

Example:
I cant use code post processed / designed for linuxcnc
I have to use separate post processor (which work quite good for f360 btw)

so if i want using something but f360, or use existed code for lcnc / mach3 i have to spend tremendos of time each time, so in long term it not worth it (except for me personally)

undefined

@chimaeragh Yes,
Im using it, with few modification (have probably made merger request if it'll be interested)
that's where I find that we are probably heading the wrong way

examples:

I want using the probe (fusion360), ok - let say, that I'll be able to write/debug code for it myown (support - probably no)
I want using linuxcnc addon for probes (they have like 50 scripts (tested/and updated) for probing,
but different gcode flavor, so in order to make it work I need to translate it line by line
I wanna try other CAM,

What Im saying is - duet3d cnc community is not that huge (at least now and in a few years) to create/support all that may be required and avaiable on a open-source-like enviroments

If (IHMO) d3 uses some of the more spreaded gcode flavor that can help spread the board itself

P.S. I myself probably be able to code it myself
P.P.S. or I'd realize that I spend more time coding (something needed me only) than cncing

undefined

Hi,
Im start using d3 as cnc controller
Works just great
Im using some post-processor for fusion360 + some modification in it, but I think its no a road should be followed:

d3 has not enough cnc folowers (and would not have enough in a few years) compare to march3 or linuxcnc
as a result of p1 - it would be quite a limited support for post processors - probably only the very basic features for major cam only
if I try moving/port something from lcnc/m3 eviroment it would be quite hard, since I would be needed to emulate the difference in first place

That said, I think it worths considuring moving cnc gcode style toward lcnc / m3 or any other standard (tormach ?)

P.S. Im not even close to be named as a cnc newbe, im just walking around cnc ). I do IT system design for a living, and that exact part I force my teams to avoid in my projects )

undefined

@t3p3tony Thank you
and following our conversation the other day
pendant video

Next newbe question would be how to set it as a plugin

undefined

Hi,
Quite a newbe to Python DSF. may you please point me to the right direction
I'd like to be able to send multiple commands to Duet through python

Thanks