Advanced Search

So I've run this in my virtual machine several times, both in an imperial and a metric simulation on v2.9.238.315.  I cant get it to do anything but cut in the same place over and over.

Perhaps it would be helpful to know more about your workflow?  If it's still a problem, maybe a backup of your config as made from QtPlasmaC would help.

Unfortunately its a bit more complex, the remote update seems to not work properly
with Rev 14 or earlier base part and Rev 15 and newer user parts, so until
this can be figured out, cards Rev 14 or earlier would need to be updated
to Rev 16 with  a PIC programmer. I will try and figure this out tomorrow
but its a bit subtle...

You can get back the original functionality (with key 8 long wiring bug)
by remote updating to the R14 version
 

the one with .ini at the end.
Use a text editor to edit it, not the office suite.

What file is this located in?

probe_basic --version

Double check you have the correct subroutines for the latest update.

Every config is a bit different but mostly the same. You can compare to the sim config for verification.

Ah, gotcha

I made those changes to the xml but I see no difference.
ethercat slaves shows both drives in OP but I can't get them to move and the motor shafts act as if no power is present

For anyone wanting to explore FreeCAD I would highly recommend using the latest development versions. There are nightly builds available through a ppa but I personally would (and do) opt for the near weekly builds of the AppImages from here - github.com/FreeCAD/FreeCAD-Bundle/releases/tag/weekly-builds - Linux, Mac and Window$. No worries about dependences and if any given build has a showstopper bug, you can still have the last weeks to keep going until the next build that will, 99% of the time have that bug fixed. Lots of advanced and more complete features keep showing up. Especially in the CAM workbench.

This is worth reiterating, IMO. Folks seem to be offput by the risk of bugs/crashes in the "weekly" builds, which is both fair and overblown. It's fair in that individual weekly builds occasionally have large issues/bugs (hence Spyderbreath's sound suggestion to not delete your known-working version until you've verified the very latest works). It's overblown in that most of the time they're actually less prone to crashing than 1.0 and have a lot of improvements.

This isn't Microsoft- you can find a weekly build that works for you, and then just not update it if you want a middle ground of getting some of the newer improvements while avoiding most of the instability.

Thank you for the help. I do appreciate it.

In case it helps anyone else willing to give me a hand diagnosing this issue, I've attached my .ini configuration file.

 

hope i did this right

Sorry had a family thing come up I'll post my files up in a min so I can get things checked over befor I power it up and not fry my stuff 

This is the so called "TB6600" with the TB67S109 chip, under 10$ and very good. Get these.

This is the original TB6600 with the TB6600 chip, ~15$ and usable but tend to die for no reason sometimes.

I never use ChatGPT.

It sucks.

The higher the frequency, the higher the power-to-mass ratio.

That's why high frequency switching power supplies are smaller and lighter than comparable line-frequency power supplies.