Advanced Search

Weird, so the ms300 has an "actual speed" display, however in a cut that is clearly bogging down 15-20%, it is claiming a fixed frequency dead on the programmed one. Seems not to be an accurate speed... OR the audio is deceptive.

ihavenofish wrote:

there is no way to add any form of encoder to the spindle.
 

I installed one of these encoders www.masso.com.au/product/optical-encoder/
But I still have not got anything to read it.

Thread mills are a nifty way to cut threads without encoders and rigid tapping.

Had a quick look at accelerometers. The one I saw had 3 analog outputs so you might be able to read the frequency in a realtime component. I have a routine that does a moving average in a comp. If the frequency exceeded the moving average it might be because of chatter!

Thanks Grotius


Yes the multi axis stuff is where it would be great to have a decent lookahead

And we would really appreciate it

PCW wrote:

The pncconf bug is just related to LinuxCNC version
but easily fixed by editing the hal file

The speed limit is likely because your 10000 steps/turn scale
would require very short step length and step space settings.

That is, to get to 5000 RPM at 10000 steps per turn, you need
833333 steps per second but your current step length and stepspace
settings (5 usec and 5 usec) only allow 100000 steps per second or
about 600 RPM.

Fixes: Reduce the drives steps/turn and or shorten the steplength
and stepspace parameters (noting the drives minimum timings
for these parameters and leaving adequate margins )

Fantastic then!  Thank you so much PCW!  This is great.  You are awesome and know and have lots of good skills.  I want to send you a gift or something about this if I could!

The pncconf bug is just related to LinuxCNC version
but easily fixed by editing the hal file

The speed limit is likely because your 10000 steps/turn scale
would require very short step length and step space settings.

That is, to get to 5000 RPM at 10000 steps per turn, you need
833333 steps per second but your current step length and stepspace
settings (5 usec and 5 usec) only allow 100000 steps per second or
about 600 RPM.

Fixes: Reduce the drives steps/turn and or shorten the steplength
and stepspace parameters (noting the drives minimum timings
for these parameters and leaving adequate margins )

if you go here-> github.com/LinuxCNC/linuxcnc/tree/master/lib/python/qtvcp/lib  ( /usr/lib/python/qtvcp/lib/touchoff_subprogram.py )
there it is ( touchoff_subprogram.py)
and i have not either have this path on my machine 

and i only updated linuxcnc, and it worked before whitout i had to changing anything to my .ini 

installed version of linuxcnc, on pc 

I built a little robot arm, and when it homes, the G53 locations have it facing 50 degrees backward, at the end of travel, etc.
In my ROUTINES folder there is a program firstrun.ngc that automatically loads because the INI file has the line...

Open_File = ROUTINES/firstrun.ngc

I home the robot and then click the cycle start (play) button.

I'm wondering if the postgui file or similar could have a command that basically says, "Home then run firstrun.ngc"
This file moves it to a PRESET-1 position then uses G10 L20 P0 to set the G54 home where I want it.

It would just be nice if I could hit HOME, have it go a typical home... then execute a file.

Is this possible??

Jerry

PCW wrote:

Not sure why you would get no steps but there are some issues:

net spindle-enable => [HMOT](CARD0).stepgen.04.enable

Should be:

net machine-is-on           =>  [HMOT](CARD0).stepgen.04.enable

Otherwise setting the spindle off results in an instant stop (this is fixed in newer versions of pncconf)

To debug why you are getting no spindle movement:

Enable the spindle and set its speed to 1/2 (2500RPM) in LinuxCNC and then
issue this command in a terminal:

halcmd show signal spin

and post the result here

Ok that’s awesome!  Its working in LinuxCNC when enabling the spindle!  But definitely not letting me take it up to the 5000 rated rpm lol.  Its only getting up to like 300rpm or something.  But this is great!  Im so glad for cool people like you that know these systems.  

