Advanced Search

Hold on a second. I lied. Not intentionally. My spindle motor is a DYN4 servo motor geared 1:1.8 and it has a simulated encoder signal generated by the servo driver. That is the signal I am using for the coordination for rigid tapping. The sensor on the slotted plate it just for measuring RPM.
It's been a few years since I set this up and when you mentioned more slots I thought "I knew that, why didn't I do that?" Then I looked deeper and remembered how it really works.

To actually do this with a slotted plate and sensors you would want more slots and two sensors. Read up on how quadrature encoders work.

As long as you know the ratio between the spindle and encoder you can make almost any arrangement work.

These are my .ini settings.
[SPINDLE_0]
P = 2.0
I = 4.0
D = 0.0
FF0 = 1.08
FF1 = 0.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
OUTPUT_MIN_LIMIT = -5400.0
OUTPUT_MAX_LIMIT = 5400.0
OUTPUT_SCALE = -10800
ENCODER_SCALE = 4551.111111
#((2048 * 4) / 1.8) = 4551.111111
#The maximum spindle speed (in rpm)
MAX_FORWARD_VELOCITY = 5400
#The minimum spindle speed (in rpm)
MIN_FORWARD_VELOCITY = 50
#This setting will default to MAX_FORWARD_VELOCITY if omitted.
MAX_REVERSE_VELOCITY = 5400
#The minimum spindle speed (in rpm)default to MIN_FORWARD_VELOCITY if omitted.
MIN_REVERSE_VELOCITY = 50

Sorry for the confusion. I hope this helps.

Can it verify repeatedly without error?
If so if may be something related to write
(how are the WP and HOLD pins terminated?)

It's important to keep in mind that joints (machine movement) and axes (DRO values) are not the same thing. As the X axis is supposed to be perpendicular to the Y axis it would be somewhat strange for the X value to change when moving along Y.
Also note that the forward kinematic is only used to calculate the axis values from the joint home position right after homing and probably when switching kinematics. After that only the inverse kinematic model is used to calculate the joint positions for given axis values.

A little update, changed the EEPROM from a 16MB ST part to a 16MB Winbond part (same as I've used for the EPP\SPI board). Initially no change.

Put a 5ms delay between before the "sync" instruction when erasing & writing a bitfile. Was able to write a bitfile, not everytime, but when it does it verifies ok.

Ran 100 iterations of the Linuxcnc logo gcode, one after another in a loop, and then left it, after 12 hours no comms issues.

If you have nothing connected to the 7I97T but 5V power and any analog
output is not  close to 0V, the analog output circuitry has been damaged somehow.

This may occur if an output was inadvertently shorted to say +24V or
connected before a common ground was established between the drive and
the 7I97T.

OK, that simplifies things, a lot.

Actually if you use simtools there are multiple interfaces.
Serial, udp, write your own...

Every game that is supported by simtools then has the same interface.

I'm working on the Vismach implementation and while playing around i realized, that when i move the Y axis the X axis moves as well. So for so good. But the X-coordinate in Axis does not change.


Note:
X on the Mazak is head up and down in
Z on the Mazak is table left and right

But shouldn't it change? Why doesn't it ?

Kind regards,
Jochen

 

Had the same idea today for a racing/flight sim!
I have no idea what games output for motion, that would help to know, but whatever it is (and i am sure no 2 games use the same output, but maybe through directX...), we would need just translating those to waypoints and from those to gcode.
Taping into games collision detection is out of the question by now as the coding on new games is absolutely terrible and utterly useless.
But, games that have display/gauges for pitch/tilt/angle of attack, should be much easier if they also output somehow somewhere those values.
Then there is the interpreter/LinuxCNC reading those values and sending motion, but should be doable, there are some "camera to motion" things working already somewhere on this forum.
Maybe use that and point the camera at the screen...

Hi there.

I am planning to build a hexapod as a motion sim and would very much like to use linuxcnc as kinematics processor and mesa cards as motion controller.
this is because I am used to it in the normal manner and I like the dependability.
I have searched some time now and found the python hal interface and the python command module. 

As I just get xyzabc commanded positions from the simulator, I very much would like to just set the commanded position in linuxcnc to the new value andet it move as fast as possible to it. 
to prevent motion errors the allowed error would be set very high. 

If this sounds insane tell me, give me your thoughts. Is it possible to update just the commanded position via the hal python module? 

julian

Tried with everything except power disconnected, tried to connect the drive, but the drive would proper forward with no command with stable speed with LinuxCNC off. Channel 3 was never even attempted to connect. Other channels are unresponsive.

Since these pins determine which axis jog, I would monitor them with Halshow
to see if maybe there is a electrical/switch issue with these signals.

parport.1.pin-04-in-not
parport.1.pin-05-in-not
parport.1.pin-06-in-not
parport.1.pin-07-in-not

@my1987toyota,
How is the recovery going?

If any analog output is not close to 0V at power up, (and no output mis-connections)
there is a hardware problem (perhaps a damaged op-amp) on the card and it needs repair.

more notches are better but how can i set encoder
if encoder can only positioned before geartrain ?