Data transfer LinuxCNC to / from custom board - Solved

Aciera wrote:

You seem to have a lot going on there.
First thing I would suggest is to simplify things by choosing which jog method you actually want to use and then test this method in the 'Halshow' tool without all the connections in your hal.
For example this situation should jog the x-axis:

 

Alternatively this should also jog your x axis:
 

Also, posting your hal and ini files might give us a better idea of what you have going on.
 

 

I commented out the 3 lines related to the Arduino stuff in io.hal and postgui.hal to make sure that they are not doing something strange. I then tried both your suggestions and assuming that "setting" all three in the first example or just halui.axis.x.plus (in HalShow -watch), should cause a jog, it does not in either case. So I think there is something missing between those parameters in halshow and the real time thread causing then to be ineffective. I have attached my configuration files.
 

After a bit of trial and error I found the problem, I can now jog from the Arduino board. The fundamental problem was that I was not homing all axis's, I assumed because I was trying to jog x that homing x was sufficient.

I did a little test where I banged in 10 jog increments as fast as I could and none were lost. I'm not using a MPG so I can't comment on the slow response of the ArduinoConnector as noted by blazini36 when using a MPG, however for regular button presses it seems to be doing the job for me.

I have attached the relevant portion of my postgui.hal

Thanks for the help getting this working.
Jeff
 

You can jog without homing if add jogging, enable & counts for each joint.

This is like a century ago I forgot but was it in the naming of the nets that defines whether you can jog with and/or without homing?

axis.x.jog-enable -vs- axis.joint0.jog-enable

An HAL expert would know...

axis is for jogging an axis, which needs to be homed.
joint is for jogging a joint which doesn't need to be homed.

I think these were some of the major changes from 2.8.xx to 2.9.xx

The correct names joint.xx.count, joint.xx.enable and so forth. Open axis and look at the hal configuration menu.

Cant do this anymore bye all wrote:

The correct names joint.xx.count, joint.xx.enable and so forth. Open axis and look at the hal configuration menu.

I personally would never, under no circumstance, ever attempt jogging an un-homed machine-tool (again). Don't ask me why's that, too shy to explain. Great info none the less. Suspected it was something related to the net/name or something.