Advanced Search

Either change all the HAL pin names in the Hal files from qtdragon to inova or add -c qtdragon to the load line in the INI.

DISPLAY = qtvcp -d -c qtdragon inova

One of the safest way to have the probe and the tool touch sensor on the same hight would be to install a rigid piece of metal and facing it with an meassured tool. After that calibration of the probe with this new face.

Btw. Cool machine. Do you have somewhere more info about it? Right now I retrofitting a Kuhlmann P20. Looks quite similar.

Oops.  I'll have to add an interlock for the probe when it's in storage, on the right column. 

 

Getting the gage length of the probe isn't as easy as normal tooling.  It's a dual-contact spindle nose, so normally you can measure the length of tools on the surface plate.  But with the added variable of Z travel in the probe, you can't measure directly.  I ended up touching off on the 1-2-3 block and doing the guess-and-check on a gage-block stack to find the length.  A big gage block, adjustable parallels, and a micrometer would have been less dramatic but I didn't think of that until later.

 
 

Hello,
I can't seem to find the file pause_pin.py. Does the path have to be exactly "USER_COMMAND_FILE = CONFIGFOLDER/pause_pin.py" and does that mean my machine folder? Or where does the file have to be located?

Thanks! mux4 worked.

In case others need it, here is my solution:


 

Thanks

If I build against 2.10, how is backwards compatibility handled? I am running 2.9.

You need both 5V on 7I77 field power applied for the 7I77 to be full operational

sudo mesaflash --device 5i25t --readhmid > pins.txt

and posting pins.txt here will help verify if you have the correct firmware installed

I should also clarify that it is pulling up a lot of information on the 5i25 but I dont know if it would plainly tell me the firmware version with 7i77 in it thats all.

I didnt think I wanted any parports so this is not something I selected. right now I do just have the basic stuff selected nothing crazy. I entered in that sudo mesa flash line and I am not seeing anything refering to the 7i77. I do have the 5i25t kit. I am supplying power to the 7i77 via a power supply the lights are on and I had moved the jumpers on the 5i25. should I be able to ask mesaflash for info on the 7i77 because that didnt work for me.

I tried your suggestion, but that didn't work either.

I decided to follow the advice you guys gave me earlier and just buy and old PC (a Lenovo ThinkCentre M83 SFF). Let's hope that will yield better results.

Connect the 7i77 the DB25 going outside the PC.
And no, those are not parallel ports so do not choose any in the wizard, although they can "play" as parallel ports at much, much higher speeds.
Use mesaflash to check the firmware in 5i25 is for 7i77
mesaflash --board 5i25 --readhmid
or similar, just shooting from memory here.
And make a new config, do not chose anything except the axis and encoders you need, save, test.
Do not choose MPG or anything, nothing, until you get things working somehow, you can edit and add or remove later at any time, you can have as much configs for it as you like, etc, so small steps.
And have a read through this for wiring and tuning, no skipping steps:
forum.linuxcnc.org/10-advanced-configura...ning-detailed-how-to

You need both the correct firmware on the 5I25 (or 5I25T) and the 7I77
connected and fully powered before the 7I77 will be detected.

Suggested 5V power arrangement is:

5I25 W2 down    ( No P3 5V power)
5I25T W3 down  ( No P3 5V power)

7I77 W5 right (no cable 5V power)

5V supplied to 7I77 TB1

Note that the firmware for the 5I25T and 5I25 is different and not interchangeable.

If you ordered the 5I25/5I25T with a 7I77 from Mesa, the 5I25/5I25T would normally
have been pre-configured for use with the 7I77

In any case you can look at the pinout of the firmware with:

sudo mesaflash --device 5i25 --readhmid > pins.txt

or 

sudo mesaflash --device 5i25t --readhmid > pins.txt

and post pins.txt here for confirmation


Note that the error has nothing to do with either the 5I25 or 7I77
but rather some issue with hal_input


 

Greetings everyone, I am starting a retrofit on an older maho MH800E following some of RotarySMP's documentation. I have purchased quite a few mesa cards (5i25 w/7177, 7i74, 7i73, and 7i84) I am just trying to get familiar with all of this stuff as I have never done a linuxcnc project before. I am good with wiring and I know enough about programming stuff but I am having a hard time getting the computer to talk with the 7i77. it appears to be seeing the 5i25 just not anything else. I bought the kit of both 5i25 and 7i77 so I assumed the firmware would be the right one but I have read elsewhere this may not be the case so possibly need to get some new firmware installed. I could also be doing the config wrong as I was a bit confused when it was asking about the 2x7i77 with one 7i77 that is what I picked. and before that it asked about parports I assumed it was asking if I was going to use a combination of parallel ports with the mesa cards? it could be referring to the ports on the 5i25 but again I was unfamiliar with this stuff. Any tips or suggestions would be very helpful

What he said. You basically run them as you would any stepper. Except you would connect the alarm back to a linuxcnc input so the control knows if there is a fault.

You will need to download the omron sysmac software trial to tune the servos. I have the ethercat version of these, they are very nice.

Those look like standard step/dir or analog controlled servos
(the KT model is Analog or Step/Dir)

There are multiple LinuxCNC interface options for these drives.