Advanced Search

I’d try google and any of Jeff Gerlings stuff on YouTube.

But honestly I think you’re using the wrong tool, the RPi5, for the job.

The small Lenovo’s that are popping up around eBay and such are a far better solution.

Hi Grotius,
i have a few spare ethercat stepper drives by leadshine (6amps) and a couple 230v operates servo drive and motors (750 watts) by Veichi that I could send to you for your machine trials.

This way you will be able to isolate the effects of pulse and direction jitter over ethercat on your machine.

Let me know our DM and we can set something up.
- automata

I think fom memory you need to set a udev rule for it to persist on a restart. Its covered in the sticky.

What are the voltage and current ratings of the existing DC motor on the Z axis?

You can probably just delete all hal lines with pwm in them to get running.

Its likely the 7I95T configuration boilerplate came from the 7I96S which always
has at least 1 PWM channel

Linuxcnc works fine with Raspberry Pi 5, but when I watch it on the GUI, the positions are a bit delayed. When I use it with a PC, there is no problem. It communicates with 6 servo drivers and a PLC. It would probably be better if its speed increased a bit.

@PCW - No configs in the Spindle tab. I set one of the outputs to Spindle brake. That's all. All else was default. I will track down the secure boot problem.

I think I may give up on the hypertherm thc.
I went ahead and ordered a thcad but I gotta figure out the z axis. 
I have the hypertherm dc h bridge z axis or was offered a stepper powered z axis from a candcnc setup.
I have a mesa 7i97t, but I’m not sure if I can control either of these z axis’s with it, since it has analog outputs for servos.
I assume getting the stepper axis going would be easier than the h bridge, but I’m often wrong.
Or maybe I should just buy one.
I also know I’ll need a driver. I have an old gecko 540 I could potentially use, but maybe a single axis driver would be better suited. One that’ll work with 7i97t’s analog signals? Or maybe an h bridge driver makes sense?
What do you guys think? 

1. The card name in the hal file is 7i95, not 7i95t

2. Did you setup a pwmgen for spindle or some other use?
(there is reference to  non-existent pwm hardware in the hal file):

./main.hal:66: Pin 'hm2_7i95.0.pwmgen.00.enable' does not exist

3. You don't need a num_pwmgens statement anywhere

(unless you want to disable one that actually exists in the hardware

4. There is an unrelated issue with your setup, likely related to secure boot being enabled in your BIOS:

iopl() failed: Operation not permitted
cannot gain I/O privileges - forgot 'sudo make setuid' or using secure boot?
 

This worked...

Commented out all mentions of "pwngen". There were three, one for each axis.

#net joint-0-enable => hm2_[MESA](BOARD).0.pwmgen.00.enable

There are several lines starting with loadrt.. Can't find mentions of num_pwn=0. So I added it to just try it out.

I tried this one..
loadrt [EMCMOT](EMCMOT) servo_period_nsec=[EMCMOT](SERVO_PERIOD) num_joints=[KINS](JOINTS) num_pwm=0

and then this one in the config part...
# hostmot2 driver
loadrt hostmot2
loadrt [HM2](DRIVER) board_ip=[HM2](ADDRESS) config="num_encoders=6 num_stepgens=6 sserial_port_0=00000000"

both time returned with the error "unknown parameter, 'num_pwn=0'"

I'm putting the final touches on an external push-button control board that has a big Estop button as well as buttons to do a host of other things, details here =>

forum.linuxcnc.org/21-axis/53701-please-...e-this-control-board

I mostly use my mill for "one of" prototyping so it's really common for me to interact mostly with the control board. So I prefer to use the control board buttons for as many commonly used things as possible. At the moment I can do most everything I want from the control board except reset the E-Stop. I would prefer to be able to do that without clicking in the GUI.

There are no hardware PWM in 7i95T as far as i know, so how did you end up with it in hal file? And also there are mentions of parallel port in the error report, and this is the second time i am seeing this error on MesaCT configurations, it really should not be there.
As far as i can figure out, none are of your making, so for now just edit the hal file and set the num_pwm=0 instead of whatever the number is there, should be near the top of the file and the line starts with "loadrt"

I built a configuration to just learn from. I used the quick start xyz configuration. The debug section of the report shows a board 7i95 (without the T). So I edited the .ini to include the T, but it causes errors elsewhere. Attached the .ini and report file. I don't really know what else to do except to ask here.

Mesa 7i95T, LinuxCNC 2.9.3, MesaCT 2.1.6

Thanks, and please help a newbie out.

Aciera wrote:

I would try to use custom Mcodes/ subroutines directly and avoid using the python mdi command.
 

Can you elaborate on how to do that? I'm invoking these from a VCP, buttons bound to Python code.