Advanced Search

I think `step/dir` is causing problems.

The incremental encoder has 2500 lines and therefore 10000 pulses. The motor needs 10000 pulses per revolution at 6000 RPM.

That's probably too many.

I need to somehow change the pulses via the parameters. But I'm stuck for ideas.

OK so set the scales to 1000 for now and what do you know.... they all move

Pendant is working on the TB2 encoder with the axis select and feed rate multiplier switches and the MPG doing what it supposed to do.
E-stop triggers an output that isn't connected to anything yet but it works at least
Need to connect the LED to something, probably look for a signal that shows when AXIS is in Manual Control rather than MDI

From what I understand it doesn't look like the Axis indicator "lamps" on the Axis screen will follow the pendant selections, too bad as that would actually be handy.

Next step I think is to get the spindle output working.
I'm hoping to just use a meter to watch the output since the actual spindle is a 220v VFD which I don't have here on the bench

Then I'll have to get the 7i84u hooked up and start looking at limit and home switched

Thanks again guys, more questions will be coming I'm sure
M
 

STEP_SCALE = 1.0 across the board.............. BANG HEAD!!!!
Just setting everything up on the desk so I just hit 1 on every axis in PNCconf without thinking of the effects
There's a couple of hours I'll never get back... 

Thanks guys
 

If it's moving very slowly, (and in the proper direction) that'a a scaling issue
not a wiring/hardware issue.

For step/dir drives with optocoupler inputs (like the DM556)
I would normally suggest single ended wiring:

7I96S   DRIVE
STEP+  STEP+
GND    STEP-
DIR+    DIR+
GND   DIR-
STEP-   NC
DIR-     NC
 

Be happy! you have movement!
you just need to work on your steps per mm/inch and velocities. Note that jogging uses DEFAULT_VELOCICTY so if it is low, motion will be slow. Also try a G0 in the MDI window

Would it be possible for you to give any information regarding the missing module and the installation process ?

Starting a new build for a XYZ router and I went with a 7i96s card because of availability. (Also got a 7i84u but that will create later problems)
Hooked the card up and I thought I had everything set correct for a few simple tests on the bench but obviously missing something.

Hooked the DM556T control to TB1 pins 1,2,3,4  for step -/+ and dir -/+ of the controller
Left the enabled +/- disconnected as per the StepperOnline Manual

in the PNCconf I set the first step/gen for main axis X
net x-enable=> hm2_7i96s.0.stepgen.00.enable type settings show in the machine.HAL

I can jog with the arrow keys and the DRO thinks the axis is moving but the stepper doesn't move. moves incredibly slow it turns out. G0 X100" is turning about 1/4 of a rotation on the motor and takes 15 seconds...... I must have my steps/rev way off somewhere.. back to the drawing board

(The shaft is locked when under power, turns with the power is removed which is what I would expect)

As far as I can figure from the MESA docs this should be the default wiring setup but do I need to configure different for it in the HAL or is it possible the enabled needs to be pulled down on the controller?

Tried various different things most of the afternoon now and I'm just going in circles 

Any suggestions or ways to troubleshoot would be appreciated

Thanks in advance
M

You mean like writing my own hal component?
Where can I find some more info?

I fixed the missing module with your instructions, and another one appeared related to QT5. I checked the error on the web, and it was also due to a missing module. I installed it, and PROBEBASIC worked. I also reinstalled the image with your instructions, and now everything works fine. Thank you for your support.

The 7I96S analog output is designed for unipolar use and will not work
wired directly to the drives analog inputs. It's possible to do this but requires
external +- power supplies.

Since the drive has step/dir inputs, I would use those instead

 

How can I connect an analog servo controller to the Mesa 7i96s?
DA+ to TB2-24
DA- to TB2-22
GA GND to TB2-23
I want to control the direction of rotation via + and -. Therefore, I only need S (spindle) ON connected to, for example, TB3-16.
The Mesa only outputs 5V, so do I need to adjust the parameters in the servo controller?One more question about the 7i73 board. How do I activate Mode 3 for the analog inputs for potentiometers? 

Probá con grabr.io, por ahí conseguís a alguien que te las pueda traer, o hay empresas que reciben las compras que hacés y después te las envían sin problema para Argentina. Algo como TiendaMia pero reciben paquetes de cualquier lado.

the same thing happens with a restart, as soon as I want to insert any axis or anything on the 7i96s (specifically the A axis) the fields for angular are blurred...also if I don't do that and export the configuration for the 7i77, an error appears about 0.analogen...and 0.spinnen which I have to comment on. it is very possible that it is due to the new version of mesact, which requires a newer mesaflash, and I need to see how to update the older one and then try, because there is no previously flashed 7i96s-7i77.bin in the tab ``firmware''

Maybe im missing something, is this just installed into a standard debian OS?

I see the install guide commands to "install" everything, but im attempting to install in debian13 and getting alot of errors.

At last the Spindle is back under control, the new VFD works well, and the rigid tapping cycle executes, so therefore spindle orientation must work....
M19 R120 Q5 simply times out.
Linuxcnc ORIENT Man  explains I need to setup the orientation pins etc.
loadrt orient names=orient
loadrt pid names=orient-pid
net orient-angle spindle.N.orient-angle orient.angle
net orient-mode spindle.N.orient-mode orient.mode
net orient-enable spindle.N.orient orient.enable orient-pid.enable
net spindle-in-pos orient.is-oriented spindle.N.is-oriented
net spindle-pos encoder.position orient.position orient-pid.feedback
net orient-command orient.command orient-pid.command

all good, except for the enigmatic statement at the start:-
"On spindle.N.orient disconnect the spindle control and connect to the orient-pid loop:"

This I cannot quite get into my hal without error. 

Current error is:-
./Hurco_7i92.hal:347: Pin 'encoder.position' does not exist

Also having failed to get spindle.0.orient to connect, I have reverted to the original enable connection.

I'd appreciate some guidance please.
Thanks