Advanced Search

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...