Advanced Search

The LY mill has 300 (X) by 400 (Y) mm travel and about 180 in Z. The overall machine is 1000 mm deep, 600 wide, and 600 high. Weight is 375 kg.

Re-capping a few boards seems manageable. There is less patience for old electronics. I think it reflects a lack of widespread electronics knowledge.

That PC stand is something else.

These were sold as engraving machines. I assume a spindle/VFD upgrade is in order?Will you be doing anything beyond aluminum?

Are you saying you do not get a consistent velocity reading
when the encoder is being rotated at a constant rate?

 

System:

• CNC lathe with X and Z axes, stepper motors, Mesa 7i96S
• LinuxCNC 2.9.4, config generated by PnCConf, then manually edited
• Logitech Dual Action gamepad via hal_input (-KRAL Dual)
• GUIs tried: axis and gmoccapy, no difference
• Goal: proportional jogging (analog, stick halfway = half speed)
• Only Z axis motor is connected, X is not connected at the moment. Jog via GUI (mouse) works fine.

Symptoms and troubleshooting so far:

• Gamepad is detected correctly (evtest, halmeter both show correct values).
• In halmeter/halshow, input.0.abs-x-position and input.0.abs-rz-position change smoothly with stick movement. Scaling set so left = -1, center = 0, right = +1.
• Connections in custom.hal: net jog-z input.0.abs-x-position => halui.axis.z.analog and the same for X.
• The analog pins halui.axis.z.analog and halui.axis.x.analog show the values in halmeter.
• Jogging with GUI works, motors run as expected.
• If I jog with GUI and simultaneously move the stick in the opposite direction, the axis stops moving. This proves the analog value reaches the right place.
• No matter the scaling (tried 1, 127, 32767, etc.), values are correct in HAL but motors do not move from analog stick alone.
• I have NOT tried digital jogging via button/plus/minus, as I only want analog.
• No hardware issue: GUI jog moves motors.
• Estop, enable, limits, homing are all checked and fine.
• All HAL pins/signals seem correct, no missing values.
• No difference with gmoccapy GUI.

Relevant config snippets:
custom.hal:
loadusr -W hal_input -KRAL Dual
net jog-z input.0.abs-x-position => halui.axis.z.analog
net jog-x input.0.abs-rz-position => halui.axis.x.analog369.hal:
net jog-x-pos halui.axis.x.plus
net jog-x-neg halui.axis.x.minus
net jog-z-pos halui.axis.z.plus
net jog-z-neg halui.axis.z.minus
net jog-selected-pos halui.axis.selected.plus
net jog-selected-neg halui.axis.selected.minus
net jog-speed halui.axis.jog-speedini:
[HAL]
HALUI = halui
HALFILE = 369.hal
HALFILE = custom.hal
POSTGUI_HALFILE = custom_postgui.hal
[KINS]
JOINTS = 2
KINEMATICS = trivkins coordinates=XZWhat I have tried:

• No hardware issue: GUI jog always works, signals are visible.
• All estop, enable, limit and home inputs are OK.
• No errors in logs, no HAL load error.
• Both axis and gmoccapy GUI tested, no difference.
• Analog pins connected, values update, motors do not move via gamepad.
• All possible scalings tested.
• Did NOT try button jog (digital), only want analog.
• It feels like halui.axis.*.analog is either not "active" or some enable/select/mode/condition is missing, or maybe a bug in halui or GUI blocks analog jogging.

My questions:

• Is anyone currently using analog jogging with hal_input and halui.axis.x.analog etc. on LinuxCNC 2.9.x? If yes, what is the minimal working config (enable, select, mode...)?
• Does analog jogging need a special enable/select/mode pin to be set?
• Are there known bugs or dependencies in halui/axis/gmoccapy that block analog jogging?
• Can anyone provide a minimal working config for analog jogging?

More info or logs can be posted if needed.
Thanks for any ideas!

Hello i have conect a china optical enoder with 1024 steps today on my lathe and mesa79i6s
have set up with 4096steps i get velocity from 6-10 thats way to different or?
What i make wrong? i looking for threadcutting in future
Thanks

I haven't tried any other program. This was my first test and I made it as basic as possible.
Could there be something in the .hal or .ini that makes it expect relative positions?
What information do you need?

It looks like you have the host IP address set to 192.168.1.121.
This will not work, you need to set the host address to something
different but in  the same network range, say 192.168.1.100

(in other words, you were not pinging the Mesa card but rather the host itself)
 

Well you are using different Mesa cards than I was, and I was using a much older version of Linuxcnc. You won't be able to copy what I had verbatim.

I looks like you are using a 7i95, so for the X axis limits and home, with the home/limit combined at the min limit, you might use something like this.

In your posted hal file it has the vaariable call from your ini file "[MESA](BOARD)". This tells the hal file to use what you have set in the ini file in the "[MESA}" section, what is set on the line "BOARD =", which in your case is "7i95".

Hi PCW,

Here are the results of the test you suggested. It is on a completely fresh install of LinuxCNC and I only changed the network settings using the standard ISO image. What do you think?

 

yeah touch screen would work. But what happens when some drops of coolant hit it and it freaks out. my phone is bad enough with a tiny drip of water. I wonder if itd be worth making a custom keyboard and special mapping some keys. QTdragon looks nice. I may give it a try. 

Thanks PCW,

I'll give that a try.

Works like a charm.

Hello,

I once exchanged tab for spaces, but that makes no difference. I suspect that the reader routine does not recognize the comment as such.
Incidentally, my INI file is not as chaotic as there, I just copied it in and this strange arrangement came out.
In practice, everything is nicely arranged in the INI.

Many greetings Frank

Unfortunately I do not have any coding experience...

like i mentioned in previous post a "C" at the end "LS 403 C", indicates you have a distance coded version of the scale. Do you also have an interpolator like the exe 602?

I doubt i'll manage to HAL such a custom component myself, but I have my mill moving and would of course be willing to do some testing if someone has some time over to give it a try!

/Hampus

I think this is a raspberry PI issue as there is no fast sample rate option in the halscope.
Hopefully won't affect what I am doing, other than spoil my pictures.

A break-out box.
A car relay.
Break the arc start ground cable when sensing.
And ohmic sensing works with the IPTM-60.
No modifications to the plasma cutter.
Standard arc voltage reader used, I use my own THTIC2.