LinuxCNC Errors - Help please

I'm using MesaCT version 2.1.2 (Feb 4-2024)

Where can I find the latest version and what version is it?

Thank you

rodw wrote:

Your hal file looks like its missing a bit but i'll leave it to PCW as he has more experience

From what you are describing, you might like to look at Dual loop feedback where the  motor encoder in velocity mode is attached to the motor drive
And the outer loop from your scales in position mode is closed by linuxcnc.
Ref:  granitedevices.com/wiki/Dual-loop_feedback_position_control
 

Dual loop feedback sounds like exactly what I will be looking for, I'm glad I'm not the first one trying this. Thank you for the link.

slowpoke wrote:

I'm using MesaCT version 2.1.2 (Feb 4-2024)

Where can I find the latest version and what version is it?

Thank you

That should be the latest version by number, but not by date, JT fixed this a few days back, so do check github or wherever MesaCT is.
Sorry for vague replies, but busy.

What tommylight said...  that looks like a hal file created by the bad version of MesaCT
Fetch the latest and try again.
 

github.com/jethornton/mesact/releases
There it is, same version number, but uploaded yesterday.

Thank you for the link, I will know where to look in the future.

As shown below, I renamed the Feb5 version _Feb5-2024.deb and then right clicked the new version and ran Reinstall Package using GDebi on the new version. However when I run MesaCT now, it still shows Build Data as 2/4/2024, so it appears that the old version has not been updated with the new version?

Perhaps I need to install using the command line?

Nothing changes by installing it using CLI, it is the same as using gdebi.
Try uninstalling first, then install this new version, see if that helps.
And try to make a new config then open the created hal file with a text editer and see if it has more than about 20 lines, should be much more lines.

Thanks for that, I'm making progress......

I uninstalled the old MesaCT and reinstalled the new version and I now have a build date of Feb24 in MesaCT. Furthermore the hal file generated is now much longer (see attached).

I then started LinuxCNC (Axis) and reset E-Stop, powered the machine and homed. Then on the MDI page I executed G1X 1 F1 and the Axis DRO slowly ramped up from 0 to 1.000, but I did not get any actual servo movement. My servo driver is powered, connected to the step and dir 0 channel on the Mesa board in differential mode and enabled via a jumper at the moment.

I don't see any pulses coming from the Mesa board.

 

Are you getting any errors?

Do the direction pins change state when jogging in different directions?

Pictures of the wiring?