Wecreat Vision 40W move axis not working

[pandrade82 (Peter A)]

I’m trying to jog either X or Y axis in the Move window and nothing happens. If I enter the code to move the X or Y axis in the console window it works fine. I tried changing jog option from “continuous” to step with not positive result.

I’m using the latest LBDEV file from Wecreat, and using Lightburn 2.1.04.

Also, when I connect Lightburn to the Wecreat device I get a message in the console stating the following “Your laser has been detected as a Wecreat device but you are not using a custom gcode device with the Wecreat device flavor”.

 Thanks, Peter

[MikeyH (Mike Hembrey)]

@pandrade82

Also, when I connect Lightburn to the Wecreat device I get a message in the console stating the following “Your laser has been detected as a Wecreat device but you are not using a custom gcode device with the Wecreat device flavor”.

Search the Forum. I think Lightburn has come up with one that works better than that supplied with the machine. A little bit of searching got me here…

https://support.wecreat.com/hc/en-us/articles/9633347845519-Instructions-on-Direct-LightBurn-Connection-with-Wecreat-Laser

[pandrade82 (Peter A)]

Okay, thanks, I will check it out and get back..

[MikeyH (Mike Hembrey)]

I just ran across this Thread. It may help…

WeCreat Lumos Ultra — controller status report never leaves Idle, streams desynchronise on long jobs

I’ve been building a LightBurn device configuration for the WeCreat Lumos Ultra (WeCreat publishes configs for the Vision/Vista/Lumos but not the Ultra) and I think I’ve found a protocol-level problem worth reporting. Everything below is from LightBurn 2.1.04 on a physical machine, and the captures are public: Setup: Custom GCode device, GCodeFlavor: wecreat, serial at 1,000,000 baud over the machine’s CH340 bridge. LightBurn detects it correctly — “Found WeCreat Device” — and emits WeCreat-s…

[pandrade82 (Peter A)]

I have the most recent version of the Wecreat software, Makeit V3.0.6 and the LBDEV file.

The LBDEV file is V1.0. And have followed the instructions as outlined.

I just noticed something in the link you sent me regarding a version of lightburn that has a GCode

license key -

" If you need to use LightBurn on Vision machine, please buy the one with GCode license key."

I did not realize or see this when I purchased Lightburn, could this be the root cause of my problems?

Thanks Peter

[MikeyH (Mike Hembrey)]

The CORE version is the GCode license version. The PRO version is needed for Ruida’s and Fiber machines. The Pro license works on GCode machines as well as the others.

[JessN (Jess)]

WeCreat_Vision_40W_08_2026.lbzip (30.6 KB)

Please try this device profile and let us know how it goes.

Core keys communicate with gcode controllers.

Pro keys communciate with gcode, DSP, and galvo controllers.

Wecreate vision falls under gcode.

[pandrade82 (Peter A)]

Thank you. I’m having a problem opening the file type lbzip.

I’ll give it a go tomorrow..

Again, thanks for the help.

[pandrade82 (Peter A)]

Okay, I realized after a bit of poking around that Lightburn will import ZIP files as well as LBDEV files.

But, when I try to import this ZIP file it does not display in the devices window as a configuration file.

I have another “Home” computer that I also have a copy of Lightburn installed, not connected to any Laser" and I can import this lbzip file into Lightburn, the only difference between the 2 is my home computer is running version 2.1.02 and my shop is running 2.1.04.

I hope all of this makes sense. This is frustrating to say the least but I do appreciate all the support…

Peter

[pandrade82 (Peter A)]

This is crazy! Now my screen has changed from English to some form of Arabic… I’m totally confused…

[pandrade82 (Peter A)]

I reset my language back to English, not sure what made it change.

I finally was able to Import your lbzip file and NOW I can finally jog my Laser, I’m thrilled, finally.

I will continue with the rest of the setup later…

Thank you one and all…

Peter