Advanced Search

More of a general Linux question but it's probably been a decade since I logged into any of my old Linux forums lol. 
My CNC machine is on wheels and my monitor sits on top of a file cabinet next to it. I broke my last monitor absentmindedly pulling the machine out to work on it and have almost done the same with my new monitor. 
My new monitor has HDMI or VGA. 
My computer internal GPU only has displayport. 

I bought an HDMI wireless adapter I would love to try to get working but it hasn't gone so well so far. 
I plugged it into my displayport to HDMI adapter cable but the internal GPU doesn't seem to see it and won't send signal to it. 
I bought an active displayport to HDMI adapter hoping that would fix it but no luck. 
I also have an old quadro 600 card that has a displayport and DVI. I haven't tried a DVI to HDMI yet. I might have an adapter laying around somewhere. 
With the HDMI wireless adapter plugged into the quadro with the active displayport to HDMI adapter it displays the boot manager to boot up but deactivates before it gets to the login screen. 

Now I'm trying to figure out the best way to move forward. I think I could probably figure it out on my own but I think it could take hours more. Possible options I think might be worth persuing. 


1. It seems like there is a way to force a signal to be sent to a displayport but it seems like the displayport still needs to detect something being there before it registers as a device to have that command work? 

2. The built in displayport doesn't display anything on startup with the HDMI wireless adapter into the displayport adapter, into the computer. 
The quadro card does but goes off before the login screen. 
Maybe it would work to force the signal to this port instead?
A semi related topic I found online suggested installing the Nvidia drivers. This is getting into a much bigger box of worms than I had hoped for my little Linux machine but if this would likely solve the problem I would do it. 

3. I think I can find a cheap graphics card online with an HDMI port. If this would be a better option and work out of the box, even just if it saved me needing to mess with installing proprietary drivers or anything I would be open to that as long as I was confident it would work. But if it puts me in the same situation as I have with the Quadro then I might as well just go with that. 

4. if there is an option, a wireless adapter, or anything else that would work better than anyone knows of let me know. 
If it's any help this is the one I currently have. 
www.amazon.com/dp/B0FVXVG3ND?ref=ppx_yo2ov_dt_b_fed_asin_title
It doesn't look like displayport wireless transmitters are really a thing which is kind of interesting. 

 

grandixximo wrote:

For example YangYang is now looking at stopping to destination with vel0 acc0 jerk0 all at the same time at the ends of an arc segment, in the servo-thread we compute next position forward in time, they keep adding up, and this leads to numerical errors, which make the jerk overshoot near the final destination, then you have to clamp down the error smoothly to arrive at destination, within current architecture you have to overshoot, you have to readjust, he has tried multiple avenues to fix this, nothing so far has worked.
How commercial TP fix this? they don't plan forward, they plan from destination backwards at each time increment with dedicated hardware, and deal with feed override changes by re-planning to a different time destination.
You can probably understand how different LinuxCNC is from commercial controllers, they practically work in the complete opposite way...
Many of the issues we are faced with, have similar kind of solutions in the commercial space, they just don't do it how LinuxCNC does it.
When I wrote "we are limited to what we can do", I intended it in the scope of implementing jerk limiting within the current TP, with tangential jerk limiting code that is being enabled with planner_type 1, and some blending and look-ahead improvements, to try and stick to jerk limited motion, without introducing any non-realtime code in servo-thread, sure a complete rewrite you can do whatever, but that is not something you do overnight. And we are also limited by physics, you can't have high-speed accuracy smoothness all at the same time, physics just don't allow this. I understand most here would sacrifice speed, but there is a camp that would like to squeeze out a bit more speed if possible sacrificing some accuracy within what's allowed by the gcode.




 

You'll need to change the TP. I'm not offering a $3000 cnc as a bounty for something you can vibe code overnight

Speaking of, a little bird told me that someone with the skills should request tormachs latest source....

DO IT NOW!

Hi Hakan,

If LinuxCNC always receives the position feedback ~2 servo cycles late, can I simply “ignore” this by increasing the following-error limits (FERROR / MIN_FERROR), or does this latency actually affect the LinuxCNC motion planner/trajectory execution?

In other words:
Does LinuxCNC only use the feedback for monitoring/fault detection (so the part accuracy is still fine as long as the drive itself tracks well and has near-zero internal following error)?

Or does LinuxCNC actively “react” to the delayed feedback (e.g. by slowing down, modifying the commanded motion, degrading contour accuracy), meaning I cannot machine precise parts even if the servo drive is perfectly tuned?

So the decisive question for me is:
Can I still mill accurate parts with this inherent 2-cycle EtherCAT feedback lag, as long as the servo drive is properly tuned and its internal following error stays low — or does the lag directly reduce machining accuracy?

Thanks a lot for clarifying this.

