Advanced Search

I can try it, but since ethercat at the command line (linuxcnc isn't even running) shows ~50% lost uploads, what's the point?

I don't think this is a linuxcnc problem, but rather some networking or drive problem.

I think that the problem is inconsistent HAL signal naming.

You haveThen later in the file:
You need to connect the hm2_,,, pins to the halui.... (and motion....) pins.
Use the same signal name (the first term after "net") to link:

hm2_select pin / axis.L.jog-enable / joint.N.jog-enable

hm2_mpg_counts / axis.L.jog-counts / joint.N.jog-counts

You will also need to work out logic to set the scale:

(probably a mux block) axis.L.jog-scale joint.N.jog-scale

For initial testing, try:

(change the setp to 0.01 if using inches)

If that works, then configure the jog scale (but to help with that we wiuld need to know whether the MPG binary-codes the speed selector or has a pin for each speed)

(This is using the pins from "motion" which are slightly preferable to the halui pins. However HALUI supports analog jog mode, so has its uses.)

linuxcnc.org/docs/stable/html/man/man9/motion.9.html

Looks like mine has two sensors for the tool turret and the z limit switch.

Hi,
I am working on a FlexGui for a waterjet and I want to have some custom buttons that call hal and emc functions. 
I see I can import a python module and do the "from functools import partial" to get the parent, but does the parent also pass access to hal and emc?

I am trying to make a custom stop button that will turn off some hal output pins with hal.set_p() and then call emc.abort() in python so it will turn off the jet and sand when pressed. I also need to make one that will pause by setting the hal pins off and setting the motion.adaptivefeed to 0.

Any help would be appreciated

Made the change net tool-change-request iocontrol.0.tool-change.
 

I have made some progress:

I have had to set the axis velocities to constant values (500000, where the encoder has 524288 counts per revolution), since I don't see any HAL pins from the motion planner that carry that information. I will see about writing a custom HAL component that can interpolate velocity from waypoints.

I assembled a MB2HAL config file, and loaded it as a userspace component through halrun. With that, I could control each motor, with no perceptible lag between command entry and motion.

I can control the motors through Axis, but in G1 feed mode at the MDI, I get one step every second or so. For instance, I will command one axis to G1 Z1.0 F5.0 and it will move ~60° every second or so until the move is done. In G0 rapid mode at the MDI, there is a significant delay, again roughly one second between the time I press Enter and the time the motor begins to move. While the move is in progress, distance to go changes smoothly, but actual position (and the motor shaft) move in steps.

Can you help me understand how Glade and Handler work? I've already created the switch and the LED. How do I now connect them so that pin 17 switches on and off? I'm completly stuck.

I believe you referred to this to run

# rm /etc/{initramfs/post-update.d/,kernel/{postinst.d/,postrm.d/}}z50-raspi-firmware
# apt purge raspi-firmware

What should I do after that? I apologize Tommy, but I have no idea what should I do.
Thanks.

yes

If you select 'Utilities' > 'HalMeter' in the tklinux menu and select 'iocontrol.0.emc-enable-in' does it show TRUE ?

Peter, thank you for the guidance.  Once I re-enabled the PID stuff, things worked as expected.

I used the auto tuning steps and from there have been able to get to a good state.

i did and its not working, when i start sim tklinuxcnc its working

Have you clicked on the 'ESTOP' button in the tklinuxcnc gui to set 'Estop off' and 'Machine on'?

Note that you can use either a handler or the postgui halfile to make the connections.

That does not work because you have forgotten to give a signal name after the 'net' command.

I entered the command in postgui. This does not start linuxcnc. Do I have the correct command from Halshow for postgui.hal?

Not sure I understand this correctly but halshow does not make any distinction between postgui and regular hal files.
The regular hal files are read before the gui has loaded so if any gui related halpins are used in these files you will get a startup error because those pins are missing. The postgui halfile is read after the GUi and the custom panels have loaded.