Advanced Search

7i76E is connected to the computer through ethernet, the 7i77 connects to the 7i76e with a ribbon cable and the 7i64 connects to the 7i77 with a modified ethernet cable.
The boards have 5v and 24v field power.
It has been a while since I wired and had time to do the cards but I remember that I did flash one for some reason or another. Does it need different flashing for step direction than for analog?
And sorry again, as I said it has been a while since I had time to get into this again and don't remember where to type readhmid

It would be much better to give us correct info about your setup, like what is attached to 7i76 and 7i77?
Or is it a 7i76E with 7i77?
Did you flash the correct firmware for whatever is in use?
What does readhmid return?
Do the boards have 5V and Field (12-24V) power?

Hi Guys, I am having trouble getting my lathe to work.
It is an Old Superslant Hardinge.  It has 4 axis, 2 turrets each with an x and z and each with 8 tool changer.
The problem I have is that I have a working hal that connects to the boards, and all the io's are working.  But the drives both axis and spindle don't do anything.  The axis I know the problem is that im wired for step and direction and the configurator doesn't give a setup for that, and using the step configurator and blending the file is giving me a major headache.as its difficult to see what parts of one I need and what parts I can't have.
I am running 7i76-7i77 and 7i64.
Any suggestions as to how I can make or blend a hal file that will do what I want would be appreciated.   

Thank you for noticing my bonehead move. I commented it out when I was trying the pwm gen copied from pncconf with an 7i92/7i77. (I tried re-naming stuff to 7i97 unsuccessfully.)

Sadly I am still doing something wrong with the pwmgen. I no longer have AOUT4 stuck at 10v, but it is now stuck at 0v.

I have un-commented what you noted in my hal file. Changing [SPINDLE_0]SCALE to SPINDLE_0]OUTPUT_SCALE and adding OUTPUT_SCALE = 10000.0 to my ini file under spindle_0.

The pwmgen that you found was copied from my X axis and renamed for the spindle. It came from Mesa CT.

I am re-reading the pwmgen component in the docs, but I am having trouble understanding what I need to do.

arauchfuss wrote:

Hi I am converting a Tree Journeyman 325 to LinuxCNC. The XYZ analog servo controllers all work so I need 5 encoder inputs: X, Y, Z, Spindle, MPG jog wheel. I have a 5I25 and 7i76 from a previous mill conversion but I don't think they will be useful.
Is a 7I95T a good match? I may want to use the 7I76 for additional IO.

Thanks

You might want to start a new thread if you have further questions, but here's a quick answer:

The 5i25 can work with a 7i77 (or 7i77D) DB25 daughterboard if you want to reuse it.  You'll need a computer with the appropriate slot, of course.

If you want an 'all-in-one' board then the 7i97T is the analog-output board you need, not the 7i95T.  The 7i95T is for step/direction output.

Either of the above options will have enough drive outputs and encoder inputs to work with your Tree.  Note that your MPG, while technically an encoder, does not require the same high-speed encoder input that a servo drive does.  The MPG can be connected to MPG-specific IO on the above boards (taking up two input pins), leaving you with two spare drive outputs and HS-encoder inputs.

I've not personally used Mesa analog-out boards, so please review your drive command signal requirements and verify the above boards outputs and encoder input signals will work with your drives and spindle control.

andresgodinho wrote:

Hey guys,
First ever post here and first ever linuxcnc retrofit.
Just got a Chiron FZ12S Rapid CNC machine with a Siemens Sinumeric 810M controller and Siemens Simodrive 611 for all axis and spindle.
Sinumerik 810M is dead.

Started converting to Linuxcnc, got a Mesa 7i92 + 7i77 + 7i74 + 7i70 + 7i71.
Got the basics running. Home switches, XYZ motors running fine, drive enables, a few inputs conected and a few outputs conected (to allow for proper drive and machine start, it requires a complex sequence of relays and input feedback for the safety relays to activate)

Now i am facing the first issue. Basically i got the encoder feedback from the spindle going to the spindle drive and then to mesa 7i77 encoder 5 input.
I comand M3 S200 --> spindle rotates in right direction and at 200 rpm.
I then comand S1000 --> spindle drives jumps to 1000 rpm
If i comand M4 --> spindle rotates in the right direction and at the comanded speed.

Now the problem:
Up until 3900 rpm (spindle is 10500 rpm max) everything works perfect. If i comand S4000, encoder feedback seems to desapear and the drive goes to max rpm... It seems that the Siemens drive is disabling the encoder output to linuxcnc...
Drives uses +-10V and is in velocity control. 
Is there any way to say to linuxcnc that up to 3900 rpm it should use encoder feedback and after 3900 just use the index pulse from the encoder to control the rpm?

Thanks a lot guys and i will be posting pictures soon.



 

Hi, I'm Brazilian and I'm trying to do what you did, use the Sinumerik 611 driver on an 810m using Linux CNC, could you tell me more about what it was like to do this integration? Did you use the +-10v command to activate it or instead of step-dir?