For example YangYang is now looking at stopping to destination with vel0 acc0 jerk0 all at the same time at the ends of an arc segment, in the servo-thread we compute next position forward in time, they keep adding up, and this leads to numerical errors, which make the jerk overshoot near the final destination, then you have to clamp down the error smoothly to arrive at destination, within current architecture you have to overshoot, you have to readjust, he has tried multiple avenues to fix this, nothing so far has worked.
How commercial TP fix this? they don't plan forward, they plan from destination backwards at each time increment with dedicated hardware, and deal with feed override changes by re-planning to a different time destination.
You can probably understand how different LinuxCNC is from commercial controllers, they practically work in the complete opposite way...
Many of the issues we are faced with, have similar kind of solutions in the commercial space, they just don't do it how LinuxCNC does it.
When I wrote "we are limited to what we can do", I intended it in the scope of implementing jerk limiting within the current TP, with tangential jerk limiting code that is being enabled with planner_type 1, and some blending and look-ahead improvements, to try and stick to jerk limited motion, without introducing any non-realtime code in servo-thread, sure a complete rewrite you can do whatever, but that is not something you do overnight. And we are also limited by physics, you can't have high-speed accuracy smoothness all at the same time, physics just don't allow this. I understand most here would sacrifice speed, but there is a camp that would like to squeeze out a bit more speed if possible sacrificing some accuracy within what's allowed by the gcode.

Ok, found it, this should be it
forum.linuxcnc.org/27-driver-boards/3497...iers?start=90#337507

Hakan wrote:

Position feedback from a drive is always two servo cycles behind.
 

Thank you pointing this out, somehow everyone keeps skipping this.
Not a deal breaker, but nice to know.

It's possible some percent of emails get put in the spam bucket
but losing many in a row would not be common.

Who did you email?



 

Ferrite beads on the motor wires near the drive are usually a must, and having an LC filter on the mains side never hurts.

They (PCW) always replies here, and almost always inside of a single day, no idea about e-mails.
What is your exact issue?

You hit the weak point in linuxcnc Ethercat.
Position feedback from a drive is always two servo cycles behind.
Following error due to this is at least axis speed x 2 x servo cycle time.
You can easily verify this.
 

In a terminal:Click on "glxgears" several times (5-10), leave it on for 15-30 minutes while doing something like copy files, watch youtube, etc and post the resulting screenshot.

Thank you very much.
It works perfectly.
Now we are trying to link all the inputs and outputs.

rodw wrote:

How can you expect the 1 ms servo thread to work when it takes 1,6 Ms on average to talk to the card
Ditch the laptop! 
 

Rod,
I'm want to understand if the laptop is the problem or the adapter?

These are the ping results from the working laptop:
60000 packets transmitted, 60000 received, 0% packet loss, time 60029ms
rtt min/avg/max/mdev = 0.269/0.311/0.600/0.006 ms

These are the ping results from the newer laptop:
60000 packets transmitted, 60000 received, 0% packet loss, time 102174ms
rtt min/avg/max/mdev = 1.297/1.631/3.302/0.044 ms

So obviously the newer laptop is MUCH slower, what I would like to know is the problem the laptop or the external USB-c to Ethernet adapter.

I'm thinking it would be worth trying another adapter, thoughts?

As a reality check, can I force the LinuxCNC timing to extra slow, say 2ms just to see if the error goes away?
If so how would I do that?

rodw wrote:

BUT for a square with NO programmed corners, blend with arcs and parabolas are acceptable? 
This is hypothetical and the gcode is really bad, an error waiting to happen. You might as well attempt to cut a 7 pointed star and break things properly!
Time to get out of the office and onto a real machine!
You should be either looping the corners or adding fillets to the part. If you choose to write bad gcode, be prepared to suffer the consequences. Fixing that is your problem, not the S code developers.

This is the mix up between cv and jerk. This square either has to exact stop at each corner, where linuxcnc has no jerk limiting and makes a big bang, OR, you are running g64 and it rounds the corner base of feed and p value and already functionally works in linuxcnc (it can be better absolutely, but it is that part that DOES work good enough). So clearly we want jerk limiting on the first case (option 1) and its a bit less important in the second case (option 2)... BUT in no way should jerk limiting be directly influencing the path. At all. Ever.

There should be no talk of altering the path, or corners when discussing jerk limiting. In the same way you don't talk about path deviation when discussing acceleration, or velocity. The TP has to hit the path precisely in exact stop mode.

And 100%, you need to be using this on a real machine while you work, not vibe coding and saying "look I made a thing, try it on your expensive equipment for me!". Not even disparaging vibe coding here either if it gets the job done, but you need to actually understand what you are trying to achieve first, and I'm not 100% sure everyone is on the same page.

As I've dug into linuxcnc from a "not particularly good coder" stand point just learning the functional structure, I reaaaaally don't think this is going to happen without a ground up new TP. Option 1 or 2. What seems to be the case is linuxcnc TP is "built different" from most industrial ones and the order of processes causes some problems for simple higher order motion integration.

Can people involved with the existing TP can maybe offer some more complete explanations here? Do we need a structurally new TP to get what we want (option 1 first, 2 second)? I always get some glossed over answers when I search that never supply a definitive "not this isn't going to work at all because:" And we also have the bizarre paradox that linuxcnc in fact surfaces better than many low to mid end jerk limited controls, so we don't want to be losing that either.

And as always, not discouraging anyone or any idea, I have just seen this start and fail SO many time, when literally every other control has had it since the 80s and it always feels like the exact same failure mode: distraction away from the root task.

The 7i96s is a drop in kind of replacement.
At the risk of adding far more complexity, you could consider Ethercat. There are some interesting options emerging. eg The Lichuan 4 axis stepper driver in a single package. I only hope I can get this going, Also available in closed loop. At USD $92 plus shipping, it competes on price depending where you live.