Advanced Search

No, I was just setting up. I have a couple toggle switches working on gpio but that’s it. I was just getting excited I could see it talking through halshow. No servo/spindle drivers yet.
I figured the MPGs should have been the next easiest thing to do

Hi, great tool — thanks for sharing it!

I ran into two issues with the generated G-code on a standard LinuxCNC setup (not PathPilot), both easy to fix:

**1. D and I parameters are swapped in the G71/G72 line**

The generator outputs:
```
G71 Q#### D{stock_allow} I{doc} R... F...
```
But LinuxCNC G71 expects `D` = depth of cut per pass and `I` = finish stock allowance — the opposite of what is currently generated. With the values swapped, the cycle runs with a 0.2 mm DOC and a 2 mm finish allowance instead of the other way around.

**2. X and Z arguments on the G71/G72 line cause the machine to stall**

The generator adds `X{start_x} Z{start_z}` directly on the G71 line:
```
G71 Q#### X30.000 Z2.000 D... I... R... F...
```
LinuxCNC does not accept X/Z on the canned cycle line itself — the approach is already handled by the preceding `G0`. With these arguments present the spindle starts but the machine does not move.

**Fix** — patch profiler.py (4 occurrences):
```bash
sed -i 's/X{start_x:.3f} Z{start_z:.3f} D{p.stock_allow:.3f} I{p.doc:.3f}/D{p.doc:.3f} I{p.stock_allow:.3f}/g' profiler.py
```

After the fix the output looks like:
```
G0 X30.000 Z2.000
G71 Q#### D0.500 I0.200 R1.000 F100.0
G70 Q#### F50.0
```
Which runs correctly on LinuxCNC 2.10 with AXIS.

Hope this helps, and thanks again for the project!

I did, unfortunately with SyncToRefclock set to false, the dc-phased pin starts flickering.

the reset counter doesnt go up either.
with it set to true, the rest counter goes to 1 or 2 per lcnc launch.
what ive also found, without every driver being ready, the dc-phased pin is already HIGH. Is that supposed to happen?

Was this a fully working system before you added the MPG?
 

moved to a different PCI slot, no change in behavior
moved to enable breakout power (W1, W2 up) no change in behavior
tried lspci -vv, didnt find the board. Sucessfully enabled board with setpci, then lspci confirmed board was not disabled.
...tried mesaflash, and mesaflash still returns no 5i25 board found.
did not mess with W3 on the 6i25

EDIT: i have completely removed the encoders from the 7i77 and later removed the 7i77 from the 6i25 in an effort to at least see if the 6i25 could be found.
I would also like to point out that if I connect the 7i77 i am in fact getting 5v from the 6i25 (if enabled breakout power) ...i probed with a multimeter (on the 7i77) the encoder TB and also probed on TB1. So I would say the 5v power seems to be there...


I am beginning to think i have a problem. I do have an ethernet port. should i consider a 7i97? Or i might be money ahead trying a whole new PC at this point.

The whole encoder thing suggests a  5V power issue.
(short or mis-connection)

The hard crash may only happen when LinuxCNC fully starts meaning the correct firmware is installed

W3 sets the I/O pin 5V tolerance option, it should be left on the defauly "UP" position

To be clear, i am not hard crashing anymore after installing a new 6i25 that i got last week. I am not sure what firmware is on either board.

I could try another motherboard...just a ton of work. what does the w3 jumper do on the 6i25?
i may try going back to breakout power enabled on the 6i25. It didnt like the differential encoders when I did that, but at least i was getting things through the 7i77.

I wonder if somehow the motherboard was damaged in some way at the first fault.
Because this is quite odd behaviour.

I wonder if you would get the same hard crash fault if the new 6I25 had the correct firmware?

ok, I used the setpci command, seems to have worked, I no longer get a disabled on the lspci command:
 

however, the very next thing I do is try to run mesaflash, and again it cannot find the card: 


I have adjusted all the PCI setting I could find in BIOS, no luck there either. The motherboard does not have PCIe jumpers, checked that as well. Everything was set to GEN1 just the same

Hello,
I am sorry my bad ...I am too much focusing in something and then I failing in others ...

I have tested some toolpaths till now ... Infinite spikes are gone at tp 1 and 2 at paths where it defenetely were in the past ... I noticed that TP1 during its startup with testing code 1_1001.ngc spiking much with servo time (if we take 250us as our goal - for 1ms it is fine) ..

Default TP0 and TP2 do not this behaviour ...

dark blue from scope pictures in the attachments then TP1 is spiking at each segment change over 200us during cloud of points its repeating spiking too.. 

I notice that switching between TP1 and 2 is not possible sometimes it creates error and switch me back to TP2 from TP1

thank you E.

I'm near complete converting another manual lathe (Standard Modern this time) to LinuxCNC.

These programmable keypads are convenient for commonly used key entries to Axis/MDI. From LinuxCNCs perspective they are just another keyboard.

I have a few spare keys and I would like to use one to activate a Mesa output. I can program the key to any key or even key sequence.

Is there a way to make this happen in HAL?

IIRC there is a file somewhere that either defines or lets you redefine key codes, I'm not sure if that will come into play? I suppose choosing an oddball key for this might be advantageous, so a typing a key on the regular keyboard does not inadvertently activate the Mesa output. 

 

Connect your external power button to halui.machine.on, note the estop must be released before pressing the power button.

JT

andrax wrote:

Er, no. It’s not that simple; LinuxCNC isn’t plug-and-play. If you don’t have any prior knowledge, you should put the A6 aside for now and start with simple stepper motors. You’ll first need to learn how the system works and what each component does. With EtherCAT, you’re moving beyond the hobbyist level, and even professionals sometimes find it frustrating.

I only broke 4 mice from throwing them in anger... its fiiiinnnee.

In seriousness though, I find its less about beginner vs expert in CNC stuff, and more about if you are well versed in linux usage. Most of my troubles setting up were because the instructions just assume you know everything about linux already and leave a lot of critical details out. I am working with one of my customers to trying an make a true step by step guide.

If you do know "nothing", step and direction with a mesa card is generally pretty safe cause its mostly done by a wizard. You aren't mucking in the terminal or doing much editing in HAL.

(also important to note ethercat in linuxcnc has some quirks too, its not quite "final" in my opinion)

The following is the Python interface so it forces you to use joint number before homing then use index of axis after homing.

JT

It's easier to start with a Mesa card for sure.
You have the pncconf utility that will give you a working configuration.
Once you have the Mesa config working, it's not that hard to
replace the motion part with EtherCAT. Cut and paste, though.