UI works but CLI doesn't with NEJE DK-8-KZ

[sleptew]

Hello,
EzGraver 4.0.0-beta works nicely with my DK-8-KZ on Linux Mint 19 Cinnamon with the UI version; however, when I try to run the CLI version, it connects to the DK-8-KZ via ttyUSB0 but is unable to command it via the reset, home, or start commands. I notice that the terminal window feedback differs between the UI and CLI versions - e.g., when I run the reset command in the CLI version, I see the message "transmitting 1 bytes "f9"", whereas when I run the same command in the UI version I see the message "transmitting 4 bytes "ff040100""; this seems to correspond somehow to the corresponding functions in ezgraver.cpp versus ezgraver_v3.cpp. What should I do to get the CLI version working?
Thank you!

[sleptew]

I've tried re-compiling the CLI main.cpp file with an updated reference to ezgraver_v3.h instead of exgraver.h, with the hope that this would cause the CLI version to invoke the v3 protocol functions - which, as I mentioned before, seem to work - but the CLI version still invokved the v1 protocol functions, which didn't do anything with the DK-8-KZ. Any ideas as to what I should do to get the CLI version of EzGraver working with the DK-8-KZ?

[onebeartoe]

sleptew, I had (other) issues with the command line as well.

camrein directed me to the unix_cli_fixes branch in this issue:

#45

See his reponse from Apr 10th.

That version of CLI app works with an Ubuntu 16.04 laptop setup and a Raspbian Jessie setup I have at my pad.

Good luck man.

[sleptew]

onebeartoe, thank you for the reference. I've downloaded, compiled, installed, and run the command-line version of the unix_cli_fixes EzGraver branch. The only difference in behavior when I try resetting or homing the DK is that the commands run to completion; the same v1 protocol information is printed in the terminal window, indicating that this branch still uses the v1 protocol as opposed to the v3 protocol which the UI version uses - which DOES work on this machine. I'd like to get the CLI version working for a project, though. :-/ Any other ideas?

[onebeartoe]

Ah okay. I missed that you are trying to configure a different protocol version.

Maybe try that same code change you mentioned you did in the other branch, if you haven't tried already.

But now I am more interested in what you are doing. I want to get/poll the status of the printer for this Web app I am writting that uses the CLI as a system command to control the engraver.

https://github.com/onebeartoe/electronics/tree/master/neje-engrave

Does the V3 protocol provide engraver status, like percentage complete of a job?

[sleptew]

I've tried the code change mentioned (referencing ezgraver_v3.h instead of ezgraver.h). Didn't make a difference. As I've not been able to get the v3 protocol to work yet in command-line mode, then I have no idea if the engraver provides an ongoing status while it is exercising a job....if I do get it to work, I'll try to update this thread to let you know.

[onebeartoe]

Sounds good, thanks.

[firstel]

any news on this? - i also have this problem. I also tried a new driver from here for my Mac Pro with Mojave - https://www.mac-usb-serial.com/dashboard/

Is there any logs where I can see where this is getting stuck?