Hello
Hope it’s ok to follow up on this thread
I have read and tried to search for information.
I have a similar problem and have done some testing but will explain.
1: Changed the position of the laser and with that bought a new USB, 5 meters.
I have tried switching back to the original USB but the same problem as described in the thread.
2: Have also extended the cable to the Laser module!, maybe this is where the problem lies??
When I run a program now with the laser at 0% it works without a problem!
Is it the case that the cord for the laser is adapted to the Neje master 2s Max?? and how can I get around this because I need a longer cord!?
Grateful for answers!
baud rate is as you wrote 115,200, but have tried with long and short USB cable, without Laser (0%) without the machine hooking up, but when I have the laser on it hooks up with both long and short USB.
so I will shorten the Laser cord again and test tomorrow. Will get back to you, thanks for the reply!
OK, but, you don’t think it’s because I changed the length of the “Laser” plug/cord, it was after I did that that the problems started, that and I changed the length of the USB cable, now trying to take it one step at a time so I can double check what works and what doesn’t
“Try 9600, it may be much higher”
what does “9600” refer to in “115,200 baud rate”?
If we were speaking your language, I doubt I could get ‘hello’ across to you… you’re doing fine, we’ll adapt…
Baud rate usually refers to bits/second being transferred across a communication medium.
It’s usually in either bits/second or bytes/second.
The USB uses the value to set the communication equipment to understand what the other end is saying…
You should not the the high bit set output on your console… these always end up being a mismatch in communication speed…
If you can find someone that knows your machine, they can probably tell you.
I use commas to separate the 1000’s separation, not as a decimal, as you may be interpreting them… 9600b is also 9,600 as 115200 is sometimes written as 115,200 … it’s an American thing…
I have a ‘watch’ that gets it time every night from WWVB, the time standard in the USA. It takes 57 seconds to send 57 bits with power shift keying. It has a baud rate of 1
This comes from the controller, so the baud rate is correct here. For some reason, the controller is sending you data you can’t display.
From your post, I’m not sure what to try…
Can you type $$ in the console and post what it outputs? It should output the controller settings.
Also try $I
Maybe one of the people good with grbl knows a good solution, there is a reset command, but I’m not sure it’s applicable here… maybe @berainlb can tell you…
I looked at an unboxing video that showed the two Neje drivers and they’re running at different communication speeds (Baud Rates). The video is toward the end of this page.
At the 9 minute mark the speeds are shown to be locked to the grbl version installed in the Neje.
One of the grbl 1.1f versions is built for 152,000 - the other 38,400
It may be of interest to test the 38,400 baud rate setting.
To access it in LightBurn,click Edit in the top row - then click Device Settings (toward the bottom of the list). The Baud Rate is in the lower right hand corner.
With the correct length/original cable to the laser it works without problems!
So I guess I have myself to blame when I change things you don’t understand
thank you for your effort!
