Advanced Search

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 ...

You may be able to rework it to run on single phase. I haven't done it myself but i've heard reports:
www.practicalmachinist.com/forum/threads...han-expected.429807/

We have an old 3016 with the 88HS control in our tool room that we run from time to time. I find the built in control pretty ok and there is a lot of support out there for spare parts still. We use one of these: www.calmotion.com/product-page/lanusb-fad
to drip feed large programs and load smaller programs from USB

Yessir, my experiments concur.
In fact a P of 0.45 and an I of .0015 works quite well for this system.

The slowest speeds are quite a bit faster than commanded, but 1000rpm and above are fine.
This tripping of the relay is I think self inflicted, I don't believe hopping from a very high speed to a very slow one, is something you'd do in the real world without stopping the spindle to change a tool.
Next test is to see if I can orientate the spindle and even execute a tapping cycle.

Very exciting. Thanks for your guidance as ever.

Test fit of push buttons and choosing imbedded keyboard.
note that buttons are not secured in place yet. 

ist immer noch ein Call
schreib mich mal mit call ät darc.de an
dann schick ich dir die Dateien

Also:

eusurplus.com/index.php?route=product/search&search=7i84u
 

D typically makes no sense in a velocity--> velocity loop

Important ones are 
FF0 == 1

P and I