Do you think because Im running the raspberyPI 4 version of LinuxCNC that theres some bugs like you mentioned with the net spindle-enable => [HMOT](CARD0).stepgen.04.enable Should be: net machine-is-on =>  [HMOT](CARD0).stepgen.04.enable? 

Even after changing that line in the hal file I still wasn’t able to test or get much further with the testing and calibration in of the spindle Pncconf.

This is great though I am inspired to learn more about this.  Thanks!

there is no way to add any form of encoder to the spindle.

When i analyse the audio track form my steel cutting video i can see the motor frequency quite clearly, distinct from the "teeth" hitting frequency (which is stronger because its louder).

Seems worth trying. Accelerometer vs piezo sensor, etc.

Exactly, id use an induction sensor. something like this might work. LJ18A3-8-Z/BX

They make bigger ones and smaller ones. The bigger they are the longer the detection distance.

Those are cheap ones, they make nice industrial ones as well.

Well if the vfds you can find are open loop why not single point encoder. You could use a sensor like the one above, they make some that work off reflective tape as well. (Check out laser tachometers for the idea)

Interesting idea on the chatter vs speed. Not sure how easy it would translate to rpm. Easy way to test though......just don't enter the wrong flute number

ooh, i wonder if the chatter control sensor can measure speed. 1000hz x 3 flute will make a distinct 3khz vibration. hmmmm.

Not sure why you would get no steps but there are some issues:

net spindle-enable => [HMOT](CARD0).stepgen.04.enable

Should be:

net machine-is-on           =>  [HMOT](CARD0).stepgen.04.enable

Otherwise setting the spindle off results in an instant stop (this is fixed in newer versions of pncconf)

To debug why you are getting no spindle movement:

Enable the spindle and set its speed to 1/2 (2500RPM) in LinuxCNC and then
issue this command in a terminal:

halcmd show signal spin

and post the result here

 ok sorry to be a pain but i tried installing this again, went through the tutorial and followed the steps in the video to install the ng file m130 and the easyicons.tff in the newly created fonts folder, i already have a pyvcp xml file that is used for the spindle rs485 control pyvcp panel called vfd.xml, so instead of adding the probe_panel.xml i edited my vfd.xml with the easy probe tab as per the manual, and in the (DISPLAY) section of my .ini file, i put vfd.xml instead of probe_panel.xml, i added the required entries under the (RS274NGC) and (HAL) sections

manuals instructed entries

[RS274NGC]
SUBROUTINE_PATH = macros
ON_ABORT_COMMAND = O <on_abort> call
FEATURES = 12
RETAIN_G43 = 0
INI_VARS = 1
HAL_PIN_VARS = 1

to my [RS274NGC] section

[RS274NGC]
PARAMETER_FILE = linuxcnc.var
SUBROUTINE_PATH = macros
REMAP=M6 modalgroup=6 ngc=tool-change
REMAP=M600 modalgroup=6 ngc=tool-job-begin
SUBROUTINE_PATH = macros
ON_ABORT_COMMAND = O <on_abort> call
FEATURES = 12
RETAIN_G43 = 0
INI_VARS = 1
HAL_PIN_VARS = 1

manuals instructed entries for HAL section

[HAL]
TWOPASS = on
HALFILE = Probe_preload.hal
POSTGUI_HALFILE = Probe_postgui.hal

to my (HAL) section

[HAL]
HALFILE = PRINTNC.hal
HALFILE = custom.hal
POSTGUI_HALFILE = vfd.hal
POSTGUI_HALFILE = custom_postgui.hal
POSTGUI_HALFILE = postgui_call_list.hal
TWOPASS = on
HALFILE = Probe_preload.hal
POSTGUI_HALFILE = custom_postgui.hal

and the (PROBE) section to my .ini file, in the manual,

the manual also says

*Note: When TWOPASS is activated, realtime components can not only be loaded in the main hal file but in any other hal file,
too. This allows us to offer a hal file with all required realtime components for [easy]probe so there is no need for you to
edit your machine hal file.*

