Advanced Search

in many cases autotune broke parameterisation, for example Siemens s120 with their servos working like a charm, but if You use third party supplier of servos, just be sure You are using parameters delivered by Your supplier of servo, if supplier have not parameters for Your driver, don't take it, auto tune mostly broke settings, same manufacturer of drive and servo have to work, but i think it can be price reason (in comparison to Panasonic MINAS A6B for example)

It wont work,(the simple explanation since you don't understand\haven't read the links) the RPi SOC doesn't do the memory\port mapping the parallel ports require.

When searching about this a thread I started came up, regarding SPI, mentioned parallel ports don't work with the RPi.

forum.linuxcnc.org/18-computer/51748-eoi...rpi5?start=10#303031

Rather than banging your head against a wall look at the Linuxcnc RIO project. Or get a Mesa 7i90HD, it's really quite cheap if you are based in the USA.
store.mesanet.com/index.php?route=produc...oduct&product_id=291

I think I have wrapped my head around my stepper motor and limit switch wiring. Regarding the spindle, I have a few questions:

The inverter is a woods eTrac x2c and the manual offers a nearly overwhelming number of options. I was never able to see the spindle working with the stock
AMC controller. I have attached the relevant table from the inverter manual and it seems like I should be able to use the analog spindle interface to provide 0-5vdc signal for speed control (vin). Do I simply use inputs on the 7i96 to conteol fwd/rev and a ground connected to the inverter common? Is that all there is to it?

The original wiring from the AMC controller to the inverter is somewhat different and it isn’t obvious that the AMC was actually able to control the spindle speed. It is connected to use 4 preset spindle speeds and the AMC has wires indicating an acceleration/deceleration signal, as well as some connections to NO and RCM.

 

 

Thanks. I tried all three variants on both parport cards. Did not work.
Let's not spend any more time on this. appreciate everyone's time and effort.
I'll likely jump back in this fall when I have more time.

I deleted my previous post as i missed a crucial point, sorry for the confusion.

Possibly. I have not tried it but it will be up to the devs to increment the Python version. I thought that would have been done as linuxcnc 2.9.4 is in Debian 13 natively.

M3 S10000 ; works, spindle starts and spins up
M5 ; works, spindle stops
G53 G1 F4000 Z-10 ; Spindle does not move and GCode interpreter seems to be hung!

Is spindle-at-speed true? if not, pretty sure this will hang waiting for spindle-at-speed to be true.

One advantage, If you have step/dir servos, returning the position information to LinuxCNC
allows LinuxCNC to monitor the actual following error during operation.

DELETED as i missed a crucial point so my reply was not correct.
See PCW's reply below

OK, so an update on this issue.
Tonight I had some time to isolate where the problem is happening, and I can bring it down to just a couple of commands.

I start up Linux CNC, toggle the CNC on and home it, this is my start point.

Now in the MDI window I type the following

G53 G1 F4000 Z-10 ; This works, carriage moves down 
G53 G1 F4000 Z0 ; This works, carriage moves up 

I can repeat the above multiple times, the carriage moves up and down as expected.

BUT, if I type the following (either after typing the above or after a clean start)

M3 S10000 ; works, spindle starts and spins up
M5 ; works, spindle stops
G53 G1 F4000 Z-10 ; Spindle does not move and GCode interpreter seems to be hung!

On the console I see the following output 

mdi_execute_hook: MDI command 'M5' done (remaining: 0)
Issuing EMC_TASK_PLAN_EXECUTE --      (  +509,+280,   +23,G53\032G1\032F4000\032Z-10,)
emcTaskPlanLevel() returned 0
NML_INTERP_LIST(0x55afd11daa60)::append(nml_msg_ptr{size=208,type=EMC_TRAJ_LINEAR_MOVE}) : list_size=1, line_number=0
emcTaskPlanExecute(G53 G1 F4000 Z-10) returned 0
emcTaskPlanLevel() returned 0
NML_INTERP_LIST(0x55afd11daa60)::get(): {size=208, type=EMC_TRAJ_LINEAR_MOVE}, list_size=0
emcTaskPlanLevel() returned 0
Issuing EMC_TRAJ_LINEAR_MOVE --      (  +220,+208,    +0,605.000000,400.000000,-10.000000,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000,    +2,25.000000,25.000000,750.000000,    +0,    -1,)

I've attached the full console output from the linuxcnc command 
 
 

Oh good, and oh .... i don't know....

Yes that is it, and sorry forgot to mention, read until Host Interface section.

Thanks for the reply. I have LinuxCNC installed on a computer now but I’m still waiting for the Mesa card to arrive (should be this week). When you wrote ‘Mesa manual’ do you mean the ‘7i96s Ethernet Step/Dir Motion control interface’ document? If so, I’ve read it but will admit to not fully understanding all of it (yet).

Oh! I thought feedback would be required for coordinated motion.

What are the limitations or benefits without/with encoder feedback to LinuxCNC+Mesa?

Yes, to have all servos/drives start acting on new data/position data at the same time.
For servos and drives you want distributed clock mode.

The following error in LinuxCNC with EtherCat is somewhat superficial.
If the drive offers a following error, use that, if possible.