Startup trouble

Is that the exact error message?

If so , I have never seen that error

(a "joint following error" is common with setup issues)

And no, you should never ground any Mesa Step/Dir outputs, this
can damage the driver chips

poesel wrote:

"Motor 0 positioning error
Position: relative expected"
(also for motor 1 & 2).

Is this the actual message? Or has it been translated back from a different language on the machine? 
The reason I ask is that I can't see that message in the code (I was looking to see what kind of fault causes that message) 

poesel wrote:

tommylight wrote:

You have step and dir pins wired to DB25 on the +step and +dir, but there is nothing to -step and -dir, those should be tied to GND.
 

As PCW already noted, that board doesn't have STEP- or DIR-. Or do you mean I have to ground it on the Mesa card?

Edited the post, i missed the small writing on Mesa port so i assumed they are the drives.
Sorry.

andypugh wrote:

"Motor 0 positioning error
Position: relative expected"
(also for motor 1 & 2).
Is this the actual message? Or has it been translated back from a different language on the machine? 

The reason I ask is that I can't see that message in the code (I was looking to see what kind of fault causes that message)

 

No, sorry. The original message is in German:
"
Motor 0 Positionsfehler
Position: relativ erwartet
"
 

Ok, I found it. There is actually a typo in the error message, which I didn't replicate properly in my message.
The error spells "Positionssfehler" but the correct spelling is "Positionsfehler" with only one "s".
Makes it easier to find.

#: src/emc/motion/control.c:830
#, c-format
msgid "joint %d following error"
msgstr "Motor %d Positionssfehler"

Now I need someone to please tell me what causes the error. Or to be more precise: what did I configure wrong, because you cannot have a following error without a position sensor and I don't have one.

A joint following error means that the actual position differs from the
commanded position by more than a preset error limit.

In the case of Mesa hardware, it means that the stepgen position
(feed back position from the step generator) does not match the
commanded position.

This can happen with various setup issues and poor latency on the host PC

Can you post your current hal and ini files?

That would help to discover the issue

PCW wrote:

Can you post your current hal and ini files?

That would help to discover the issue
 

Sure - thanks!

OK those hal/ini files work for me with a 7i96s

So something is different on your system.

Can you launch LinuxCNC from the command line
and post the the precise error message(s) that you get?
(Printed in the console)

 

I started linuxcnc and 'moved' all three axis. There was no error message, but the motors did not move.
That is all from the shell.

markus@lcnc:~/linuxcnc/configs/Janus$ linuxcnc -l > log
Note: Using POSIX realtime
note: MAXV max: 33.333 units/sec 2000.000 units/min
note: LJOG max: 33.333 units/sec 2000.000 units/min
note: LJOG default: 16.667 units/sec 1000.000 units/min
note: jog_order='XYZ'
note: jog_invert=set()
Note: Using POSIX realtime

Log:
 

You could try doubling the step time in case the step inputs are really slow.

Also, are you sure about the DB25 pinout? there are a lot of TB6560 modules
with different pinouts (many with different enable inputs)

You could also verify the direction signals with a voltmeter when jogging either way
to make sure there is not a hardware error of some kind