Search Results (Searched for: )

  • grandixximo
04 Apr 2026 23:41
Replied by grandixximo on topic LinuxCNC S-Curve Accelerations
@endian
Exactly right, the cycle time is a fundamental constraint that belongs in the tolerance budget, not something to fight against. G-code level control of spike tolerance makes a lot of sense and aligns well with what I have been discussing as a TP option.

@rodw
Fair point in an ideal world, but LinuxCNC has to interface with a very wide range of CAM outputs, many of which the end user has no control over. We should strive for maximum compatibility. Yes, some G-code will be genuinely nonsense and will need fixing at the source, but for cases where the geometry is valid and the only issue is a parameter mismatch between the toolpath and the machine limits, an INI or G-code option that lets the integrator choose the behavior is the right balance rather than rejecting the job outright.
  • spumco
04 Apr 2026 22:40
Replied by spumco on topic Pico Systems Servo Controller

I have a need for some Pico hardware to validate some updates to the driver ( github.com/LinuxCNC/linuxcnc/issues/2331 )

Could I persuade you to send the cards to the UK (and maybe reduce the price even more, as this is for the project, not for me, and the project has exactly zero money)
 
How much does the project need me to send the OP?

I can't code my way out of a paper bag, but I know how to solve this problem.
  • tommylight
04 Apr 2026 22:17
Replied by tommylight on topic Closed loop - encoder/position not updating while moving
Thank you for reporting back.
  • reboots
04 Apr 2026 22:05
Replied by reboots on topic Spindle delay
I just wanted to register that this solved the same issue for me on 2.9.7. There are older solutions on the forum, for example " Automatic pause when spindle is started " from 2015, but they don't reflect current pin/signal names. Modified default spindle control HAL section below, two lines commented out and six more required.
Code:
# ---setup spindle control signals--- net spindle-vel-cmd-rps        <=  spindle.0.speed-out-rps net spindle-vel-cmd-rps-abs    <=  spindle.0.speed-out-rps-abs net spindle-vel-cmd-rpm        <=  spindle.0.speed-out net spindle-vel-cmd-rpm-abs    <=  spindle.0.speed-out-abs net spindle-enable             <=  spindle.0.on net spindle-cw                 <=  spindle.0.forward net spindle-ccw                <=  spindle.0.reverse net spindle-brake              <=  spindle.0.brake net spindle-revs               =>  spindle.0.revs ##net spindle-at-speed           =>  spindle.0.at-speed net spindle-vel-fb-rps         =>  spindle.0.speed-in net spindle-index-enable      <=>  spindle.0.index-enable # ---Setup spindle at speed signals--- ##sets spindle-at-speed true # 5-second spindle ramp delay loadrt timedelay count=1 addf timedelay.0 servo-thread setp timedelay.0.on-delay 5 net spindle-enable => timedelay.0.in net spindle-timer <= timedelay.0.out net spindle-timer => spindle.0.at-speed

My spindle VFD is connected as follows for simple "run" operation with no feedback:
Code:
net spindle-enable  =>     hm2_5i25.0.7i77.0.0.output-00
  • backyardengineer
04 Apr 2026 21:49
Replied by backyardengineer on topic Closed loop - encoder/position not updating while moving
Hi, just wanted to give an update. The problem was annoyingly trivial: The chinese board was faulty.... They are of astonishingly poor quality. I ordered two to new ones, one came already dead, they soldered the diode (on the 24v input) in the wrong way. Anyway thank you for troubleshooting with me. All the best, Marc
  • rodw
04 Apr 2026 21:48
Replied by rodw on topic LinuxCNC S-Curve Accelerations
All this talk about exact stop mode and angles to me seems to be an academic exercise in mathematics. In the real world it can be solved by simply sacking the part designer. A few minutes at the design phase to account for the physical constraints of the manufacturing process can save many hours of work on the shop floor. This does not just apply to the machining world, there are many other work environments where this rule applies. In my case, it applied in the printing industry and I made sure wherever possible my graphic artists designed for our capabilities.

Reject the design, and send it back for rework would solve most issues when this hits the real world...
 
  • andypugh
04 Apr 2026 21:23
Replied by andypugh on topic Pico Systems Servo Controller
I have a need for some Pico hardware to validate some updates to the driver ( github.com/LinuxCNC/linuxcnc/issues/2331 )

Could I persuade you to send the cards to the UK (and maybe reduce the price even more, as this is for the project, not for me, and the project has exactly zero money)
  • spumco
04 Apr 2026 21:02
Replied by spumco on topic CSS/G96 for other than X-axis?

Sounds correct. Famous last words :)

Yea, that was backwards

Makes sense in hindsight: I want the V-DRO to move at twice the speed of the joint, not half.

But everything's working now: switchkins, subspindle synch to main with CSS and the parting slide programmed as "X".

I couldn't compress a GIF small enough to embed, but I've attached a short video as a ZIP file.

parting_slide.comp and the four M-codes are all commented pretty heavily for future reference.

I think this is nearly the last hurdle on the DIY lathe.  Only big challenge I can think of is mounting tools for subspindle work.

Thanks again @Aciera, couldn't have done it without you.
  • andypugh
04 Apr 2026 20:09
Replied by andypugh on topic New update on STMBL
I suspect that the problem is getting hold of the actual hardware?
  • tommylight
