LAOS Laser

I bet this is what I fixed in https://github.com/LaosLaser/Firmware/pull/11

Please try my change (binary version here: http://files.thomas-oster.de/laos-fixed.bin) and confirm if this fixes the issue.

Hi Thomas,

Thanks, that looks feasible and maybe your firmware results in more stable movement of the z-axis, but the movement is so small it's difficult to tell.

I have noticed though, that movement of the X or Y axis by the movement buttons on the I2C module also results in movement of the z-axis - ironically at a reasonable speed...

Hi. Somebody I know also told me Z was moving together with X/Y, but I can't find the issue by just looking at the code.

However, I changed the code to use 100*speed as for x/y. Please test http://files.thomas-oster.de/laos-fix-z-jogging.bin

cheers

T

Thanks Thomas,

I remember that as well but spent the last hour looking for it without success. I seem to remember that it was the order of a bunch of variables that fixed things but can't remember what.

I tested the movement of the z axis when x/y is moving from the buttons some more and the 'Move:' debug output to the serial port shows the z-axis is not incrementing at all while in reality it is physically moving.

I'm beginning to think there may be a runtime issue with variable handling...

Many thanks for the new firmware. The z-axis doesn't seem to move at all from the focus buttons with it though.

Hi...
as you see in the commit, I didn't change anything except the speed. So the only thing which I can think of is, that you z-min and z-max is not correct, so it just clips the values.

Another thing:
I remember some weird bugs when initializing variables as:

v1 = v2 = v3 = 0;

v1 = 0;
v2 = 0;
v3 = 0;

Since I do not have a z-axis, it takes much time if i step by step change the code, send it to you and you test it.

Thanks Thomas, I'll have a dig.

So far I've found that all seems sensible in the 'specific speed' version of the two LaosMotion::moveTo() functions so far as the call to plan_buffer_line()

I'm stuck now.

Sending a simple job via TFTP that moves just the z axis end to end. I can see with a few additional printf's in plan_buffer_line() that the z-axis remains static, but the z-axis most definitely physically moves. Same with a simple move of the y-axis.

I have no idea really of what's going on, not being a C++ programmer. I'm kinda hoping someone will send the clue bus for me :)

'guv