LinuxCNC Errors - Help please

  I have LinuxCNC v2.9.2 installed and connected to a Mesa7i95t, via Ethernet cable. I ran MesaCT v2.1.2 and have configured most of the settings, likely enough to exercise at least the X axis.The jumpers for the IP address are down, up for EEPROM, so should be default 10.10.10.10, and when in MesaCT, the IP address is set to 10.10.10.10. When I click on Check Config, I get Configuration checked OK, I'm not sure if I need to send this to the Mesa board or if that happens transparently as you make changes?I have a configuration in /home/jeff/linuxcnc/configs/7i95t_xyz/and in that folder I have main.hal, io.hal, 7i95t_xyx.ini, tool.tbl and parameters.varWhen I attempt to start LinuxCNC, I get errors. I have attached the linuxcnc.report. It seems to indicate that LinuxCNC is not communicating with the Mesa board, but that might just be a symptom of another problem.

One other note up in the top right corner there is a spinning circle icon that appears to be associated with the wired connection to the Mesa board.

Please advise, and thanks in advance for the support.

Looks like you don't have your networking set up right
Please watch this

rodw, correct, after I setup as per link below yours LinuxCnc starts, I'm going to watch the remainder of the video now, thank you.

tommylight, easy when you have the instructions, thank you.

slowpoke wrote:

rodw, correct, after I setup as per link below yours LinuxCnc starts, I'm going to watch the remainder of the video now, thank you.

tommylight, easy when you have the instructions, thank you.

Great! There was a time when you had to know what I covered in the video the moment you created a network. But today, its been automated and hidden from the user. Just another example where technology has deskilled the worker!

Rod,
I just watched the video in your link, I assume that's you in the video?

Very helpful particularly the short segment on networking, I'm strong with electronics, know next to nothing about networking and I will make time to learn more as this has been a perennial problem and I need to learn more.

Now that LinuxCNC runs and communicates with the Mesaboard verified by connecting an E-Stop button to an input and seeing it trigger in LinuxCNC when I operate the switch.

My next step might be a bit tricky, let me explain......

I'm using four ac servos to drive the various joints, X, Y, Z(quill), and U(knee)

For the moment I just want to get some motion on X.

The ac servo drivers I'm using (T6), have tuning software that I have used to configure the PID loop that is controlled internal to the T6 driver. The servo motor encoder feeds directly into the T6 driver. This seems to work very well and with the tuning software I'm able to move the X axis very quickly and accurately. The T6 drivers accept step and direction pulses (just like a stepper).

I also have Magnetic scales that presently only drive a separate DRO. Eventually I plan to split the magnetic scale signals and drive both the separate DRO as well as the Mesa board, so I can "close the loop" around the magnetic scales instead of the servo encoders so that any infinitesimally small errors in the ball screws etc. are corrected. So for the moment their is no encoder signal being fed back to LinuxCNC.

So until I make up the splitter I need treat the servos more like a stepper, send the pulses and hope for the best.

Today's problem
After resetting E-Stop, and enabling machine power on
Then manually homing (I think that's a requirement)
Then moving to the MDI tab, I send G1X 0.1 F1 and I get a following error.

I assume this is because LinuxCNC is expecting an encoder signal, but I'm not sure about that or how I can get LinuxCNC to treat the motor like an open loop stepper?

Your assistance is much appreciated.

 

Whether LinuxCNC uses encoder feedback or local
stepgen feedback is  determined by your main hal file.

Can postt your main hal file and ini file here?

Please see attached

   

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