Advanced Search

Thanks, and to confirm both tool setting and probing use "probe-input"?

If so, then I am considering using mux2 and utilizing M64 and M65 to select which digital input the tool setter and digital probe are connected to.

INCREMENTS = 1 mm, .5 in, ... - Defines the increments available for incremental jogs. The INCREMENTS can be used to override the default. The values can be decimal numbers (e.g., 0.1000) or fractional numbers (e.g., 1/16), optionally followed by a unit (cm, mm, um, inch, in or mil). If a unit is not specified the machine unit is assumed. Metric and imperial distances may be mixed: INCREMENTS = 1 inch, 1 mil, 1 cm, 1 mm, 1 um is a valid entry.

From the docs. I don't think you can change on the fly since it in the initialization file. I could be wrong, but you can mix and match to suit your needs. I rarely use any besides the fine feed. Could probably get away with 4 units, jog, mm, mm, in, in

Thanks.

I want to jog in inch increments when in G20, and have it change to mm increments when using G21. Similar to the DRO when it changes.

Yes you can have either in or mm to specify what is displayed.

the internal wifi card sits on the same pci bus as hard-drive and ethernet, so its driver can easily throw a wrench into the latency. I could probably just blacklist its driver in grub from loading, but i chose to completely remove it.

yes, sudo apt install r8168-dkms will work fine if you have your controller connected to the internet. I did not, so i used that command to build realtek 8168 driver on a virtual machine connected to the internet. (which in fact is just one file called r8168.ko) then i copied this file over to the controller using usb stick and manually replaced the default driver.

I don't plan to upgrade the kernel any time soon, so this approach works for me.

Boring example - but possible:

 

A high resolution encoder allows better velocity feedback
so you don't get "crunchy" feedback/motion at low speeds.

This is especially important with absolute encoders as you do
not get time stamps of count events like you can with normal
quadrature encoders.

Returning the encoder count to LinuxCNC if the drive has local
feedback is mainly useful if the feedback is from linear scales. 

Gents,

have a question on those famous cheapish AC servos form Aliexpress. Most of them are 17-bit absolute encoders. Correct me if i'm worng - this means it has 17-bit resolution per revolution? 1 / 131072. What for? is there any advantage of having such a big resolution per rev? i can imagine belt drive involed in drive - the slightest tension change in the belt under load will lead to position vs command discrepancy and force the motor to react. I think it will make the system nervous unless you set some parameter like dead band - but then why use such a big resolution?

Have anyone of you used those servos with Mesa cards and used encoder feedback from driver to Mesa?

Bit confused.

What material is the enclosure ?

Spindle model SW100
MAX power(kw) 3.3
MAX current(A) 13.1A
Maximum speed(RPM) 30000 
Maximum frequency(Hz) 1000hz
Nose HSK32E
Lubrication Grease
Weight(kg) 15
Cooling water or oil
Tool change type Pneumatic
Diameter 100mm shipping list
1pcs spindle motor
6pcs hsk32 er20 new chuck
6pcs hsk32 chuck holder 
1pcs solenoid vale
1PCS SPINDLE HOLDER
1PCS 4KW VFD input 220v single phase/ output 380v 3 phase 1000hz
1PCS BRAKING RESISTOR
10m PU tube 8mm
1PCS power conector
1PCS signal conector



www.ebay.com/itm/187284133495 

Hello,
Can the INCREMENTS be dynamic by G20 (in) or G21 (mm)?  

In my .ini / DISPLAY
INCREMENTS = JOG  .010in .001in .0001in
INCREMENTS = JOG  .100mm .010mm .001mm

Thanks

Thanks Rod, the external antenna was my next move.
I am in Sydney, any suggestion on model number that is known to work with LC2.9.4 ?

The Extender has been set up to use 2.4 GHz from the start.

The engineer in me wants to know why the failure in the cubicle.
I will do some more testing.
John.

Just so you know I run Ubuntu 10.04 on my CHNC lathe with no issues and no reason to upgrade. Oh and I'm running LinuxCNC 2.7.15.

Posting the actual error message would help.

JT

Linuxcnc only has one probe input.
You need to devise a way to check which probing method is in use in hal.
One simple way would be to set a digital input in  gcode before probing for tool height. 

You are two versions behind. The first step is to install master branch (2.10) to confirm the bug it still present. It may have been fixed.
If it has been fixed, it won't find its way back into an older version of Linuxcnc.

You should report the bug as an issue on Linuxcnc's GitHub page.