Advanced Search

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.
 

 So, just arrived the order for my retrofit .  I bought Mesa 7i76EU (i've done the configuration of Linuxcnc in a hold pc), than  Leadshine ELM1  , 3 of them 750w and one small 400w  and the drivers  EL6 for all the motors with different power supply. Im bit struggling because i can't connect the Motion Studio software to my driver for some tests idk if its the cable or other. I need to do a bit of wiring, and discover where to plug the brake of the motors , becausa i mounted all but i don't understand if i have to wire it with a another circuit with relays and a powersupply or if i can control it from the driver , didn't discovered it yet i need to check the schematics a few more times. If someone has any advices , or any experience with Leadshine motors and driver it's appreciated.
 

tommylight wrote:

Rod, he has huge excursions on both sides of the graph, those are not shown unless using --show, and those are the ones causing latency errors and link drop.

Of course there are excursions. That's because the histogram is only showing a window of 20 usec when the range is 70 usec over a 20 minute period. Whether you use --show or --sbins 1000 won't matter because either will show the full histogram. This is a case of how to lie with statistics with an inappropriate graph scale.

I get this error when the same tool is in the machine and I start the program. If I use another tool, the machine normally changes and measures the height of the tool.
anyone have any idea what the problem isOperator Error : Operator Error : M6 / change epilog : Python argument types in emccanon.CHANGE_TOOL ( ) did not match C ++ signature : CHANGE_TOOL ( int )


 

Hi Chris

I found a few things to fix in qtdragon(hd)
When saving the log to a file, an error is displayed, as in the screenshot.

The "clear status" button does not work.

In MacroTab Widget, the spacebar does not work.
In all others, "FACING", "hole enlarge", etc. pause works with the spacebar, but with MacroTab it does not.

There is such a topic forum.linuxcnc.org/38-general-linuxcnc-q...p-line-number#330090
Could you make it save the line number, e.g. in the log?

Hi Chris,
I will use hal pins to control LEDS status. no toggle.

This push button will probably be popular with qtvcp users since it will mimic certain pathpilot buttons. It will also reduce the amount of real state on screens. I can see it used for pause/resume, jog inc/cont ...