Tommylight thanks for this, I had completely forgotten that the 7i96s has an output of 0-10v cw or ccw, it depends on how the motor phases are connected mechanically... on the lathe that I plan to retrofit, the main spindle is an Ac servo and the factory of course has cw ccw.. my question is whether in that case I will be able to set the counter direction with some magic in the hal
i mean m3-M4 ,or via some relay that would change the motor phases or a third option to find the input pin for changing the direction on the Simodrive itself? there is another option to take the analog output from the 7i77 because I planned it for x and z control. In the case that PhilipMe has, I have the same servo driver on my diy lathe and it can work in both modes, position and velocity also and torque over 25 13 analog inputs on the driver. in the manual there is a possibility to change the direction...PhilipMe check which parameter is responsible for that, it was a long time ago and I forgot.

PCW wrote:

The 7I96/7I96S are step/dir controllers. The 7I96S has a one channel 0 to 10V
output for spindle control. I think tommylight suggested the 7I96S as it gives
you some step/dir outputs for added drives.

For an analog  servo system you need multi channel analog outputs and
multiple encoder inputs. You can add these to the 7I96S either by adding a 7I77
or a 7I85 and 7I83.

A 7I84 just adds more digital I/O say if you have a tool changer.

Sourcing means for example an output device that supplies +24V to a load with a negative common
 

Sinking means for example an output device that grounds its outputs to drive loads with a +24V common

so now I'm a little more confused.  I just read about the 7i77, which seems like doing the 7i96s plus 7i77 would get me where I want to be, but then I looked at the much cheaper 7i83, which appears to do the same thing?  

and you said pair the 7i96 with a 7i77 or 7i85 and 7i83, so why would I need the 85 and 83 together?  So is a 7i77 essentially like a 7i85 and 7i83 put together on one board?

I'm sorry for my complete ignorance, but so many of these cards seem to do the same thing, especially to someone like me who has no clue about things...

The 7I96/7I96S are step/dir controllers. The 7I96S has a one channel 0 to 10V
output for spindle control. I think tommylight suggested the 7I96S as it gives
you some step/dir outputs for added drives.

For an analog  servo system you need multi channel analog outputs and
multiple encoder inputs. You can add these to the 7I96S either by adding a 7I77
or a 7I85 and 7I83.

A 7I84 just adds more digital I/O say if you have a tool changer.

Sourcing means for example an output device that supplies +24V to a load with a negative common

Sinking means for example an output device that grounds its outputs to drive loads with a +24V common

 

