Advanced Search

Will the 5 axis product line include the 3+1 lineup? or will it be designed directly for 5 axis toolpaths?
Is there an upgrade path from 3+1 to 5axis when released? or new purchase required?

I am about to get a RapdiChange type tool changer running. (thanks to haskins-guitars/linuxcnc-rapidchange  for the code with some modifications) The Tx M6 stuff is all working but editing the tool2.tbl file is a pain (each tool needs a pocket # from 1-8) and then of course after editing you have to restart PathPilot.
The Tooledit gui is the answer but given that Mint 17 is rather ancient I was wondering if anyone has gone through this process already.
PathPilot recently moved to GTK3 so that is a bonus.
Standalone version is fine, it includes a Reload button to reload the configured tool2.tbl file.
The goal is to load up the toolchanger with tools for a program, edit Tool2.tbl, reload it and then run the program.

Hello,
I’d like to try LCNC again on a different PC. Is there perhaps a mini live ISO with a real-time kernel—available on a USB stick or DVD—that contains only the latency test? That way, I could test the PCs beforehand rather than wiping everything, installing LCNC, and then finding out it doesn't work. Thanks,
Hans

If the analog output stays at 0.7V and the PWM value changes, that suggests
that that analog output  has been damaged somehow (or is currently shorted out)

Do you still get  a steady 0.7V output if the analog output is disconnected from the drive?
If so I would try another analog output

 

PLease review my @MrRodW YouTube channel. If you think I can help, email me on the channel email address. I am GMT+10. But a Tommy says Todd is the woodworking expert in the US

So I checked the voltage with a fluke meter a couple of days ago and it never changed, it just stayed at .7 volts DC

Unfortunately no. Linuxcnc must follow the acceleration settings you used in your machine configuration. If your acceleration settings are too slow for your machine you can increase them. But if they are already set as fast as your machine can go, the only other option is to rewrite your g-code to be smoother so the machine does not need to stop and start so much.

Another consideration would be if your G-code has a lot of transitions from short G0 moves short to cutting moves.  This can cause serious slowdowns because those transitions are treated as full stop positioning moves with no blending.  They are the equivalent of programming in G61 mode instead of G64Pn. (Actually I think all G0 moves are full stop positioning moves.) Sometimes changing all G0 moves to G1 moves can significantly improve runtimes.

RV antifreeze is for use in potable water systems, and doesn't have any anti corrosion or lubricative additives like an automotive or other industrial antifreezes. The industrial stuff recommended by most spindle manufactures such as Dowtherm or Dowfrost or their own proprietary mix, is often quite expensive and isn't easy to find compared with automotive products.

Sorry should have said, that I am looking for who still run these, and has plans to update, or could help test a port for the drivers to uspace.

@858PSJ Are you planning to update to linuxcnc 2.9 or 2.10? Willing to test a uspace driver?

ich dachte du wüster das.
Die Namen müssen eineindeutig sein
Benenne "Digital IN" in Digital_IN_0 und Digital_IN_1 um.
oder so ähnlich 

When that ui compiles, it updates the py files correctly using all the required init.

Now THAT makes sense.

Ok, I'll start over without the py file edits and stop at editing the UI files only.  Fingers crossed.

Thanks again.

Yes, the software is available in

German, French, Italian, Spanish, Japanese and Korean apart from English

No not at all I'm telling you from my experience in finding what I said above. It got me in a bunch of trouble.

The py files in the config are created, but the backend code, NOT by a user or me. So when you edit them directly you're changing how they work when loaded. This breaks things that you're likely unaware of and then you ask ai to solve again and it says hey I'll keep going until it works and it's breaking it further...

Hence why I'm saying only edit in the ui in qt designer. When that ui compiles, it updates the py files correctly using all the required init.

Widget rules are built inside designer, formatting can be done in designer under the style sheet. It's ok to ask ai for code to put in designer but not edit the py file or things get out of synch in how they are loaded.

So again never edit anything outside of designer or you are guaranteed to break something that pops up (such as your hal issue and not loading in the correct order or at the correct time).

Two developers tried to create your issue and neither of us could. But we also build correctly in designer only. So finding an issue is all but impossible when the rules get bypasssed from an edit made outside the working system.

That's not too say ai cannot be helpful but how you use it matters. You can't say Claude do this for me unless you specifically give Claude rules to abide by and remain faithful to the existing code architecture. Not knowing how that works means Claude will just find the quickest way to make problem A go away regardless of creating problem B and C. It will even create tests and if they fail it will change the test until it gives a successful result even if that means cheating the test to give that result. And then with bold confidence it will tell you it's fixed the problem with it's own "proof" of the solution

To use Claude correctly you really need to install a dev install with a local pip been where you can give Claude access to the full qtpyvcp repo and probe basic two and linuxcnc repo and open that in a dev folder in vscode where Claude can work through the existing architecture. This will give you better results, but you still need to perform all your machine use config ui work direct in qtdesiger. Using output explanations from the Claude chat.

The very first probably to Claude would be too create a working knowledge base of the 3 softwares and how they interact. And that will take several prompts alone to fill in the gaps.

1. Please post your hal and ini files

2. Measure the output voltage of the 7I97T to see that it changes with position error.

I also tried swapping the +- leads going to the drive and that didn't work,

Note that this usually ends up shorting out the analog output

 

Lcvette wrote:

You need to stop editing the py files, they are generated from ui file and your going to break things doing what you are doing. All edits must be performed in the ui in qt designer as things are designed. I'm going to go out on a limb and say your other issues come from allowing ai to edit files directly. A warning, ai sucks at xml and ui editing because it rarely has our understands the complete context. And if you don't know when it's hallucinating to guide it back to reality it's going to continue down the wrong rabbit hole. Just do your edits/work in designer where it builds the file correctly on start up and correctly uses all necessary code to initiate the used widgets. Your ai generated posts are mostly hallucinations where it may seem confident in it's conclusion but it's completely out in left field and no where near what's actually happening.

Ai seems wonderful until you realize it's extremely fallible.
 

Appreciate your take on it.

I've not touched any of the probe_basic py files, qss files, or anything outside of the config/user_nnn/ folders.

Unfortunately, I am not able to diagnose the various issues without assistance when I can't accomplish what I want in qtpyvcp/qt/PB.  And I would prefer not to pester you or other skilled folks unless absolutely necessary.

I have zero coding skills, period.  I can work out HAL logic no problem, but figuring out how to create a widget rule, stylesheet, or other text/terminal-based edits is a no-go without some sort of assistance.

I tried to add some hal leds.  Didn't work until AI helped me discover it was the layout (as you pointed out).

Once there, I tried to create a widget rule for the hal pins.  Didn't work.  Still doesn't, but without AI I wouldn't have discovered there's no widget rule channel for HAL items.  I would have either given up, or I would have fiddled with everything I could until I broke it and had a tantrum.

With AI help, I now have user-button panel & sidebar indicators that work exactly as I want, and a DRO that's as close to what I want as is reasonable.  Getting to this point would have been impossible without AI assistance, or at best would have taken weeks of back-and-forth over the forum.

I'm sorry if I'm coming off as a clown who's spamming you or muddying the waters with AI slop.  I genuinely hesitated to post anything, including the current GH issue I've got open, but I thought it might be helpful.  Even the "easy fix, you haven't formatted the sidebar..." was a non-obvious problem to me.

And thank you for all the work you've done.  Seriously.