also the manual says

*Note: LinuxCNC allows not more than one postgui hal file called from the ini file. If you already have a postgui hal file,
copy all content from the Probe_postgui.hal to your postgui.hal.*
so i dont use the Probe_postgui.hal file from the manual, i add the information to my custom_postgui.hal file.

now when i load linuxcnc it says classicladder couldnt load, and the only way to get it to run is commenting out the #TWOPASS = on ,in the hal section as i copy and pasted above , and when i do none of the buttons work on the probe tab, but classicladder loads, and my spindle panel works fine  , ive tried moving around the hal file entries in the hal section but had no luck, i have uploaded my machine config files, as i have an m6 remap for manual toolchanges and classicladder to control my spindle with an rs485 adapter, and tried with the 1.2 easy probe, and now struggling with this version

computer: dell optiplex 7010 business desktop
"Dell Optiplex 7010 Business Desktop Computer (Intel Quad Core i5-3470 3.2GHz, 16GB RAM, 2TB HDD, USB 3.0, DVDRW,"

Now flashed with linuxcnc 2.7 which went well

I need a parallel port to use with my sherline lathe but am gettting worried now because every thread about this seems to have been a dead end - I am using the startech card "StarTech.com 1-Port Parallel PCIe Card - PCI Express DB25 LPT Printer Card"

I added all of the necessary files per the instructions and installed all of the packages which went well. However, when I navigate to the folder in the terminal and type in "make" I get the following error: Im sure other errors will arise...

/home/Desktop/ttt/ax99100_sp.c: In function ‘serial99100_request_port’:
/home/Desktop/ttt/ax99100_sp.c:2282:6: error: ‘mem_size’ undeclared (first use in this function)
/home/Desktop/ttt/ax99100_sp.c:2282:6: note: each undeclared identifier is reported only once for each function it appears in
/home/Desktop/ttt/ax99100_sp.c:2283:3: error: ‘ret’ undeclared (first use in this function)
/home/Desktop/ttt/ax99100_sp.c:2296:1: warning: control reaches end of non-void function [-Wreturn-type]
make[4]: *** [/home/Desktop/ttt/ax99100_sp.o] Error 1
make[3]: *** [_module_/home/Desktop/ttt] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.4-9-rtai-686-pae'
make: *** [default] Error 2
XXXXX@mglinux:~/Desktop/ttt$


When I go to the associated file ax99100_sp.c and look into those variables, this is the section of the code: I am confused because it does seem like the variable is properly defined...any suggestions?

//Helper function to get the necessary kernel resources for the port
static int serial99100_request_port(struct uart_port *port)
{
struct uart_99100_port *up = &serial99100_ports[port->line];
#if defined(__x86_64__) || defined(__amd64__)
int ret = 0,size=8,mem_size=4096;
#endif
#if defined(__arm__) || defined(__aarch64__)
int ret = 0,mem_size=4096;
#endif
//todo:the mem_size and the mem2_size are not yet known properly
DEBUG("In %s

---

START\n",__FUNCTION__);
#if defined(__x86_64__) || defined(__amd64__)
if(!request_region(up->port.iobase, size, "AX99100"))
return -EBUSY;
#endif
if(!request_mem_region(up->port.mapbase, mem_size, "AX99100")){
ret = -EBUSY;
goto release;
}
DEBUG("In %s

---

END\n",__FUNCTION__);
return ret;

Thanks

The gs20 is the same as the ms300. I'm using a GS10 on this spindle right now.
Problem is they are not fast enough. I need 1000hz. I can find very few 1000hz drives at all (nuclear proliferation sanctions) and the ones I do find are only V/F - like the delta MS300HS.

On the atc mag sensors. that gave me a thought. i just need 2 sensors with a trigger at each station. one trigger is "on station", and the other senses the shaft somehow below the shank. would need to have 5-10mm range to not get hit by anything.