my friend just repaired the 7i77 that I had and broke it with a short circuit (he says it's a dc-dc converter), in case it's successful, I'll try to connect it with the 7i96s...my question is, in that case, can I use the spindle output and encoder from  7i96s plus mpg and I/o, and with the 7i77 also use the I/O plus analog signals for the drivers (siemens amplifiers)?

So after the crucial tip from pcw I got the outputs working and configured the lube system. As for the hydraulic draw bar I repurposed the former cycle start button from our very simple hand held. After looking at the code for the central lubrication, I modified it a bit to fit the drawbar application and loaded it as drawbar component, which will only release the drawbar, if the spindle is not running.
It connects via Hal similar to the central lubrication component (wiki.linuxcnc.org/cgi-bin/wiki.pl?CentralizedLubricator).

Hi All,My brother and I recently purchased an old MAHO MH600T with the intention of retrofitting it using LinuxCNC, a 7i77, a 7i84, and the GmoccaPy interface. We began our project by following Mark's thread, which provided invaluable information—without it, we would have been lost. The machine originally came with an old Heidenhain 332 CNC controller, but unfortunately, the video output seems to be broken. Since this compact module also contained the EXE interfaces, we had to replace them with three EXE602 modules to read the linear scales.This is working fine (we are currently ignoring the c-axis...) and the cable cabinet still had a convenient place for its three new members. 

At this stage, we have successfully set up the endstop chain and the linear motion system (encoders and the Indramat drives for X, Y, and Z axes), using conservative values for the PID controller and homing. Our next step is to get the "accessories" working, such as flood coolant, the tool holder, and basic spindle control (including potentially allowing for manual gear changes). While the machine behaves as expected when we press the test buttons on the relay board, we are facing difficulties controlling these functions via LinuxCNC. I have a few questions about this (apologies if they seem basic, but I am new to LinuxCNC and HAL).

1. I wired the 2K2 relay for the coolant pump to output-15 of my 7i84, with field power supplied by the 24V line. The pump operates correctly when I test the relay using its test button, but attempting to activate the relay from the Mesa card causes the machine to go into an emergency stop. Even connecting the relay to my field power alone triggers a shutdown. I've double-checked the wiring (I have a connection from output 15 to the test lead MP12 and to the relay), swapped the relay with a known working one (19K1, machine on), and tested the output without anything connected (it pulls up and down correctly). I initially thought it might be an issue with using a different 24V line, but the "machine on" relay is functioning. I'm currently suspecting a short circuit, but there is no error message displayed by the controller—just the fact that the machine goes into E-Stop. Is there a hidden log or extended error message that might provide more information?

 
 
2. The spindle: For a first test, I wanted to have the spindle on/off working, which just should be the three relays 1K8, 1K9, 1K10, connected to output 12, 13, and 14 on the 7i84. but with the following hal code, nothing happens, when pressing spindle start, and the pins of the 7i84 are floating at roughly 13V. So it seems the pins are not connected in the hal. Is there something I am overlooking, do I need to use the halui pins?:3. The gearbox. The good news is that our machine is equipped with an 18-speed gearbox, similar to Mark's, but the sensing configuration is slightly different. While the outputs are the same, we only have nine inputs, which means we're missing the "Links-Mitte" switch that indicates whether the gear motor should turn left or right. Has anyone modified the gearbox component for the MH400E to accommodate this configuration, or has a working original MAHO with this arrangment and could share, how the gearshift is done there? I somehow hope, that it is just an easy modification, but my C is a bit rusty, so we will se how this goes.
 

Kind regards

Sebastian

Sami wrote:

"""
Remove the lathe power plug, try again.
"""
We have started linuxcnc without lathe hw plugged in and it start until error of
missing I/O-information about door etc. When lathe hw is connected to 6i25 pc reboot
at line addf hm2_5i25.0.read servo-thread.

 

That points to a bad wiring issue with outputs or inputs, or power issues, or different potential between Mesa/lathe electronic/drives/spindle drive.
Remove all the input and output plugs from the Mesa 7i77, power on everything and start LinuxCNC.
If that works, power off the machine, plug one of the connectors, turn on the machine, test connectors one by one.
When you find a connector that causes issues, start removing wires from it and test.
Do not remove wires or plugs while the machine is on.

Question 1:
Is there an output pin for an external Estop/reset safety circuit to read the status of 7i77 WDT? If not, would it be feasible to use one of the existing pin outputs by Keeping this output pin ON while the watchdog timer has NOT bit. Here where the catch 22 comes into play, when the WDT bites, the hostmot2 driver disables the digital outputs therefore my external hardwired circuit will not be able to determine the WDT output pin status (see diagram Highlighted in RED). One way I can think of to solve this puzzle is to restrict the WDT from internally disabling the digital outputs, and have WDT just set a flag and let the hardwired safety circuit take care of disabling the power to the digital outputs.       Or I am out to lunch?Question 2:
7i77 field terminal block has several terminals I am hoping to be able to keep the field power OFF to the digital outputs until the safety lockout circuit is reset and the field digital inputs and VIN powered while the ESTOP circuit is active. If you look at the wiring diagram, I need the numbers of the terminal blocks marked with question mark (highlited in green). Nomenclature:
CR# – CONTROL RELAY
MCR - MASTER CONTROL RELAY
F# - FUSE
DI – DIGITAL INPUT
DO – DIGITAL OUTPUT
PB – PUSH BUTTON
WDT – WATCH DOG TIMER
L1 - MAIN SUPPLY LINE 120 VAC
N - MAIN SUPPLY NEUTRAL
PL- Pilot Light A brief explanation to what this hardwired circuit does follows this diagram.
  The wiring circuit diagram below  is a hardwired circuit that will allow power to be removed from digital outputs, servos and spindle. The circuit achieves the following:

• If power is lost during operation the machine will not restart when power is re-established.
• If an Estop is activated or a fault occurs during operation, the circuit will inhibit (prevent) power to digital outputs, servos and spindle. The rest of the machine control circuit will stay in the ON state; this will enable you to troubleshoot and resume operation without major reinitialization of the machine.
• Machine will not restart until all faults are corrected and operator presses reset button.

This hardwired circuit is the equivalent of safety relay without guided contacts.

I've got a 5' x 10' CNC router with a failed Mach 3 control. It has Yaskawa Servos (SGMGH-09ACA61) and was set up for step/dir with an ethernet smooth stepper. It was "open loop" with that control. It has four motors for the 3 main axis and a 5th motor for a rotary axis. I might not use the 5th axis but I do have a crazy idea for an automated dust collection "axis" that would probably use stepper motors. 

I have a Mesa 7I76e that I bought several years ago for another machine that has yet to be completed and I think this would be my fastest/easiest control to drop in but would still leave me open loop to the control. Instead I've been thinking of running with analog servo signals and the encoder feedback into LinuxCNC using a 7I92TF with a 7I77 or a single 7I97T. It seems the 7I97T might be a bit light on general I/O since the machine has an ATC spindle and several other pneumatics that need to be controlled and sensed so I'm leaning towards the former combo. 

Any suggestions wrt to Mesa card availability and the advantage of using analog vs step/dir in this application?