Search Results (Searched for: )
- rodw
07 Jun 2025 21:14
Replied by rodw on topic Feature Request: ramp piercing (aka moving piercing)
Feature Request: ramp piercing (aka moving piercing)
Category: Plasmac
You really should read the previous post.Sorry to post on a old topic but I wanted to see if this functionality was in qtplasmac in the 2.9.4 install or if you need to be running from the 2.10 master? Also, has anyone done moving piercing in Fusion360 CAM?
- BlownCorona
- BlownCorona
07 Jun 2025 21:01
Replied by BlownCorona on topic Mesa 7i97T & LinuxCNC setup struggles
Mesa 7i97T & LinuxCNC setup struggles
Category: Installing LinuxCNC
Yesterday evening i was using chatgpt to help understand some of the nuts and bolts of what certain values mean. i made progress but perhaps you can check its homework.
i did set the following errors wider which has prevented this error occurring for the most part, though i understand this should eventually be taken right back down to the tight window it should be.
FERROR = 10
MIN_FERROR = 5
notably, it suggested changing the PWM scale from 10 to 1, claming that this would provide the expected +-10V and the voltage limits coming from the max outputs which on the surface makes sense and got me to the point where i was tuning a motor that was either violently oscillating or buzzing angrily, tuning pid values to a very low point gave a quieter (but not silent) motor but it was sluggish.
Now it could be that im not in a position to tune properly, or i could have screwed the code up much worse because i am quite aware that chatgpt is not our savior and it will be confidently wrong.
the documentation here supports the claim that the scale should = 1 however im not certain why mesaCT set that scale as = 10
www.linuxcnc.org/docs/html/man/man9/pwmgen.9.html
feels like progress, and i dont think im far off cracking it.
i did set the following errors wider which has prevented this error occurring for the most part, though i understand this should eventually be taken right back down to the tight window it should be.
FERROR = 10
MIN_FERROR = 5
notably, it suggested changing the PWM scale from 10 to 1, claming that this would provide the expected +-10V and the voltage limits coming from the max outputs which on the surface makes sense and got me to the point where i was tuning a motor that was either violently oscillating or buzzing angrily, tuning pid values to a very low point gave a quieter (but not silent) motor but it was sluggish.
Now it could be that im not in a position to tune properly, or i could have screwed the code up much worse because i am quite aware that chatgpt is not our savior and it will be confidently wrong.
the documentation here supports the claim that the scale should = 1 however im not certain why mesaCT set that scale as = 10
www.linuxcnc.org/docs/html/man/man9/pwmgen.9.html
feels like progress, and i dont think im far off cracking it.
- rodw
07 Jun 2025 21:00
Replied by rodw on topic IO Questions around mixing IO between Ethercat and Pi 5?
IO Questions around mixing IO between Ethercat and Pi 5?
Category: EtherCAT
Howdy all,
I am working out the high level architecture (and ordering) for a Ethercat retrofit of my CNC Mill ( its VFD is dying and its as good an excuse as any to re work may decisions I made on it when I converted it to LinuxCNC the first time)..
Anyways, I am looking at the MPG and realizing that I have open IO pins on my pi (like all of them).
So here is my current "plan" for I/O which I would love feedback on
1x EK1100 - Ethercat to FieldBus coupler
2x EL1819 - 16 inputs (I need 28 so 2 it is) - (the response time is killer vs the EL1809)
1x EL2819 - 16 output (need 11 so that works)
1x EL5151 - Encoder for the MPG <-- this is where I would love feedback because this guy is $250 used
The really open question is what risks on integration and general PITA am I facing if I use my Pi's IO pins to handle MPG encoder rather than the spendy EL5151.
I plan to use either Leadshine or Innovance mult-turn servos for all of my motors and spindle so my only current known need for an encoder is the MPG... This is less a question of "can I mix Ethercat with Pi IO pins" and more a question of "should I"... Am I setting myself up for sparks and pain getting the realtime thread where the Pi IO will come in syncing with the rest of the system that is all running on the Server Thread?
To that end, should I be using other parts of the Pi's IO for emergency stuff like e-stop?
Thanks in advance.
- rodw
07 Jun 2025 20:54
Replied by rodw on topic QTPlasmac pierce delay handling
QTPlasmac pierce delay handling
Category: Plasmac
The pierce delay starts from when qtplasmac gets an ArcOK signal signifying that arc transfer has occurred. If your synthesized arcOK is off, you will have problems.
Do yourself a favour and wire in the machine's arcOK signal. The time you will save stuffing around trying to get a synthesized arcOK working will more than cover the time you will spend wiring it in properly.
Do yourself a favour and wire in the machine's arcOK signal. The time you will save stuffing around trying to get a synthesized arcOK working will more than cover the time you will spend wiring it in properly.
- beauxnez
- beauxnez
07 Jun 2025 19:22
Replied by beauxnez on topic ESP32/S2/S3 LinuxCNC Controller (6 axis hardware step gen), USB plug-and-play
ESP32/S2/S3 LinuxCNC Controller (6 axis hardware step gen), USB plug-and-play
Category: Computers and Hardware
Thanks for the reply
This version doesn't work?
github.com/SybexX/ESP32_LinuxCNC_MotionController_RealTime
This version doesn't work?
github.com/SybexX/ESP32_LinuxCNC_MotionController_RealTime
- PCW
07 Jun 2025 19:06
Replied by PCW on topic Index homing Heidenhain ls 403/exe602
Index homing Heidenhain ls 403/exe602
Category: Basic Configuration
I am still looking into this, I did make a small change to the encoder driver to simplify
the index spacing detection. (I added the option to not zero the position on index detection)
This should simplify the distance coded index detection hal component, otherwise I would
have needed to undo the encoder position zeroing in the hal component, and that was pretty ugly.
the index spacing detection. (I added the option to not zero the position on index detection)
This should simplify the distance coded index detection hal component, otherwise I would
have needed to undo the encoder position zeroing in the hal component, and that was pretty ugly.
- PCW
07 Jun 2025 18:58
Replied by PCW on topic Mesa 7i97T & LinuxCNC setup struggles
Mesa 7i97T & LinuxCNC setup struggles
Category: Installing LinuxCNC
I would try setting the following errors wider so you can see the actual behavior without getting an instant following error
(say 25 and 25 mm)
Then first set the PID up with all terms 0 except a small amount of P
Then check if the motors roughly hold position and move when jogged
(say 25 and 25 mm)
Then first set the PID up with all terms 0 except a small amount of P
Then check if the motors roughly hold position and move when jogged
- TheTinkeringMechanic1
- TheTinkeringMechanic1
07 Jun 2025 18:46
Replied by TheTinkeringMechanic1 on topic CNC lathe to grinder.
CNC lathe to grinder.
Category: Basic Configuration
Please read the post fully to understand why this is necessary.
- TheTinkeringMechanic1
- TheTinkeringMechanic1
07 Jun 2025 18:44
Replied by TheTinkeringMechanic1 on topic CNC lathe to grinder.
CNC lathe to grinder.
Category: Basic Configuration
I will get this posted as soon as I can. Thank you.
- farmer_mike
- farmer_mike
07 Jun 2025 17:59
Replied by farmer_mike on topic Experimental XML config generator
Experimental XML config generator
Category: EtherCAT
Thanks for the help everyone. I decided to move my project to a Raspberry Pi 4, so I made sure to use the latest versions of LinuxCNC and Ethercat. I think I have the experimental XML config working now. I am a little unsure what to do with the output file.
I'll paste two files below. The first file is the ethercat-conf.xml from my CNC project when I had a single axis using an Rtelligent ECT 60 stepper motor.The single axis worked, so I have since bought two Rtelligent RS750E AC Servo drives. All I have done with the RS750E drives is power them up and connect the Ethernet. I haven't done any onboard parameter programming yet.
The experimental XML config generator recognized all three drives in order.
Is the output from the experimental XML config generator meant to be used to create the ethercat-conf.xml file?
I'll paste two files below. The first file is the ethercat-conf.xml from my CNC project when I had a single axis using an Rtelligent ECT 60 stepper motor.The single axis worked, so I have since bought two Rtelligent RS750E AC Servo drives. All I have done with the RS750E drives is power them up and connect the Ethernet. I haven't done any onboard parameter programming yet.
The experimental XML config generator recognized all three drives in order.
Is the output from the experimental XML config generator meant to be used to create the ethercat-conf.xml file?
<masters>
<master idx="0" appTimePeriod="1000000" refClockSyncCycles="1">
<!-- Joint 0 -->
<slave idx="0" type="generic" vid="00000a88" pid="0a880002" configPdos="true">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<sdoConfig idx="2000" subIdx="0"><sdoDataRaw data ="88 13"/></sdoConfig> <!-- Max motor current (5.0) -->
<sdoConfig idx="2007" subIdx="6"><sdoDataRaw data ="05"/></sdoConfig> <!-- Input 6 - Emergency Stop -->
<sdoConfig idx="2007" subIdx="5"><sdoDataRaw data ="05"/></sdoConfig> <!-- Input 3 - Home Function -->
<sdoConfig idx="2011" subIdx="0"><sdoDataRaw data ="01 00"/></sdoConfig> <!-- Closed loop -->
<sdoConfig idx="6098" subIdx="0"><sdoDataRaw data ="11 00"/></sdoConfig> <!-- Home mode 17 -->
<sdoConfig idx="607C" subIdx="0"><sdoDataRaw data ="00 00"/></sdoConfig> <!-- Home offset 0 -->
<sdoConfig idx="609A" subIdx="0"><sdoDataRaw data ="F4 01"/></sdoConfig> <!-- Home accelleration 500 -->
<sdoConfig idx="6099" subIdx="01"><sdoDataRaw data ="C4 09"/></sdoConfig> <!-- Home fast speed 2500-->
<sdoConfig idx="6099" subIdx="02"><sdoDataRaw data ="F4 01"/></sdoConfig> <!-- Home slow speed 500 -->
<syncManager idx="2" dir="out">
<pdo idx="1600">
<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="cia-controlword" halType="u32"/>
<pdoEntry idx="6060" subIdx="00" bitLen="8" halPin="opmode" halType="s32"/>
<!-- Target Position -->
<pdoEntry idx="607A" subIdx="00" bitLen="32" halPin="target-position" halType="s32"/>
<!-- Target Velocity -->
<pdoEntry idx="60FF" subIdx="00" bitLen="32" halPin="target-velocity" halType="s32"/>
<!-- Digtial Outputs (manufacturer's extension ECT86/ECT60)-->
<pdoEntry idx="204A" subIdx="0" bitLen="16" halType="complex">
<complexEntry bitLen="1" halPin="out-1" halType="bit"/>
<complexEntry bitLen="1" halPin="out-2" halType="bit"/>
<complexEntry bitLen="14"/>
</pdoEntry>
</pdo>
</syncManager>
<syncManager idx="3" dir="in">
<pdo idx="1a00">
<pdoEntry idx="6041" subIdx="00" bitLen="16" halPin="cia-statusword" halType="u32"/>
<pdoEntry idx="6061" subIdx="00" bitLen="8" halPin="opmode-display" halType="s32"/>
<pdoEntry idx="6064" subIdx="00" bitLen="32" halPin="actual-position" halType="s32"/>
<pdoEntry idx="606C" subIdx="00" bitLen="32" halPin="actual-velocity" halType="s32"/>
<pdoEntry idx="6077" subIdx="00" bitLen="32" halPin="actual-torque" halType="s32"/>
<!-- Digtial_inputs (cia402 compatible) -->
<pdoEntry idx="60FD" subIdx="0" bitLen="32" halType="complex">
<complexEntry bitLen="1" halPin="CW-limit" halType="bit"/>
<complexEntry bitLen="1" halPin="CCW-limit" halType="bit"/>
<complexEntry bitLen="1" halPin="in-home" halType="bit"/>
<complexEntry bitLen="13"/>
<complexEntry bitLen="1" halPin="in-1" halType="bit"/>
<complexEntry bitLen="1" halPin="in-2" halType="bit"/>
<complexEntry bitLen="1" halPin="in-3" halType="bit"/>
<complexEntry bitLen="1" halPin="in-4" halType="bit"/>
<complexEntry bitLen="1" halPin="in-5" halType="bit"/>
<complexEntry bitLen="1" halPin="in-6" halType="bit"/>
<complexEntry bitLen="10"/>
</pdoEntry>
</pdo>
</syncManager>
</slave>
</master>
</masters>
<masters>
<master idx="0">
<slave idx="0" type="ECT60" name="D1">
<!-- Enable support for Cyclic Synchronous Position mode. -->
<modParam name="enableCSP" value="true"/>
<!-- Enable support for Cyclic Synchronous Velocity mode. -->
<modParam name="enableCSV" value="false"/>
<!-- Maximum stepper Amps. -->
<modParam name="peakCurrent_amps" value="6.0"/>
<!-- Operation mode: openloop, closedloop, or foc. -->
<modParam name="controlMode" value="closedloop"/>
<!-- Number of encoder steps per revolution. -->
<modParam name="encoderResolution" value="4000"/>
<!-- Output 1 use: general, alarm, brake, in-place. -->
<modParam name="output1Func" value="alarm"/>
<!-- Output 2 use: general, alarm, brake, in-place. -->
<modParam name="output2Func" value="brake"/>
<!-- Input 3 use: general, cw-limit, ccw-limit, home, clear-fault, emergency-stop, motor-offline, probe1, probe2 -->
<modParam name="input3Func" value="cw-limit"/>
<!-- Input 4 use: general, cw-limit, ccw-limit, home, clear-fault, emergency-stop, motor-offline, probe1, probe2 -->
<modParam name="input4Func" value="ccw-limit"/>
<!-- Input 5 use: general, cw-limit, ccw-limit, home, clear-fault, emergency-stop, motor-offline, probe1, probe2 -->
<modParam name="input5Func" value="home"/>
<!-- Input 6 use: general, cw-limit, ccw-limit, home, clear-fault, emergency-stop, motor-offline, probe1, probe2 -->
<modParam name="input6Func" value="motor-offline"/>
</slave>
<slave idx="1" type="basic_cia402" vid="0x00000a88" pid="0x0a880013" name="D2">
<!--RS750E(COE)-->
<modParam name="ciaRxPDOEntryLimit" value="9"/>
<modParam name="ciaTxPDOEntryLimit" value="9"/>
<modParam name="enablePP" value="true"/>
<modParam name="enablePV" value="true"/>
<modParam name="enableTQ" value="true"/>
<modParam name="enableHM" value="true"/>
<modParam name="enableCSP" value="true"/>
<modParam name="enableCSV" value="true"/>
<modParam name="enableCST" value="true"/>
<modParam name="enableActualFollowingError" value="true"/>
<modParam name="enableActualTorque" value="true"/>
<modParam name="enableDigitalInput" value="true"/>
<modParam name="digitalInChannels" value="16"/>
<modParam name="enableDigitalOutput" value="true"/>
<modParam name="digitalOutChannels" value="16"/>
<modParam name="enableErrorCode" value="true"/>
<modParam name="enableFollowingErrorTimeout" value="true"/>
<modParam name="enableFollowingErrorWindow" value="true"/>
<modParam name="enableHomeAccel" value="true"/>
<modParam name="enableMaximumCurrent" value="true"/>
<modParam name="enableMaximumTorque" value="true"/>
<modParam name="enablePolarity" value="true"/>
<modParam name="enablePositionDemand" value="true"/>
<modParam name="enablePositioningTime" value="true"/>
<modParam name="enablePositioningWindow" value="true"/>
<modParam name="enableProbeStatus" value="true"/>
<modParam name="enableProfileAccel" value="true"/>
<modParam name="enableProfileDecel" value="true"/>
<modParam name="enableProfileMaxVelocity" value="true"/>
<modParam name="enableProfileVelocity" value="true"/>
<modParam name="enableTargetTorque" value="true"/>
<modParam name="enableTorqueDemand" value="true"/>
<modParam name="enableTorqueSlope" value="true"/>
<modParam name="enableVelocityErrorTime" value="true"/>
<modParam name="enableVelocityErrorWindow" value="true"/>
</slave>
<slave idx="2" type="basic_cia402" vid="0x00000a88" pid="0x0a880013" name="D3">
<!--RS750E(COE)-->
<modParam name="ciaRxPDOEntryLimit" value="9"/>
<modParam name="ciaTxPDOEntryLimit" value="9"/>
<modParam name="enablePP" value="true"/>
<modParam name="enablePV" value="true"/>
<modParam name="enableTQ" value="true"/>
<modParam name="enableHM" value="true"/>
<modParam name="enableCSP" value="true"/>
<modParam name="enableCSV" value="true"/>
<modParam name="enableCST" value="true"/>
<modParam name="enableActualFollowingError" value="true"/>
<modParam name="enableActualTorque" value="true"/>
<modParam name="enableDigitalInput" value="true"/>
<modParam name="digitalInChannels" value="16"/>
<modParam name="enableDigitalOutput" value="true"/>
<modParam name="digitalOutChannels" value="16"/>
<modParam name="enableErrorCode" value="true"/>
<modParam name="enableFollowingErrorTimeout" value="true"/>
<modParam name="enableFollowingErrorWindow" value="true"/>
<modParam name="enableHomeAccel" value="true"/>
<modParam name="enableMaximumCurrent" value="true"/>
<modParam name="enableMaximumTorque" value="true"/>
<modParam name="enablePolarity" value="true"/>
<modParam name="enablePositionDemand" value="true"/>
<modParam name="enablePositioningTime" value="true"/>
<modParam name="enablePositioningWindow" value="true"/>
<modParam name="enableProbeStatus" value="true"/>
<modParam name="enableProfileAccel" value="true"/>
<modParam name="enableProfileDecel" value="true"/>
<modParam name="enableProfileMaxVelocity" value="true"/>
<modParam name="enableProfileVelocity" value="true"/>
<modParam name="enableTargetTorque" value="true"/>
<modParam name="enableTorqueDemand" value="true"/>
<modParam name="enableTorqueSlope" value="true"/>
<modParam name="enableVelocityErrorTime" value="true"/>
<modParam name="enableVelocityErrorWindow" value="true"/>
</slave>
</master>
</masters>
- farmer_mike
- farmer_mike
07 Jun 2025 17:55
test post was created by farmer_mike
test post
Category: Off Topic and Test Posts
Thanks for the help everyone. I decided to move my project to a Raspberry Pi 4, so I made sure to use the latest versions of LinuxCNC and Ethercat. I think I have the experimental XML config working now. I am a little unsure what to do with the output file.
I'll paste two files below. The first file is the ethercat-conf.xml from my CNC project when I had a single axis using an Rtelligent ECT 60 stepper motor.The single axis worked, so I have since bought two Rtelligent RS750E AC Servo drives. All I have done with the RS750E drives is power them up and connect the Ethernet. I haven't done any onboard parameter programming yet.
The experimental XML config generator recognized all three drives in order.
Is the output from the experimental XML config generator meant to be used to create the ethercat-conf.xml file?
I'll paste two files below. The first file is the ethercat-conf.xml from my CNC project when I had a single axis using an Rtelligent ECT 60 stepper motor.The single axis worked, so I have since bought two Rtelligent RS750E AC Servo drives. All I have done with the RS750E drives is power them up and connect the Ethernet. I haven't done any onboard parameter programming yet.
The experimental XML config generator recognized all three drives in order.
Is the output from the experimental XML config generator meant to be used to create the ethercat-conf.xml file?
<masters>
<master idx="0" appTimePeriod="1000000" refClockSyncCycles="1">
<!-- Joint 0 -->
<slave idx="0" type="generic" vid="00000a88" pid="0a880002" configPdos="true">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<sdoConfig idx="2000" subIdx="0"><sdoDataRaw data ="88 13"/></sdoConfig> <!-- Max motor current (5.0) -->
<sdoConfig idx="2007" subIdx="6"><sdoDataRaw data ="05"/></sdoConfig> <!-- Input 6 - Emergency Stop -->
<sdoConfig idx="2007" subIdx="5"><sdoDataRaw data ="05"/></sdoConfig> <!-- Input 3 - Home Function -->
<sdoConfig idx="2011" subIdx="0"><sdoDataRaw data ="01 00"/></sdoConfig> <!-- Closed loop -->
<sdoConfig idx="6098" subIdx="0"><sdoDataRaw data ="11 00"/></sdoConfig> <!-- Home mode 17 -->
<sdoConfig idx="607C" subIdx="0"><sdoDataRaw data ="00 00"/></sdoConfig> <!-- Home offset 0 -->
<sdoConfig idx="609A" subIdx="0"><sdoDataRaw data ="F4 01"/></sdoConfig> <!-- Home accelleration 500 -->
<sdoConfig idx="6099" subIdx="01"><sdoDataRaw data ="C4 09"/></sdoConfig> <!-- Home fast speed 2500-->
<sdoConfig idx="6099" subIdx="02"><sdoDataRaw data ="F4 01"/></sdoConfig> <!-- Home slow speed 500 -->
<syncManager idx="2" dir="out">
<pdo idx="1600">
<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="cia-controlword" halType="u32"/>
<pdoEntry idx="6060" subIdx="00" bitLen="8" halPin="opmode" halType="s32"/>
<!-- Target Position -->
<pdoEntry idx="607A" subIdx="00" bitLen="32" halPin="target-position" halType="s32"/>
<!-- Target Velocity -->
<pdoEntry idx="60FF" subIdx="00" bitLen="32" halPin="target-velocity" halType="s32"/>
<!-- Digtial Outputs (manufacturer's extension ECT86/ECT60)-->
<pdoEntry idx="204A" subIdx="0" bitLen="16" halType="complex">
<complexEntry bitLen="1" halPin="out-1" halType="bit"/>
<complexEntry bitLen="1" halPin="out-2" halType="bit"/>
<complexEntry bitLen="14"/>
</pdoEntry>
</pdo>
</syncManager>
<syncManager idx="3" dir="in">
<pdo idx="1a00">
<pdoEntry idx="6041" subIdx="00" bitLen="16" halPin="cia-statusword" halType="u32"/>
<pdoEntry idx="6061" subIdx="00" bitLen="8" halPin="opmode-display" halType="s32"/>
<pdoEntry idx="6064" subIdx="00" bitLen="32" halPin="actual-position" halType="s32"/>
<pdoEntry idx="606C" subIdx="00" bitLen="32" halPin="actual-velocity" halType="s32"/>
<pdoEntry idx="6077" subIdx="00" bitLen="32" halPin="actual-torque" halType="s32"/>
<!-- Digtial_inputs (cia402 compatible) -->
<pdoEntry idx="60FD" subIdx="0" bitLen="32" halType="complex">
<complexEntry bitLen="1" halPin="CW-limit" halType="bit"/>
<complexEntry bitLen="1" halPin="CCW-limit" halType="bit"/>
<complexEntry bitLen="1" halPin="in-home" halType="bit"/>
<complexEntry bitLen="13"/>
<complexEntry bitLen="1" halPin="in-1" halType="bit"/>
<complexEntry bitLen="1" halPin="in-2" halType="bit"/>
<complexEntry bitLen="1" halPin="in-3" halType="bit"/>
<complexEntry bitLen="1" halPin="in-4" halType="bit"/>
<complexEntry bitLen="1" halPin="in-5" halType="bit"/>
<complexEntry bitLen="1" halPin="in-6" halType="bit"/>
<complexEntry bitLen="10"/>
</pdoEntry>
</pdo>
</syncManager>
</slave>
</master>
</masters>
<masters>
<master idx="0">
<slave idx="0" type="ECT60" name="D1">
<!-- Enable support for Cyclic Synchronous Position mode. -->
<modParam name="enableCSP" value="true"/>
<!-- Enable support for Cyclic Synchronous Velocity mode. -->
<modParam name="enableCSV" value="false"/>
<!-- Maximum stepper Amps. -->
<modParam name="peakCurrent_amps" value="6.0"/>
<!-- Operation mode: openloop, closedloop, or foc. -->
<modParam name="controlMode" value="closedloop"/>
<!-- Number of encoder steps per revolution. -->
<modParam name="encoderResolution" value="4000"/>
<!-- Output 1 use: general, alarm, brake, in-place. -->
<modParam name="output1Func" value="alarm"/>
<!-- Output 2 use: general, alarm, brake, in-place. -->
<modParam name="output2Func" value="brake"/>
<!-- Input 3 use: general, cw-limit, ccw-limit, home, clear-fault, emergency-stop, motor-offline, probe1, probe2 -->
<modParam name="input3Func" value="cw-limit"/>
<!-- Input 4 use: general, cw-limit, ccw-limit, home, clear-fault, emergency-stop, motor-offline, probe1, probe2 -->
<modParam name="input4Func" value="ccw-limit"/>
<!-- Input 5 use: general, cw-limit, ccw-limit, home, clear-fault, emergency-stop, motor-offline, probe1, probe2 -->
<modParam name="input5Func" value="home"/>
<!-- Input 6 use: general, cw-limit, ccw-limit, home, clear-fault, emergency-stop, motor-offline, probe1, probe2 -->
<modParam name="input6Func" value="motor-offline"/>
</slave>
<slave idx="1" type="basic_cia402" vid="0x00000a88" pid="0x0a880013" name="D2">
<!--RS750E(COE)-->
<modParam name="ciaRxPDOEntryLimit" value="9"/>
<modParam name="ciaTxPDOEntryLimit" value="9"/>
<modParam name="enablePP" value="true"/>
<modParam name="enablePV" value="true"/>
<modParam name="enableTQ" value="true"/>
<modParam name="enableHM" value="true"/>
<modParam name="enableCSP" value="true"/>
<modParam name="enableCSV" value="true"/>
<modParam name="enableCST" value="true"/>
<modParam name="enableActualFollowingError" value="true"/>
<modParam name="enableActualTorque" value="true"/>
<modParam name="enableDigitalInput" value="true"/>
<modParam name="digitalInChannels" value="16"/>
<modParam name="enableDigitalOutput" value="true"/>
<modParam name="digitalOutChannels" value="16"/>
<modParam name="enableErrorCode" value="true"/>
<modParam name="enableFollowingErrorTimeout" value="true"/>
<modParam name="enableFollowingErrorWindow" value="true"/>
<modParam name="enableHomeAccel" value="true"/>
<modParam name="enableMaximumCurrent" value="true"/>
<modParam name="enableMaximumTorque" value="true"/>
<modParam name="enablePolarity" value="true"/>
<modParam name="enablePositionDemand" value="true"/>
<modParam name="enablePositioningTime" value="true"/>
<modParam name="enablePositioningWindow" value="true"/>
<modParam name="enableProbeStatus" value="true"/>
<modParam name="enableProfileAccel" value="true"/>
<modParam name="enableProfileDecel" value="true"/>
<modParam name="enableProfileMaxVelocity" value="true"/>
<modParam name="enableProfileVelocity" value="true"/>
<modParam name="enableTargetTorque" value="true"/>
<modParam name="enableTorqueDemand" value="true"/>
<modParam name="enableTorqueSlope" value="true"/>
<modParam name="enableVelocityErrorTime" value="true"/>
<modParam name="enableVelocityErrorWindow" value="true"/>
</slave>
<slave idx="2" type="basic_cia402" vid="0x00000a88" pid="0x0a880013" name="D3">
<!--RS750E(COE)-->
<modParam name="ciaRxPDOEntryLimit" value="9"/>
<modParam name="ciaTxPDOEntryLimit" value="9"/>
<modParam name="enablePP" value="true"/>
<modParam name="enablePV" value="true"/>
<modParam name="enableTQ" value="true"/>
<modParam name="enableHM" value="true"/>
<modParam name="enableCSP" value="true"/>
<modParam name="enableCSV" value="true"/>
<modParam name="enableCST" value="true"/>
<modParam name="enableActualFollowingError" value="true"/>
<modParam name="enableActualTorque" value="true"/>
<modParam name="enableDigitalInput" value="true"/>
<modParam name="digitalInChannels" value="16"/>
<modParam name="enableDigitalOutput" value="true"/>
<modParam name="digitalOutChannels" value="16"/>
<modParam name="enableErrorCode" value="true"/>
<modParam name="enableFollowingErrorTimeout" value="true"/>
<modParam name="enableFollowingErrorWindow" value="true"/>
<modParam name="enableHomeAccel" value="true"/>
<modParam name="enableMaximumCurrent" value="true"/>
<modParam name="enableMaximumTorque" value="true"/>
<modParam name="enablePolarity" value="true"/>
<modParam name="enablePositionDemand" value="true"/>
<modParam name="enablePositioningTime" value="true"/>
<modParam name="enablePositioningWindow" value="true"/>
<modParam name="enableProbeStatus" value="true"/>
<modParam name="enableProfileAccel" value="true"/>
<modParam name="enableProfileDecel" value="true"/>
<modParam name="enableProfileMaxVelocity" value="true"/>
<modParam name="enableProfileVelocity" value="true"/>
<modParam name="enableTargetTorque" value="true"/>
<modParam name="enableTorqueDemand" value="true"/>
<modParam name="enableTorqueSlope" value="true"/>
<modParam name="enableVelocityErrorTime" value="true"/>
<modParam name="enableVelocityErrorWindow" value="true"/>
</slave>
</master>
</masters>
- tommylight
07 Jun 2025 17:47
Replied by tommylight on topic CNC lathe to grinder.
CNC lathe to grinder.
Category: Basic Configuration
I do not have much experience with lathe, but homing near the chuck is just asking for trouble, there is a damn good reason to home as far as possible from the chuck, especially if the machine has a toolchanger.
- tommylight
07 Jun 2025 17:43
Replied by tommylight on topic ESP32/S2/S3 LinuxCNC Controller (6 axis hardware step gen), USB plug-and-play
ESP32/S2/S3 LinuxCNC Controller (6 axis hardware step gen), USB plug-and-play
Category: Computers and Hardware
Try to set networking from serial, if it reboots do not bother with it as it will not work.
Something got left unfinished, the developer has not been around for a year or two, so short of you forking it and fixing it, there is not much use.
It also does not work with ESP32S3 despite him posting everything running on it, it will not compile at all.
Use the hal2udp version of it, the older version worked fine on ESP32Wroom, but the new version also has issues. You can get the older version on github, or try the new version as this one is being developed still.
Something got left unfinished, the developer has not been around for a year or two, so short of you forking it and fixing it, there is not much use.
It also does not work with ESP32S3 despite him posting everything running on it, it will not compile at all.
Use the hal2udp version of it, the older version worked fine on ESP32Wroom, but the new version also has issues. You can get the older version on github, or try the new version as this one is being developed still.
- Aciera
07 Jun 2025 17:35
Replied by Aciera on topic CNC lathe to grinder.
CNC lathe to grinder.
Category: Basic Configuration
If you change your home position then you will also need to change the limit values for the axis/joint in question.
If unsure please post your ini file.
If unsure please post your ini file.
- Chorca
07 Jun 2025 16:48 - 07 Jun 2025 16:54
Replied by Chorca on topic Wiring up for 7i92T reflash
Wiring up for 7i92T reflash
Category: Driver Boards
I got it!
Thank you, after a bunch of messing with this I'd glazed over the 95/92 difference and didn't notice until you called it out.
Turns out my wiring was good, but I had the wrong file being programmed.
Here's what worked for anyone else who might have this problem in the future (in Linux, using a FT2232H Mini Module):
In my case I Just flashed a random user file, as once Pathpilot starts up it will automatically reflash the board with it's necessary firmware.
Thanks again for the help, hope the info I added is helpful if anyone else has the same issue.
Thank you, after a bunch of messing with this I'd glazed over the 95/92 difference and didn't notice until you called it out.
Turns out my wiring was good, but I had the wrong file being programmed.
Here's what worked for anyone else who might have this problem in the future (in Linux, using a FT2232H Mini Module):
- Download latest efinity software, extract to your computer. You need to register for a support account and then request a license, at which point you can download the software.
- Download the 7I92T support software (contains the FPGA binfiles): mesanet.com/software/parallel/7i92t.zip
- Download the seveni92t.zip file and extract it.
- Connect up the FT2232H Mini Module to the 7I92T according to the wiring diagram attached. No connections to CN2 are necessary. Use 5V power to the 7I92T's power terminals, and don't forget to connect the jumper on the FT2232H Mini Module to USB bus power it.
- Change the seveni92t.hex file's extension from .hex to .bit (The software won't accept a .hex file for JTAG programming)
- Source the setup for the efinity software: $ source efinity/2025.1/bin/setup.sh
- Set the board jumpers to Down,Down (to set the IP to 192.168.1.121)
- Power the board on and flash it: $ sh efinity/2025.1/pgm/bin/ftdi_pgm.sh seveni92t.bit -m jtag
- The /DONE light should go out and the green LEDs should blink in sequence as the board starts up, and ethernet should connect, now set your computer's IP to something in the same range as the board's IP (I used 192.168.1.120)
- Use mesaflash to write the fallback firmware (this bin file is from the support zip) : mesaflash --device 7i92t --addr 192.168.1.121 --write 7i92t_16m_fallback.bin --fallback
- Now flash your desired userfile to the user flash area: mesaflash --device 7i92t --addr 192.168.1.121 --write 7i92_<yourfile>.bin
- Power down the card, unhook your connections, and power it back up, everything should function normally.
In my case I Just flashed a random user file, as once Pathpilot starts up it will automatically reflash the board with it's necessary firmware.
Thanks again for the help, hope the info I added is helpful if anyone else has the same issue.
Time to create page: 0.365 seconds