camrein / EzGraver

Simple multi-platform management software for NEJE laser engravers.
MIT License
132 stars 37 forks source link

Comment and trouble similar as Issue #12 NEJE DK-8-KZ cant transfer data correctly #34

Open Jazzjerry opened 6 years ago

Jazzjerry commented 6 years ago

Hello Camrein,

I absolutely respect your effort and other peoples same mindmap about making the cheap NEJE laser engravers accessible to the Linux users. This is where this type of diy machines should originate.

So I only use linux, and saw this real cheap machine and had a look to see if I would be able to get it running and found some backwards engineering... some scripts and your perfect effort to actually get this machine running on my mint machine...

So I ordered my NEJE DK-8-KZ build by Trustfer hoping I would be able to get it to burn my idears.

And so far... It has burned the test butterfly that was preinstalled on its eprom many times...

I cant seem to get the data connection needed to actually send a new Image 512x512 px to the eprom.

Your EzGraver 3.2 software recognizes the serial connection of my NEJE DK-8-KZ perfectly.

So I try and connect.

connecting to port ttyUSB0 with protocol version 2 connection established successfully loading image: /#####/####/Downloads/ezgraver source/EzGraver-3.2.0/screenshot.png erasing EEPROM uploading image to EEPROM upload completed

So all seems ok up to this point.

The Engraver wakes up after uploading my image through your Gui or Cli..

It buzzes and relocates after a few seconds.

Then I try and start...

Nothing happens.

Not through the Gui nor Cli..

The up down left right reset start pause etc ... buttons have no effect.

When I press the red button on the machine... I starts printing from its eprom and gues what...

It again prints the preinstalled test butterfly NEJE put on the eprom.

I would love to help us out with pentesting and trying to figure out why I cant communicate with the machine. Maybe the protocol has changed.

I tried V1 and V2 of your protocol options that appear automaticly within EzGraver but untill now no result nor any change.

I truely hope you are still reading this and willing to help the diy people on a china budget out to get this working open source.

Sorry to cause this trouble... but hope it might be simple and just something I have overlooked.

I truly hope I will be able to engrave some nuts and autumn nature with poetry on a small scale this year ;-)

I love your work so far. Looks perfect. Hopefully I can get it to work for me.

cybervegan commented 5 years ago

When I looked at EzGraverCLI, I couldn't see any way to select/use different protocols.

I don't know if there's a map of protocols to models, sorry.

On Wed, Sep 5, 2018 at 4:28 AM Roberto Marquez notifications@github.com wrote:

cybervegan and others here, thanks for putting this information up. I am currently looking to use the progress feedback that the Neje machines give off while engraving.

With the different protocols (and code around them), I think it would be a good idea to have a profile to select for each Neje machine.

I am working on a Web app that is a wrapper for the CLI verison of the code.

http://electronics.onebeartoe.org/3d-realization/laser/engraver/neje/engrave/

I don't mean to hijack this thread, but is there a breakdown of which EzGraver protocols work with which Neje machines?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/camrein/EzGraver/issues/34#issuecomment-418587970, or mute the thread https://github.com/notifications/unsubscribe-auth/AHTZwwzA50ksZGq1qRoJrdhpTbmDN221ks5uX0T4gaJpZM4PiAIx .

onebeartoe commented 5 years ago

Yeah, same here cybervegan.

I guess I more meant that it would be useful to be able to select a target protocol and/or model.

bitmuster commented 3 years ago

Hi all,

I was able to get my hands on a Neje DK-8-KZ with the new protocol. After sniffing the communication with the original software I was able to write a python script that can engrave images. It is still in an early/hack state but gives some insight: https://github.com/bitmuster/nejePrint/blob/new_protocol/printer_new_protocol.py

Other files and test-image are located here (forked from AxelTB/nejePrint ): https://github.com/bitmuster/nejePrint/tree/new_protocol

The image size conversion is strange: A square image of e.g. 451px (max size that the orig. software accepts) translates to four values : 0x04 0x38 0x04 0x33 . Instead of converting 451 to 0x1c3 they split it into 400 and 51 (0x33) -> 0x04 0x33. 0x04 0x38 is just the image width rounded to the next multiple of 8 (456). Somewhere between sizes of 127 and 180 they seem to switch from a single byte to two bytes (facepalm!).

Hope that helps Regards Michael

cybervegan commented 3 years ago

That's great news. Thanks for putting in the work. I'll see if I can brush off the NEJE and give it a spin later today. (BTW, can't seem to find my old login details, so using these instead of @cybervegan).

bitmuster commented 3 years ago

Hi all,

I was able to get my hands on a Neje DK-8-KZ with the new protocol. After sniffing the communication with the original software I was able to write a python script that can engrave images. It is still in an early/hack state but gives some insight: https://github.com/bitmuster/nejePrint/blob/new_protocol/printer_new_protocol.py

Other files and test-image are located here (forked from AxelTB/nejePrint ): https://github.com/bitmuster/nejePrint/tree/new_protocol

The image size conversion is strange: A square image of e.g. 451px (max size that the orig. software accepts) translates to four values : 0x04 0x38 0x04 0x33 . Instead of converting 451 to 0x1c3 they split it into 400 and 51 (0x33) -> 0x04 0x33. 0x04 0x38 is just the image width rounded to the next multiple of 8 (456). Somewhere between sizes of 127 and 180 they seem to switch from a single byte to two bytes (facepalm!).

Hope that helps Regards Michael