TB6600 and new motherboard.

Have you tried longer step times?

Step times need to be changed in the .INI file, not n the .HAL file.
Also the step time will depend on the base period if using one, so using a slower base period might help.
Not sure what is going on but if other axis are working but Z is not, check the drive and motor wiring then switch the Z drive and motor to X or Y, if it still does not work = change the drive or in rare cases the motor.

Oh, using parallel port, so in the hal file change the reset time to 10000, then in the ini file change the base period to 100000.
Did you try connecting it to X or Y?

MagicMarcus wrote:

I have X axis with M542 driver, Y asis 2x M542 driver. Only Z axis I have TB6600 driver which doesn't work on any axis on 

Ah, so you are saying that the TB6600 driver does not work at all? Or that is works, but not with LinuxCNC? 

They can just fail. The TB6560 fails as a hobby. The 6600 is meant to be better. But can your observations be explained by a failed driver? 

@tommylight: His HAL is coming out wierd, hard-coded to 1 for step and space and no reset.  Possibly a unit confusion in the date entered, but  the INI is not involved. 
 

Yup noticed that, but i would not change the timings in hal, back in 2.7 while it was in beta i did change that and it had some issues with it. Reset line can be added in hal, but this seems like a driver issue since 2 other drives are working.

That might be due to 5V on old and 3.3V on new motherboards.
The easy way around that is to use a USB cable to provide 5V to drive inputs and wire the inputs for common 5V.
New TB6600 drives ( they use a different chip inside) work with 3.3V always, not sure about the real 6600 ones, i do not think i have any left to test.