Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility with K6 #6

Open
JarrettR opened this issue Aug 12, 2022 · 2 comments
Open

Compatibility with K6 #6

JarrettR opened this issue Aug 12, 2022 · 2 comments

Comments

@JarrettR
Copy link

This seems to aaaalmost want to work with the K6.

This link implies that it should work:
https://www.mariolukas.de/better-software-for-k3-k5-and-k6-laser-engraver/
But all the comments are talking about an issue in VisiCut that I also get.
Related issue here: t-oster/LibLaserCut#170

I'm using WSL / Ubuntu on Windows.

jarrett@Jarrett:~/laser/K3_LASER_ENGRAVER_PROTOCOL/src/k3_laser_api/build$ ./k3_laser_api --port /dev/ttyS4 --if ../
../../documentation/test_images/test_image_1.bmp
file_to_laser= ../../../documentation/test_images/test_image_1.bmp
set serial_port = /dev/ttyS4
Arguments remain = 1
SERIAL_CONNECTED
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_OK
ACK_TIMEOUT
SERIAL_DEVICE_NO_CONNECTION_ANSWER_IS_IT_THE_RIGHT_DEVICE```
@mgmax
Copy link

mgmax commented Aug 12, 2022

This sentence in the README.md could be the clue: "I found out that at commands where the head has to travel long distances it makes more sense to wait 100ms until the next one is sent to avoid errors."

So I would guess that these 100ms are not enough, maybe one needs to calculate the time based on how far the head moves or so. Would be helpful to look at how the original software reacts - how long does it wait after the ACK before sending the next command?

@RBEGamer
Copy link
Owner

RBEGamer commented Aug 13, 2022

Yeah thats a good point. In my tests and test images (also for empty lines), 100ms was good working delay time. I think this is calculated per line basis. Maybe a factor for the waittime is the travelspeed of the head...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants