Advanced Search

Machine partially rebuilt.
Did wind up finding that one of the linear blocks was damaged. order some new ones. I lapped and realigned everything, so things should be more precise now too - better than 0.001" over the whole work area pre compensation. Hopefully by next weekend its all running again with the new spindle and vacuum. woo. 

 

I am in the middle of building an EtherCAT system using a Beckhoff EK1100 and would like to use the el6021 module to drive my spindle VFD with RS485.
I've searched the forum and seen it mentioned briefly a couple times but I can't find where anyone has got a driver working for it?
How hard would that be to accomplish?

Hi All
I have been trying to set the smart serial node addresses in stmbl config so I can use multiple stmbl modules with an 7i96s.
Could anyone enlighten me as to how to set node addresses in the stmbl?######## software info ########STMBL v0.9.18 v0.9.18-184-g9590cb33Branch masterCompiled 2024-12-28 15:41:15 by scott on scott-Ubuntu-iMacGCC 10.3.1 20210621 (release)newlib 3.3.0CMSIS 4.30StdPeriph 1.6.0size: 340888 crc:65008998######## Bootloader info ########STMBL-Bootloader v0.9.18 v0.9.18-184-g9590cb33######## HV info ########STMBL-hv-f303 v0.9.18 v0.9.18-184-g9590cb33hv start:0x801024c ,size:0x1a54c ,end0x802a798

Many thanks in advance.
Dean

Lcvette wrote:

its been a while since i tested this, and i currently have a large project pulled that i don't want to exist until finished as we are preparing a release for qtpyvcp and probe basic.

based on spumco's response above does this mean that a remap for 200+ mcodes is required? i think spumco is running probe basic also if memory serves so his experience should be the same as the pb sim.
 

Lcvette -

I'm running PB on my mill, and will use PB on the lathe when it's mechanically done.

My suggestion is to use remap for everything when you have a bunch of custom M-codes.  In fact, I may change my M100-M103 to m100.ngc remaps.

Reason being is that if you have some m-codes as User Defined Commands, and some as remaps... they're going to be in different folders and 'look' different to anyone poking around in the folders or trying to edit them.

I think for clarity it'd be better to have everything in one place, in the same basic format.  And once you've got the remap for one m-code, it's easy enough to paste a bunch more in the INI file.

Using remaps also lets you organize the m-code numbers somewhat logically without running out of headroom.  In my case, since I've got about 3 different 'mist' functions and 3 or 4 different pneumatic cyls/grippers planned, I could use M700-M702 for the mist, and maybe M900-M904 for the automation stuff.

You could also number all the Probe Basic probing routines as M200-Mnn instead of the long text names.

If your list gets long enough, you can also put a "MCODES.txt" file in the subroutines folder with a (hopefully current) list of what they all do.

muestra tus archivos de configuración para poder ayudarte. saludos

Oh here we go, something that someone thinks else that is foreign to you, you allude to some sort of mental issues.......confirmation umber 2, thank you once again.

You really are the archetypal NPC.

Thanks for the guidance. I implemented the following code and it seems to work. The logic is that the laser has to be 0.375" of less (relative) above the surface. AND the laser engraver tool number (8) must be selected. And the motion input (triggered by a M62 P21 or M64 P21) must be true.

Currently I program z=0 as the top of the work surface. This code won't work if I program z=0 as the spoilboard or somewhere else. I guess I could use another M code to set a laser safety height or something. We'll see how this works first.

-Jim

 # inhibit laser engraver when at unsafe height (relative)
addf comp.0 servo-thread
setp comp.0.in1 0.375 # okay to have engraver on below this (relative) z height
setp comp.0.hyst 0.005 # hysteresis
net engraver-height-current comp.0.in0 <= halui.axis.z.pos-relative

# engraver tool (T8) must be the active tool and height must be safe
addf conv-u32-float.0 servo-thread
net tool_number_u32 <= halui.tool.number => conv-u32-float.0.in
net tool_number_float <= conv-u32-float.0.out

addf comp.1 servo-thread
setp comp.1.in0 8 # engraver tool number
setp comp.1.hyst 0.0001 # floating point is never equal
net tool_number_float => comp.1.in1

addf and2.3 servo-thread
net engrave-safe-height <= comp.0.out => and2.3.in0
net engrave-safe-selected <= motion.digital-out-21 => and2.3.in1
net engrave-signal <= and2.3.out

# make sure comp.1.equal and engrave_signal are both true, if so we turn on optimat_o_laser_engraver_pwm
addf and2.4 servo-thread
net engrave-signal => and2.4.in0
net engrave-tool-match => comp.1.equal => and2.4.in1
net engrave_pwm <= optimat_o_laser_engraver_pwm <= and2.4.out

 

I think maybe you need to take some time off and work some things out. That's beyond bizarre.

Hello,
I am trying to accomplish index homing on Delta B3 EtherCAT drives. Index signal is not available within SDOs, so I think the only way is to use servo internal homing procedure. I know there is a component for cia402 external homing by rodw. I am gathering info, so any input is appreciated!
i am using linuxcnc-ethercat deasda:

github.com/linuxcnc-ethercat/linuxcnc-ethercat

thanks