Advanced Search

Well done mate.

There is a lot of consumers here, unless it relates directly to themselves, it's like meh. Don't take it to heart. Unless you come up with a "pretty gui" then it's all different.

Exactly the same question, see the link provided there:
forum.linuxcnc.org/post-processors/53197...x-to-linuxcnc#304893

@Hi Arciera,

I tracked down the issue. One important issue, that was responsible for wrong cone preview angles.
The other issue i will show you in video.

The important issue was a function that calculated the abc angles from a given tcp & ta point in space.
The function was using atan... for 3 planes. However, it did not output what we want to see.

Now i changed the function to use a quaternion with config : gp_Extrinsic_XYZ. new function. This seems to work properly.

Now in next video i recorded tooldir axis lines, to show you what is the difference between

1. recorded tooldir path
2. blended or optimized tooldir path.

In the video the vertical axis lines can contain 2 different colors. One color is for recorded tooldir path. Other color
is for blended tooldir path. The axis lines can be off different lenght between path's. However they are valid as they
are on the same plane.

Parol6 + Octobot-Board
youtube.com/shorts/uLwIUsQQyCQ

HI, Is there any postprocessors available for using NX CAM for Linux CNC. Or any other postprocessors which I can modify to suite for Linux CNC. 
Kindly help me?

 

After I added both of above setting, the issue still happens.

FERROR and MIN_FERROR entries need to be in the [JOINT_n] section not in the [AXIS_l] section:
linuxcnc.org/docs/html/config/ini-config.html

I tried (FERROR; MIN_FERROR) options: (1;0.1) ; (0.1; 0.01) ; (0.01; 0.001)

I would suggest something like (100,100). I presume you are running your drives in position mode and the loop is closed in the drive, if so LinuxCNC really has no part in monitoring following errors at all and setting the values very high will effectively eliminate following error checking in LinuxCNC.

Yes, I think EtherCAT drives handle joint error, but it makes motor shocking so strong & stop suddenly without finishing targeted  position. 

If you get drive faults because of following error then you likely need to lower acceleration/velocity values. Also note that if your SCARA pose is close to a singular point  the kinematic model will likely fail and cause large or even infinite angular velocities which will then cause the drives to fault.

I folllowed your suggestion and now I have a different error:



Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/qtvcp/widgets/status_slider.py", line 142, in _action
ACTION.SET_RAPID_RATE(value)
File "/usr/lib/python3/dist-packages/qtvcp/qt_action.py", line 400, in SET_RAPID_RATE
self.cmd.rapidrate(rate / 100.0)
KeyboardInterrupt

Hello Aciera,

Before your advice, I did not have FERROR & MIN_FERROR.
After I added both of above setting, the issue still happens.
I tried (FERROR; MIN_FERROR) options: (1;0.1) ; (0.1; 0.01) ; (0.01; 0.001)

Yes, I think EtherCAT drives handle joint error, but it makes motor shocking so strong & stop suddenly without finishing targeted  position.

I attach my INI file for your reference.
 

Not like that. Don't change anything in this line "rapid = (float(value) / 100) * self.factor"
If you have updated linuxcnc it is possible that it will work.
You should have checked if there is a line "self.factor = 1.0" in the global variables section, as in the screenshot

Have a look here:
forum.linuxcnc.org/post-processors/52105...iemens-nx-cam#296450

I guess you could verify by checking the value of the 'orient.0.mode' pin.

Thank you,Aciera. I just followed the pin guide map in the following link wiki.linuxcnc.org/uploads/orient.svg , I dont know if I need to net the orient.mode and spindle.orient-mode,because it 's not mentioned in that link.

use this video for your refernce (). This video thay have the testing part for ethercat.

Besides the pins you were already watching also have a look at the 'orient' component pins:
linuxcnc.org/docs/html/man/man9/orient.9.html

This should verify if you are getting any useful signal to 'pos-pid.command'

I see that you have not connected 'orient.0.mode' to 'spindle.0.orient-mode'. Not sure if the 'orient' component has a default value for its 'mode'-pin but you may want to make the connection just to be sure.

Note that I know nothing about the EtherCAT side of things at all, including the 'cia402' component.

Is there any postprocessor for Siemens NX to generate G-code compatible with LinuxCNC?