Advanced Search

Hi Julian,

Did some updates.

The scurve is now conversed to c code. I think this is easyer for bug solving.
And it can now be used directly in lcnc components.

I forgot to apply the feed overide to the end velocity's of segments.
Now it's running much faster.

I came accross a new bug. When a new buffer was loaded, the velocity was starting from zero when
using feed overides around 300%. Lower than that the bug was not visible.
This now is solved. During a new buffer load and transition the velocity keeps up.

There was also a endvel=0 error, wich halted motion,  is solved by pushing the motion into a new segment,
depending on rundir.

Extreme feed overides:

Hello everyone,I'm currently facing an issue while trying to write to the pinusing thecommand in my configuration. Despite the documentation indicating that this pin should be set to read-write by default, I am receiving the error message:"pin 'cia402.4.controlword' is not writable."Here are some details about my setup:

• I have verified the HAL configuration and ensured that the pin is defined correctly.
• The EtherCAT configuration appears to be set up properly, with the relevant PDO and SDO entries.
• The drive is in a state that should allow writing to the control word.

I would appreciate any insights or suggestions on how to resolve this issue. Has anyone else encountered a similar problem? Any help would be greatly appreciated!Thank you!

Thanks for the input guys. I have been able to get quite a bit of the interface working, (display alarm/state, query status of all components, get firmware revisions, set source, set process, and fire torch), but there is still a healthy chunk more to test and work out.  Unfortunately, the XPR I have been connected to has to ship out in a few days and I just came down with the flu.  I have written a python script / hal component to upload and download sdos with a back door local network socket connection to do large multi-index updates and to set things from the gui.  It seems to be working adequately, but still needs a few tweaks and more testing to make sure it is robust.

TRUE HOLE

Hypertherm has a list of features a cnc has to be capable of in order to claim it can support 'True Hole'.  The biggest hurdle is that given an ending feedrate for an arc segment around a hole, it has to be able to ramp up velocity, (the feedrate), linearly from the beginning of the arc segment to the end of the arc segment.  I don't think we have that ability with linuxcnc.

my1987toyota wrote:

Well it's official January 2026 Autodesk Fusion 360 will no longer support Windows 10 . Either switch
to Windows 11 or you can no longer use fusion 360.

Windows.... has been a train wreck for anyone who remotely values their privacy and/or security.
 

Hence the last version of Windows I used was Vista. Linux all the way for me.

Vielleicht hängt das mit diesem veränderten Verhalten zusammen:
forum.linuxcnc.org/10-advanced-configura...ging?start=30#305090

Well it's official January 2026 Autodesk Fusion 360 will no longer support Windows 10 . Either switch
to Windows 11 or you can no longer use fusion 360.

 I am not surprised by their statement just disappointed. Windows 11 has been a train wreck for anyone
who remotely values their privacy and/or security. Then you have Autodesk that has been following the
same mindset. They store all your file's on there servers. You may work off line for short periods of time
but you still will have to log in after a period of time. Like many big companies you can no longer buy
their programs, you can only lease them.

  Again this isn't a surprise. I like many others are learning or already using FreeCAD or similar on the daily
I doubt what I do will really hurt Autodesk's bottom line. That said . I am curious what the shift will truly be.
I am sure many are sick and tired of the "You will own nothing and be happy" corporate mind set.

  I am going FreeCAD. How about everyone else what are you using or switching over too?