Advanced Search

Ok, it works if I add it to CONFIG_FOLDER/qtvcp/screen/qtdragon_hd/ as qtdragon_hd_handler.py

Thank you

Same,
Do I need add it somethere to be loaded (like include qtdragon_handler)

> Add this to CONFIG_FOLDER/qtvcp/screen/qtdragon/
> name it qtdragon_handler.py
 

I do not have an account there, maybe i can convince myself to open one.

Not sure if I need the tilted workpiece plane

You tell me...

Basically G68.x is similar to G52 in the sense that you create a new WCS from the currently active offset. G68.x has the added benefit that lets the operator define how the XY-plane of the new WCS is oriented in space.


I'm sure a sales rep would tell you that you definitely need it!

But since I really have no clue about 5axis machining you may want to let other people explain:

Here is a demo for tilted work plane on a Fanuc controller for a 5axis table-table rotation kinematic:


This guy rambles on a bit:


also here:
www.linkedin.com/pulse/fanuc-g682-5-axis...planes-tim-markoski/

Hello,
i just set upo mey new pc with linuxcnc. Everything seems to work correctlly, except the keyboard. From time to time suddenly the keybiadr does not longer work. I can still use the mouse to navigate, this problem ist not only under linuxcnc itself, it affects also all other applications under linux. When i reboot everything is fine again for a while. I already tested multiple keyboards and usb ports.
i could not reproduce the problem, it coms when it has the desire for it.

to be sure its not because of the power supplies for the stepper drivers, i switched them comletely off

perhaps its a problem with the rt kernel, but i could not found something about that there are only people who have problem with the keyboard under linuxcnc but the other applications are noit effected

my configuration: microatx board with intel i5, 16GB ram, onboard graphics pcix parallel portcard und parallel bob with 4 attached axis - latest linuxcnc iso image is used

Georg

Hi scotta,
thanks for Your pointer to MCUXpresso. I don't have Windows and I don't like the NDA stuff NXP is requesting. Instead I tried the DABLink with the drag-n-drop method and the command file "erase.act" which successfully erased my boards!
Now let's try the new firmware...

regards, hanskuster

I also suspect this limitation becomes a mayor issue if you want to do 5 axis simultaneous machining. I currently have no ambitions in that direction though.

Less so than you might think. LinuxCNC had only the 1-move-lookahead TP for decades and few people noticed a problem. 
It started to be an issue mainly on very fast routers and plasma cutters, and when CAM started to be more readily available (and, to an extent, when it started being used by novice CNC-ers who assume that the smallest possible path length mush be highest resolution and therefore the best. 

If you work out what the minimum segment length is to fulfil the requirement, it is gnerally pretty short, though this depends in the feed rate and machine acceleration limits. 

Under-specifying the acceleration limit in the INI is a common cause of trouble in this regard. 

If you remember school physics: v^2 = u^2 - 2as. 

Or, the minimum segment length, s is in the order of: s = v^2/2a. 

My (slow, old) mill with a 1000rpm spindle runs typically at around 100mm/min and the INI has:
MAX_VELOCITY =       45
MAX_ACCELERATION =   200
These are units of mm and seconds. 

So, if I am running at 100mm/_min_ that is 1.7 mm/sec. 
So the minimum segment length is 7 _microns_ (or 0.3 thousandths of an inch)

Most commercial metal-working machines will have servos sized to give similar dynamic properties. 

But many home-build routers are geared for high speed and low acceleration, and it is there that problems can arise. Especially as woodworking is a lot more sensitive to reductions in feedrate, as it can lead to burning of the wood. It's not ideal on metal, either, but the results are increased cutter wear and not generally visible on the workpiece. 
 

Danke für den Link da muss ich mich mal reinarbeiten. Als erstes werde ich mal die Verbindungen tauschen, für die Mesa hab ich tatsächlich einen Realtec RTL8111, der könnte da Probleme machen.
Ja ich habe ein MPG XHC-WHB USB Handrad. Das funktioniert auch.
 

2) Esprimo Q956 Mini PC with i5: poor latency, good ping - > unusable

How poor? Mesa cards are fairly tolerant of realtime latency, up to 100,000ns or so. 

This sounds like a realtime or ethernet latency problem.

What are your latency test results? And your ethernet ping times?

Can you create an issue for these so that they don't get lost?

github.com/LinuxCNC/linuxcnc/issues

1) Does GPIO 34 actually trigger the gear change?
2) Are you being consistent in your units? Spindle speeds can be in rev-per-minute or revs-per-second.
3) You didn't include the INI file, does [SPINDLE_0]GEAR_LOW_MAX_SPEED exist, with a sensible number in it?

I think that this is probably a feature of the UI that you are using, rathe than a base LinuxCNC feature.

One use would be to move the spindle to a more convenient place to perform the manual toolchange.

I think you can ignore those warnings. They are caused by a mistake I made fixing a merge conflict.

I think that your real problem is that your INI filie references a HAL file which can't be found.

Yes just like the YouTube video.

Not sure if I need the tilted workpiece plane

You tell me...

It definitely looks really cool though