Search Results (Searched for: )
- 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.
- beauxnez
- beauxnez
07 Jun 2025 16:39 - 07 Jun 2025 16:44
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
Hello,I don't understand what's wrong. I think I connected the card to the ESP32 correctly, but I get an error message.
- TheTinkeringMechanic1
- TheTinkeringMechanic1
07 Jun 2025 16:28 - 07 Jun 2025 19:42
CNC lathe to grinder. was created by TheTinkeringMechanic1
CNC lathe to grinder.
Category: Basic Configuration
Greetings. At my work place, we recently acquired a CNC converted lathe running Knuth LinuxCNC 3.4.6.
There's a few changes we need to make for it to suit our needs. First was to set it so it would home near the chuck. I already moved the homing dogs and the limit switch orientations corrected the saddle direction so it homes out near the chuck as desired. I do understand this homing orientation is the opposite of what's commonly done on a lathe. The reason for this is the lathe is being converted into a grinder for urethane rollers. In this case we need to have the saddle home near the chuck to prevent having to move (or crash into) the tail stock so it can home every time we need to home it. We're replacing the chuck with a collet head with an internal stop for repeatability (provided our cores are to the desired spec, but that's another story)
I'm still familiarizing myself with LinuxCNC and despite my best efforts so far, I seem to have hit a wall. The issue I have is although I have it set to home safely near the chuck side, in the preview grid the position marker moves in the opposite direction. The saddle moves right the marker in preview moves left. Prior to setting XZ to X-Z it would try to travel off the grid altogether and soft stop would attempt to prevent it from moving beyond the preview boarder. You can see it in the image I attached how X & Z are positioned near the lower right of the grid. Is there a way to get the preview to place Z on lower left of the grid?
Thanks in advance.
There's a few changes we need to make for it to suit our needs. First was to set it so it would home near the chuck. I already moved the homing dogs and the limit switch orientations corrected the saddle direction so it homes out near the chuck as desired. I do understand this homing orientation is the opposite of what's commonly done on a lathe. The reason for this is the lathe is being converted into a grinder for urethane rollers. In this case we need to have the saddle home near the chuck to prevent having to move (or crash into) the tail stock so it can home every time we need to home it. We're replacing the chuck with a collet head with an internal stop for repeatability (provided our cores are to the desired spec, but that's another story)
I'm still familiarizing myself with LinuxCNC and despite my best efforts so far, I seem to have hit a wall. The issue I have is although I have it set to home safely near the chuck side, in the preview grid the position marker moves in the opposite direction. The saddle moves right the marker in preview moves left. Prior to setting XZ to X-Z it would try to travel off the grid altogether and soft stop would attempt to prevent it from moving beyond the preview boarder. You can see it in the image I attached how X & Z are positioned near the lower right of the grid. Is there a way to get the preview to place Z on lower left of the grid?
Thanks in advance.
- Groovecooper1
07 Jun 2025 15:56
Replied by Groovecooper1 on topic Need help with Linux 2.5 on a CNC lathe
Need help with Linux 2.5 on a CNC lathe
Category: General LinuxCNC Questions
will try that, thank you!
- UweSauter
- UweSauter
07 Jun 2025 15:03 - 07 Jun 2025 15:15
Replied by UweSauter on topic Umbau der Steuerung auf LinuxCNC + EtherCAT
Umbau der Steuerung auf LinuxCNC + EtherCAT
Category: Deutsch
Euch beiden vielen Dank schon mal.
Ich möchte die Frage nach dem Steuerungsrechner jetzt aber erst einmal in den Hintergrund stellen. Es macht für den Anfang keinen Unterschied, ob ich jetzt meinem Laptop oder den Raspi für die Einrichtung verwende. Und sobald ich eine lauffähige Konfiguration gefunden habe ist diese auch schnell auf einen anderen Rechner umgezogen.
Wahrscheinlich habe ich mir schlecht ausgedrückt aber mein primäres Problem besteht gerade darin, dass mir noch nicht klar ist, womit ich meine ganzen Ein- und Ausgänge verbinden muss. Ich kann mir mit "halrun: show pin" für die EtherCAT Komponenten und das Handrad die entspechenden Ein- und Ausgänge anzeigen lassen. Aber ich habe noch nirgends gefunden, wie ich mir die Ein- und Ausgänge des Regelungsthreads oder der Pfadberechnung anzeigen lassen kann. Damit ich eben für die ganzen anzulegenden Signalpfade (oder wie übersetzt ihr das "net"?) finde.
Gleiches gilt auch für die grafischen Oberflächen. Soweit ich verstanden habe, stellen die GUIs ja auch Pins zur Verfügung, um z.B. den Status eines Eingangssignals einzeigen lassen zu können.
Ein Beispiel anhand eines der Servos. Ich stelle mir den Regelkreis gerade so vor:
Mir verschließt sich aber noch, wie ich das miteinander verbinde…
Schöne Pfingsten,
Uwe
Ich möchte die Frage nach dem Steuerungsrechner jetzt aber erst einmal in den Hintergrund stellen. Es macht für den Anfang keinen Unterschied, ob ich jetzt meinem Laptop oder den Raspi für die Einrichtung verwende. Und sobald ich eine lauffähige Konfiguration gefunden habe ist diese auch schnell auf einen anderen Rechner umgezogen.
Wahrscheinlich habe ich mir schlecht ausgedrückt aber mein primäres Problem besteht gerade darin, dass mir noch nicht klar ist, womit ich meine ganzen Ein- und Ausgänge verbinden muss. Ich kann mir mit "halrun: show pin" für die EtherCAT Komponenten und das Handrad die entspechenden Ein- und Ausgänge anzeigen lassen. Aber ich habe noch nirgends gefunden, wie ich mir die Ein- und Ausgänge des Regelungsthreads oder der Pfadberechnung anzeigen lassen kann. Damit ich eben für die ganzen anzulegenden Signalpfade (oder wie übersetzt ihr das "net"?) finde.
Gleiches gilt auch für die grafischen Oberflächen. Soweit ich verstanden habe, stellen die GUIs ja auch Pins zur Verfügung, um z.B. den Status eines Eingangssignals einzeigen lassen zu können.
Ein Beispiel anhand eines der Servos. Ich stelle mir den Regelkreis gerade so vor:
┌───► Servo─────┐
│ │
│ ▼
lcec lcec
▲ │
│ │
│ ▼
cia402 cia402
▲ │
│ │
│ │
pid(?) │
▲ │
└───motion ◄────┘
Mir verschließt sich aber noch, wie ich das miteinander verbinde…
Schöne Pfingsten,
Uwe
- tommylight
07 Jun 2025 14:07
Replied by tommylight on topic QTPlasmac pierce delay handling
QTPlasmac pierce delay handling
Category: Plasmac
See what voltage you get when cutting and how much it fluctuates, then set the ARC low and high to about 20-30V above and below.
Do a lot of tests till you get it to have cuts without interruption and no false OK signal at start.
And yes, the voltage will differ with thickness and feed rate, but usually under 10V difference on all of my machines (over 15 machines) for materials from 1.8mm to 6mm.
Do a lot of tests till you get it to have cuts without interruption and no false OK signal at start.
And yes, the voltage will differ with thickness and feed rate, but usually under 10V difference on all of my machines (over 15 machines) for materials from 1.8mm to 6mm.
- PCW
07 Jun 2025 13:34
Replied by PCW on topic Wiring up for 7i92T reflash
Wiring up for 7i92T reflash
Category: Driver Boards
What card do you actually have?
(the title says 7I92T but you mention init95t)
Do you get the user (green) LED blink and Ethernet link lights illuminated after JTAG programming?
(the title says 7I92T but you mention init95t)
Do you get the user (green) LED blink and Ethernet link lights illuminated after JTAG programming?
Time to create page: 0.432 seconds