Advanced Search

fully_defined wrote:

spumco wrote:

fully_defined wrote:

 
"Help" is a strong word for what's happening here.

You seem to be getting frustrated.  Maybe I can help.

Correct me if I'm wrong, but your situation is that you have a Mesa 7i96s and Clearpath SDSK motors.  You want to:

• Set some rational values for max velocity and accel
• Connect the HLFB pins to the 7i96s
• Make LCNC do something with the HLFB signals
  
  
  Have I got it right?
  
  
  
  
  Yes, and thank you for engaging.
  
  Those points are just what are directly in front of me, right now. It's mostly because I am at the pncconf stage, and there isn't a selection for setting the pins for drive fault there. I am not hung up on moving on, as long as I know where I need to set this function. I have LinuxCNC forum people telling me they have no idea how Clearpath HLFB works and Teknic saying they have no idea how LinuxCNC works, and here I am, stuck in the middle. That's why I thought maybe seeing an existing configuration would skip the middlemen and I could just copy someone else's homework.
  
  Beyond that, I also need to know what to expect when homing the dual-Y gantry axis. There is more I'd like to learn about autosquaring too, but that's just one thing out of a long list.

Some of these features will likely not be supported by pnccconf

It seems this post gives you some options for HLFB. 
www.forum.linuxcnc.org/10-advanced-confi...with-hlfb-mesa-7i76e
I think I would use servo-on and use  a charge pump which I think pncconf supports

The drive error is connected to 
joint.N.amp-fault-in 
ref: linuxcnc.org/docs/stable/html/man/man9/m....9.html#JOINT%20PINS

Squaring the gantry is dealt with when homing
linuxcnc.org/docs/stable/html/config/ini-homing.html
Paired joints (eg your gantry motors) will have a negative HOME_SEQUENCE of the same value
Usually you will also use a HOME_OFFSET
You can  square the gantry by editing the HOME_OFFSETS. eg  if one side is out by 2mm, the HOME_OFFSET needs be 2mm different to the other side.


 

that works, thanks phil.

when I say works, only the first time you open a filedialog (or multiple times within 1-2 seconds of opening axis) then it stops working.
putting this line in my userlive_update makes it work only sometimes

possibly need to do a python instead having it inside of a separate tcl file?

You would need to use firmware that has a PWM output to drive
your PWM to analog circuit, like 7i96d_1pwm.bit.

This firmware replaces stepgen4 STEP and DIR with PWM 0
PWM/DIR

To use pncconf to set up the spindle PWM, you would also need to use
the discover option (so pncconf knows there's a PWMGEN available)


 

Interesting. So that was unmodified OS install, and then a LinuxCNC 2.93 Uspace install? It's great that that worked.

You need the 7i96S for spindle control.

You may have purchased the wrong one by mistake. I almost did that!

I'm not sure yet. I installed Debian Trixie on an i7 the other day. It uses 6.12.6. I installed Linuxcnc on it from the Debian repositories (which also installs linux-image-rt-arm64 as a dependency) and everything worked correctly.It might just be an ARM problem,

Hey, everyone.I'm doing a linuxcnc conversion on a ShopSabre 23 machine. Just got a 7i96 board in the mail and have been setting it up on my desk. It's been good so far, got the relays and endstops working. Unfortunately the spindle is giving me some trouble. We have an 18k rpm spindle driven by Mitsubishi A800 VFD which accepts 5-10 analog speed control.

I was under the impression that I would be able to convert PWM into analog voltage with this card and that's how I set it up in the Pncconf 18000 rpm at 5v, but the rpm readout in qtdragon only goes up to 500 for some reason. The spindle setup looks like another stepper config and I'm confused about the scale. I've read pretty much every spindle related post here which lead me to more confusion since everybody has different hardware.I haven't flashed any firmware on the card, just working with the stock one that it came with.I have a PWM to analog converter board

Here is the VFD manual   you can find the speed control on page 115

Can somebody please steer me into the right direction?I will include my ini an hal files just in case.

Later versions of Debian (we use debian 12 bookworm) requires careful optimisation on 2 core machines. I would suggest a 4 core Celeron, 4gb RAM, any sized SSD

Thanks Rod,

I gave this a try because I was excited to read that "This release includes realtime support (PREEMPT_RT), a feature that has been in the works for 20 years." So is there a bug in the PREEMPT_RT support in the 6.12 kernel, or is it simply not implemented the way LinuxCNC has come to expect? Obviously LinuxCNC needs to support a working standard.

Yes. you could try sudo apt install linux-image-rt-arm64

Yes the kernel needs to be specifically built to support preempt_rt even in kernel 6.12
It seems that on the Pi a default 6.12 RT kernel build is not recognised by linuxcnc unless the kernel has additional settings that are provided in the patch. This may end up being fixed by the kernel developers in later versions

This may not be relevant to you but building a custom image that includes Linuxcnc is not trivial and requires building a kernel from source so it needs to be a RT kernel.


 

I'm trying to do this with an Rpi 4 and I'm seeing the same thing. I can find the PID of latency-histogr. Then run chrt -p PID which reports that current scheduling policy as SCHED_OTHER. Then run chrt -f -p PID which does change the scheduling policy to SCHED_FIFO.

But all I did (hoped was necessary) was to update the kernel. sudo rpi-update next, thne reboot. Must one actually build the kernel with a patch? That seems odd if the kernel offers full RT support.

Oh, it's part of the Kernel files isn't it. Ugh.

Roy,

I've updated the kernel to 6.12.8 on an Rpi 4, and I'm seeing pretty much the same behavior. However, I'm not finding the file you patched anywhere on the system? sudo find / -print | grep ksysfs finds nothing.

Thanks,

Gene

What I am trying to do: in a 1" x 1" square workpiece, cut a .68" ID hole starting at (.16",.16").  The mill is .125" nminal diameter.  It is actually .122".

The gCode I tried, producing a hole that is too small:

g1 x.16 y.16 f25
g1 z0 f25
g2 i.-34