I did see a similar issue in a post around using the WiFi, while the laser WiFi is configured the connection in use is USB. I wonder if having the WiFi configured could be related to this bug
I implemented the WeCreat support initially, and one thing I am still a little frustrated with WeCreat is that they didnât create a proper bundle file with the device configuration for the Vision.
Iâm attaching a bundle file of my config for the 20W device, please try and let me know if this resolves your issue at all? The reason Iâm frustrated is because there are a few tweaks that I have made that seem to work better than the configuration they provide with their .lbdev file.
@goeland86 I will give this a go a bit later tonight, I also have a support issue open with WeCreat and have them pointed to this post. If this helps I will help apply that pressure, I have 4 start (down from 5 star review on their amazon listing) that is going to need to be updated with this entire experience so I would like to think that matters to them being that 16 people have already found it helpful
@Aaron.F sadly this did not help the issue. I was able to / had to re-process the camera focus and that worked but when I tried my next bit I get the same results.
being that the camera project did burn and the one I am doing now did not it occurs to me it might be related to the âcut selected graphicsâ feature as I do have that on and am only trying to process the selected portion of my project.
when I disabled that it does appear to process as expected.
Is this a known issue I should already know about?
Is there a known issues / supported features list?
@Aaron.F && @goeland86 overall findings thus far is that the âCut Selected Graphicsâ does not work for the WeCreat laser.
Sorry, I donât follow you. Do you mean the âCamera Lens Calibrationâ or âAlignmentâ?
@Aaron.F, so the WeCreat camera is âpre calibratedâ so it was the âalignmentâ process that sends over the 1 â 4 circles. That sent successfully and was my hint on the âCut Selectedâ as the underlying issue I was having when trying to process my project.
Version 1.7.04 just got out. Can You give it a try with the âCut Selected Graphicsâ? I hear, there was an issue (not WeCreat specific) that got fixed in the latest version.
No itâs the new bundle format that was introduced in 1.6 I think? Might have been 1.7. being on the other side I forget what was released when if I donât look at the release notes.
You should be able to find it in File->Bundles->import bundle
Have you had any luck getting Wecreat to work in Lightburn with overscanning and Scanning Offset Adjustment enabled?
It runs fairly well without those turned on, but images are extremely blurry and uneven. When I enable one or both of those the machine slows way down, then head getting a little jerky, and jobs take about twice as long as estimated.
Sorry to hammer you with questions ⌠Been trying to get Lightburn to work with this thing for months and was comparing your setup to the one Wecreat provided.
In the Custom Gcode tab they have M16 as part of their Start Gcode. Noticed that this wasnât in the bundle you created.
Whatâs that command do? Curious what difference having it in there makes vs not having it.
Oh. Thatâs a great question - I donât actually know. They didnât really give us a full g-code breakdown of their firmwareâŚ
I remember I had noticed one command that was necessary that I had missed in the start and end gcodes⌠After launching a job with it I realized it was to turn on/off the toolhead fan (i.e. to cool the LEDs). But now I donât remember the exact command off the top of my head.
Iâll be back in the workshop on Monday, and can double-check it on my device then.
My suggestion is to add it in - if they have it, itâs for a reason.
Double check the end gcode as well?
Iâll try to update my bundle file ASAP so others realize that the original bundle I provided had issues.
Basically the big difference should be in the Probe Z section - they didnât set one up, where I added in M103 as the command thatâs needed for that.
Now keep in mind that it will run the focus sequence above where the toolhead is, not based on where the design is laid out in LB like it would in their Make It! software.
The end one is there. I know the other two start have to do with starting the head and exhaust fan. Just wasnât sure what the M16 did.
The Z stuff wasnât enabled, but I knew from past experience messing with them which to turn on and set the z offset in layers.
I started using the command to move the laser to the design and run the focus to get the material height, setting it in layers, then hit stop to sent the laser back home. I can only really get the camera to be consistent when the machine is all the way up. Iâll then place the objects and start.
Everything else looked pretty much the same as the other custom device settings Iâve tried that didnât come from wecreat.
