Advanced Search

I think the problem with the keys is with the probe basic interface because it works perfectly on axis.

    I keep getting a soft max and min limit after homing x and stops the homing all process, after homing it gives "Exceeded POSITIVE soft limit (4.80000) on joint 0" i can neither move x or y axis, can move z axis, I can home y axis, but then I cant move z axis after that.I have the axis version of linuxcnc 2.9.0 on plasma KDE desktop. 

unfortunately with NVEM I had a bad experience, even with drivers other than TB6560, it could be my fault.
With EC500 after a moment of panic for the time out,
it was possible to recover and it worked on the first try

it is not necessarily the same for you

jjdege wrote:

sorry i dont understand, maybe i missed some step,
here you say everything is ok.
what is not working? Have you tried on other axes?

yes the direction of rotation and all the axes respond, you have some axes that don't work at all! Mine work but not smoothly!

Hi, are the xml files from the aforementioned Sasha’s shop somewhere to be found? Would love to have a look.

Yes that 64-bit integer data-type is missing in hal, but I think I heard that might change for next release. Don't quote me on that though.
In the other hand, there is the flexibility to use all EtherCAT's data types (almost then) and convert data into hal data types to send and receive so in one way it is very flexible. Downside is it requires a bit of understanding from the user who may not be so interested in this, just want to use it kind of.

sorry i dont understand, maybe i missed some step,
here you say everything is ok.
what is not working? Have you tried on other axes?

deleted

Well, that thread helped me before but i somehow did not notice the "Basic Mill Config Using hal_gpio" ...would have saved me a lot of time... anyways - works fine now - Thank you!

Lots of other men contributed to its discovery and invention too.

If you mean the induction motor, no, no one even tried it before him. He knew his s#it, for sure.
Induction motor has no magnets, no rotor coils, no brushes, yet it works!
It has been the single most important discovery that pushed civilization and the industrial complex forward.

forum.linuxcnc.org/9-installing-linuxcnc...only?start=10#321296

WTF would you use AI ?????????


BTW Just about everything to do with the Rpi5\4 images is in the thread linked above, rather than waste time with AI read something, a lot of work has and is going into that thread.

The B Axis can be locked but also rotate freely for full simulatanious 5 axis milling.
The milling spindle in the B-axis can be locked in 12 positions for broaching and turning or rotate freely as a milling spindle.

I don't THINK that TCP needs to be applied for turning. To be honest im not particular sure. I know from a metal working perspective that an endmill can have z and x tool-offsets and turning tools can have x/y/and z. How and if that needs to be incorperated into the kinematic...?

Here is a link to see the machine in operation to get a better understanding what is possible:


Machining starts at roughly 4:51
Its a rather simple part for a Millturn but it gives at least a rough understanding of the operation of such a machine.

Tomorrow i wil work more with Fusion and the Doosan millturn PP and see what else of proprietary G-code will be posted.

Hi, i have a similar problem with my RPi5 and GPIO but I think I/(the AI that helped me) screwed up with the .hal-File. Do you (or anyone) mind to put your working .hal here so I can see how it is done?

All available hal components work with s/u32 pins
There is no point in having 16bit numbers from ethercat, because to connect to subsequent components they will have to be converted to 32bit anyway by loading additional components to convert 16->32.
The LCEC component does this automatically in the XML configuration.  pdoentry

In practice, there will probably never be any memory problems, as the number of pdos and sm is quite limited.

There have also been suggestions in the forum to make all HAL pins 64bit for standardisation, as encoders have a problem with overflowing 32bit numbers.

Search for the ec_generic.so files like  I did.