Advanced Search

By error I mean:

What does LinuxCNC report?

Can you post the complete hal file?

I meant it as an error — I’m not sure how to configure it, what I’m doing wrong, and why the AXIS_A code is written incorrectly. please

Axis works fine, QT dragon also works fine. Its just Probe Basic

2.9.4

I don't see this in 2.9.7 with Axis (I don't have a Probe Basic setup to test with)

Can you see if you see the same issue in Axis with one of the sim configs? (This won't affect your real config)

I am looking at disable a pushbutton during program runtime. No idea how to do. It is connected to python module, and should not
be enabled during runtime. Is there a setting, it gets greyed out, eg. like mdi-button?

What version of linuxcnc are you using?

There is a version of nativecam in a linuxcnc branch that mostly works.
It's a work in very slow progress. It's based on Qt.
github.com/LinuxCNC/linuxcnc/tree/qt_ncam

There is also another project I've seem on the forum that keeps it gtk based and just updates it to python3 and whatever pygtk is called now.

But I would suggest you just finish what you have built, as it seems you are pretty far along.
You could always convert it to another platform later.

Thanks guys.
I did do:
apt-get update
before I started. 

I just ran it update again to check, and the distro is wheezy. 

I watched Rods video, but don't want to update to LCNC 2.8 or above as I have had a working system, and don't have the time to play around getting it configured again for the joints change, mesa card latency etc.
Cheers,
Mark
 

Mr.Rodw big fan of your work! I wouldnt disagree with that however if there is solution to continue to use ER16 tooling (I should have mentioned that in the og post) then I would rather do that then invest in a TTS spindle and TTS collets. I know there is a solution to this

What is the actual error?

NativeCAM is an interesting project, but it has a fundamental issue today:the codebase is very old (Python 2, GTK2/PyGTK) and has not been actively maintained for quite some time. I have taken a closer look at the project locally and am currently trying to get it running on a modern system (Debian 13, Python 3, LinuxCNC 2.10). At the moment it already fails at the basic dependency level, since Python 2 and PyGTK are essentially unavailable on current distributions. Before discussing any functional extensions, a significant porting effort is required (Python 3, GTK3/gi).Only if NativeCAM can be made stable on a modern system does it make sense to consider whether and how the lathe functionality could be extended or reimplemented. For now, my focus is not on new features, but solely on determining whether the project is still technically viable as a future foundation.

Yes, you may need to use pkluart (RX and TX) version 2 if not running the latest LinuxCNC

Hello,

I am using LinuxCNC with a Mesa 7i43 card.
Axes X, Y and Z are working correctly.

I need help with configuring Axis A (4th axis),
which I use as an auxiliary axis and want to control
with a stepper motor using STEP/DIR signals.

Hardware:
- LinuxCNC
- Mesa 7i43
- Stepper driver – blue digital stepper driver, Leadshine DM542 / DM556 type
  (or compatible clone) with PUL+, PUL-, DIR+, DIR-, ENA+, ENA- inputs
- 2-phase stepper motor

Stepper driver wiring:
- PUL+  -> Mesa P3 pin 25
- PUL-  -> Mesa P3 pin 26
- DIR+  -> Mesa P3 pin 27
- DIR-  -> Mesa P3 pin 28
- ENA+  -> Mesa P3 pin 29
- ENA-  -> Mesa P3 pin 30

The driver is configured by DIP switches for microstepping
(e.g. 3200 pulses per revolution).

Axis A is configured in the HAL file as a stepper axis
using hm2 stepgen (stepgen.00).

I need advice on how to correctly modify the HAL file
so that Axis A works properly as a stepper axis
with the Mesa 7i43.

I am attaching my complete HAL file.

Thank you.


#*******************
#  AXIS A
#*******************

setp   pid.a.Pgain     [AXIS_3]P
setp   pid.a.Igain     [AXIS_3]I
setp   pid.a.Dgain     [AXIS_3]D
setp   pid.a.bias      [AXIS_3]BIAS
setp   pid.a.FF0       [AXIS_3]FF0
setp   pid.a.FF1       [AXIS_3]FF1
setp   pid.a.FF2       [AXIS_3]FF2
setp   pid.a.deadband  [AXIS_3]DEADBAND
setp   pid.a.maxoutput [AXIS_3]MAX_OUTPUT
setp   pid.a.error-previous-target true
setp   pid.a.maxerror .0005

net a-index-enable  <=> pid.a.index-enable
net a-enable        =>  pid.a.enable
net a-pos-cmd       =>  pid.a.command
net a-vel-cmd       =>  pid.a.command-deriv
net a-pos-fb        =>  pid.a.feedback
net a-output        =>  pid.a.output

# Step Gen signals/setup

setp   hm2_7i43.0.stepgen.00.dirsetup        [AXIS_3]DIRSETUP
setp   hm2_7i43.0.stepgen.00.dirhold         [AXIS_3]DIRHOLD
setp   hm2_7i43.0.stepgen.00.steplen         [AXIS_3]STEPLEN
setp   hm2_7i43.0.stepgen.00.stepspace       [AXIS_3]STEPSPACE
setp   hm2_7i43.0.stepgen.00.position-scale  [AXIS_3]STEP_SCALE
setp   hm2_7i43.0.stepgen.00.step_type        0
setp   hm2_7i43.0.stepgen.00.control-type     1
setp   hm2_7i43.0.stepgen.00.maxaccel         [AXIS_3]STEPGEN_MAXACCEL
setp   hm2_7i43.0.stepgen.00.maxvel           [AXIS_3]STEPGEN_MAXVEL

# ---closedloop stepper signals---

net a-pos-cmd    <= axis.3.motor-pos-cmd
net a-vel-cmd    <= axis.3.joint-vel-cmd
net a-output     => hm2_7i43.0.stepgen.00.velocity-cmd
net a-pos-fb     <= hm2_7i43.0.stepgen.00.position-fb
net a-pos-fb     => axis.3.motor-pos-fb
net a-enable     <= axis.3.amp-enable-out
net a-enable     => hm2_7i43.0.stepgen.00.enable

# ---setup home / limit switch signals---

net a-home-sw     =>  axis.3.home-sw-in
net a-neg-limit     =>  axis.3.neg-lim-sw-in
net a-pos-limit     =>  axis.3.pos-lim-sw-in



 

Usually due to naming errors, like spindle.enable should be spindle.0.enable, axis should be joints, etc.