04 Apr 2026 20:04
Replied by tommylight on topic Ethercat random jitter fix

 
I saw at my own eyes synchronization of 120 seconds with beckhoff SoE AX5125 driver with older firmware ... its not odd behaviour 

beckhoff IPCs have sometime very similar behaviour with their own hardware from my close experiences...
[/quote]
The more i read here about ethercat = the less i like it.
Thank you for pointing out the quirks, not only the good stuff.
  • andypugh
04 Apr 2026 19:46
Replied by andypugh on topic RRW Lab SPI with raspberry pi 5
I tried Googling the RRW lab board and all found was this thread.

Can you link to a product page or give is more to go on?

Do you have a driver for it?
  • endian
04 Apr 2026 19:08
Replied by endian on topic Ethercat random jitter fix

Synchronization of slave clocks can sometimes take a long time at start.
There is a warning in syslog if it takes more than 5 seconds, or is it 30?
Don't know how to fix it, more than hope the slaves' clocks run more equal
when not being nudged by the master.
Add pll-err to the halscope plot. 
 
I saw at my own eyes synchronization of 120 seconds with beckhoff SoE AX5125 driver with older firmware ... its not odd behaviour 

beckhoff IPCs have sometime very similar behaviour with their own hardware from my close experiences...
  • endian
04 Apr 2026 18:52 - 04 Apr 2026 19:03
Replied by endian on topic AX5201 does not change to SAFEOP / OP
hi there,

if you do not want to change timing in the TC3 to 1ms (easiest way and no play to errors) then change -
Code:
<EtherCATMailbox> <script id="eppiocemhmnlbhjplcgkofciiegomcon"/> <script/> <script/> <SoE> <InitCmds> <InitCmd> <Transition>PS</Transition> <Comment> <![CDATA[ Tncyc - NC cycle time ]]> </Comment> <Timeout>0</Timeout> <OpCode>3</OpCode> <DriveNo>0</DriveNo> <IDN>1</IDN> <Elements>64</Elements> <Attribute>0</Attribute> <Data>d007</Data>                      to                  <Data>e803</Data> </InitCmd> <InitCmd> <Transition>PS</Transition> <Comment> <![CDATA[ Tscyc - Comm cycle time ]]> </Comment> <Timeout>0</Timeout> <OpCode>3</OpCode> <DriveNo>0</DriveNo> <IDN>2</IDN> <Elements>64</Elements> <Attribute>0</Attribute> <Data>d007</Data>                      to                  <Data>e803</Data> </InitCmd>

and in ethercat conf xml change -
Code:
<masters> <script id="eppiocemhmnlbhjplcgkofciiegomcon"/> <script/> <script/> <master idx="0" appTimePeriod="1000000" refClockSyncCycles="-1">

and in .ini file change - 
Code:
[TASK] TASK = milltask #CYCLE_TIME = 0.002 CYCLE_TIME = 0.001 [EMCMOT] EMCMOT = motmod COMM_TIMEOUT = 1.0 BASE_PERIOD = 0 #SERVO_PERIOD = 2000000 SERVO_PERIOD = 1000000


check cabling CAT5e with shielding ... its pretty sensitive stuff

check if you have non generic driver ... it has to be native NIC driver at network card with EoE turned off => very important

set time of task in TC3 to 1ms and export it ... 

connect just and only AX5201 to ethercat master... export config and translate it (problem isolation)

change 0x0740 to 0x0730 ... timing have to be correct because it is direct timing extraction from beckhoff master and exported to our shape ... 
  • Aciera
04 Apr 2026 18:35
Replied by Aciera on topic CSS/G96 for other than X-axis?


Just so Im clear, the pos->v = 2*j[2];function results in the V-axis moving twice the distance of JOINT_2?

And the reverse forj[2] =0.5* pos->v;in the Inverse section?

yes, the dro readout for V will show the double of the joint_2 position or, in other words, joint_2 will move half the commanded V axis position.


Don't adjust the case 1 X-axis/joint_2 relationship, because X-axis will move at half-distance when in diameter mode.
DO adjust the case 1 V-axis/joint_0 relationship, because LCNC doesn't have a diameter mode for any axis other than X.

Sounds correct. Famous last words :)
  • spumco
04 Apr 2026 18:08
Replied by spumco on topic CSS/G96 for other than X-axis?
Well that's a clever idea.

Just so Im clear, the pos->v = 2*j[2];function results in the V-axis moving twice the distance of JOINT_2?

And the reverse forj[2] =0.5* pos->v;in the Inverse section?

Which means in case 1 I'd want to adjust the X-axis:pos->tran.x = 2*j[2];So the X-axis moves the correct distance when connected to the parting slide joint?


Which means I can adjust the INI stepgen position scale so it's not cut in half, and then adjust both case 0 and case 1 so the V-axis moves half the distance (diameter mode).

Code:
case 0: pos->tran.x = j[0]; pos->tran.z = j[1]; pos->v = 0.5*j[2]; break; case 1: pos->tran.x = j[2]; pos->tran.z = j[1]; pos->v = 0.5*j[0]; break;
  • Don't adjust the case 1 X-axis/joint_2 relationship, because X-axis will move at half-distance when in diameter mode.
  • DO adjust the case 1 V-axis/joint_0 relationship, because LCNC doesn't have a diameter mode for any axis other than X.

Make sense, or have I got something wrong?
Displaying 5086 - 5100 out of 11812 results.
Time to create page: 0.167 seconds
Powered by Kunena Forum