Ok I’m going crazy here. There has to be something simple I am missing.
I have a jackpot board on a Primo with a 20w Diode laser on it. Has been set up this way for over a year. I run it from lightburn over USB. Never have any issues. Came out to use it 2 days ago and my computer was just acting stupid. Did a windows update and updated lightburn. After that I couldn’t get lightburn to open at all. Ended up having to reset the computer and basically start from scratch. No biggie, got it back up and running, installed lightburn. Now lightburn wont talk to the jackpot. I know my USB cable is good. I can open up fluidterm and talk to the jackpot no problem. But lightburn just wont do it. Yes I am verifying the correct com port. Sometimes it will pull up and give me “most” of the start up stuff in the console on lightburn but even after that if I run $SS I get nothing. Also no movement or anything. What am I doing wrong here???
Considering I am not even sure about what you are talking about, I’m going to say no. Its probably something I had to do a year ago when I originally set this up, but I have a hard time remembering what I did 5 min ago much less a year ago
Still not working. I tried everything from 9600 to 250000. After that I switched over to fluidterm and was able to connect no problem. Looks like the baud rate is 115200
Good connection and verified USB connection to PC for the jackpot. Sounds like you know the com port number. So this other info may not apply. Did you switch the connection port on the PC and change the assigned port number? I had one piece of software totally refuse to connect to any com port numbered higher than 8. I switched the cable to a different port one time, it got a higher number and refused to acknowledge the device… Put it back and it worked. Is it not seeing it all?
If the com port connects and some communication occurs, but it hangs… Sounds like this more what you are experiencing. RTS and CTS signals control data flow with Io voltages to say they are ready to send it clear to send data. This is hardware flow control and if set wrong, you could get some data and then it will hang. Software flow control is xon/off and I believe it keys on a specific character or character sequence to allow communication to proceed. Common serial settings are 8N1, none. Not going to get into all of that, but it should match up. Where you are using a virtual serial port over USB, usually just the baud rate needs to be accurate and the other parts are default.
Is the USB supplying power to the board control chip or is it powered by the 24V? If USB, the 5v power could be of concern and the board is rebooting part way.
Is there anything else trying to open the com port while lightburn has it open?
Side note: if your esp has a knockoff ftdi chip, newer windows drivers refuse to talk to them so you have to force install an older driver version, though if you have console control, that likely isn’t the issue.
Nothing has been moved. Its attaching to COM4, and that’s the same COM4 I use to connect with fluidterm no issues
I haven’t changed anything in regard to any of this stuff. All well above my pay grade. I have verified the correct baud rate.
I am turning on the 24v power supply to the jackpot then hooking up the USB cable. That way the TMC drivers fire up before the ESP32 does.
No. I have forgotten fluidterm open once and it gives an error that it cant open the com port because its already active.
its a brand new V1 ESP32. Just changed it out because the USB port on the original V1 ESP32 became Bluetooth It is on its way to @MakerJim in for surgery along with a few other boards.
are you saying to set that to 400000??? I have made no changes to the config file so I don’t know why that is popping up. I went in there to try and set up STA and see if lightburn can connect over WiFi, but I cant do that because of this “incorrect value” for the i2c frequency
The microcontrollers I’ve messed with usually have 2 frequencies for I2C communication. 100 kHz and 400 kHz for normal and fast mode respectively. Flip a coin.
Googled it and they now have fast mode plus at 1 MHz and high speed at up to 3.4 MHz. So you might be:
100000
400000
1000000
3400000
It is on its way to