I am building Lowrider version four and I’m having trouble with connections. This is my third home built CNC. I built with JD‘s plasma, cutter and Primo. I have got both of them working consistently and had to already learn two different software and now with fluid I needed to learn another one.
The plasma cutter works on Bluetooth and connects first time every time. The Primo has SK pro and connects USB first time every time.
where can I find instructions on how to set up Bluetooth and USB? I would like to try these just for troubleshooting purposes.
One picture is the controller in the wiring seems to be plenty of clear of the antenna. The second picture is my satellite for my wireless. it’s like 6 feet away.
Przemyslaw and Paster Joe seems to have similar situations
just randomly stops communicating and I have to reboot. I cut my struts without a hitch. I’ve done a couple other little projects fine.
I want to cut my torsion box, but I don’t wanna waste for my sheet
I kind of feel like you did not read my question I have been to that page. I even showed pictures of my set up. I have cut my struts so it’s evident that it works sometimes. It just quits.
I thought if I used another type of connection.
I could troubleshoot to see if it was my wireless or if it was my set up is this not wise?
Is there any instructions on the Bluetooth set up?
Is there any instructions on USB set up?
I understand wireless through fluid is the best but if it doesn’t work for me, what good is it? I feel like just going back to SKpro added expense and all.
When you use the wireless you are just starting the file that is on your memory card. After than, wireless is not needed again. So if you hit “go” and it started moving the wireless works.
only in the fluidNC wiki, you need to make firmware edits.
The USB is active, but it only gets you a terminal or a connection to a program like lightburn or CNC.js.
Wireless is the most stable way to start a file.
It very well could be a gcode issue. Do you have issues using my test crown file?
Can you let us see what the first dozen or so lines say when you run $SS in the terminal. If you are running an old version of FluidNC there is a chance you are crashing your machine trying to connect to it multiple times during a job.
The other option is a loose wire.
The other option is bad or paused Gcode.
That is not how the wifi connection works. I hope my previous comment clears that up.
That means most likely you have a Gcode issue. That could be as simple as a tool change you did not mean to do so it is paused and waiting for input, or just bad gcode.
What does “disconnects” mean to you exactly? What does it do?
How much joggin around are you doing, are you button mashing and sending a ton of commands at once? Run my test crown file in the air several times and see if you have any issues.
Are you certain you only have one device connected to the jackpot? have you ever signed in with another device and now they are fighting to log in?
Are you using the captive portal, the one that pops up, or are you going to 192.168.0.1 in a real browser window?
What type of device and browser are you connected with?
Curious what Bluetooth controller and client setup you have that’s reliable for you?
Like Ryan, I would like to confirm if you’re connecting from PC/tablet/phone directly to the JackPot’s ESP32 “FluidNC” network, or, if you have configured ESP32 joined to your existing home network via the Satellite (WiFi access point/extender) in your earlier photo?
Personally, have been reliably using a relatively cheap tablet (with BT keyboard) that connects directly to my ESP32’s “FluidNC” AP.
Lately, I’ve been using a PC which I CAD/CAM on, the tablet has to be off though, I can’t have more than one device trying to connect. If you mistakenly have multiple devices trying to connect, then they’ll take turns being unexpectedly disconnected by FluidNC.
My (dual homed) PC has wired network connection and a WiFi adapter, I configured the WiFi adapter to connect to ESP32’s “FluidNC” network, but also changed the ESP32 gateway IP to 1.2.3.4 instead of the default 192.168.0.1, this avoids confusion and unwanted traffic going to the memory/compute limited tcp stack on the ESP32.
Also, I used a wifi analyzer app to identify and fix crowded channels, ended up explicitly configuring wifi channel 11 for my ESP32 to reduce congestion with my other home networks.
So with my JDs garage I use openbuilds via bluetooh.
I have been using an Old windows, 10 laptop Toshiba. I had a Wi-Fi extender for my security cameras. It worked fine for that so with my problems, I have put in a mesh with a satellite in my garage.
I am hook directly to fluidNC
I tried to iPhone 6 would never hook up just this afternoon. I hooked up my latest lap laptop two month old HP.
This afternoon I brought down my new hp Laptop and it seems to be a lot better. I did five air crowns 4 of five went through The first one stopped at 60% also cut some foam
I have done the Z tests it seems to run G code fine but if I sit around, I go back to it. It’s nothing works. I have to shut it down and restart. I ran five crowns back to back no problem, cut crown, and foam picture on last post
As far as Button Mashing not so much The only G code I know is G 92 x0 y0 z0 and Jogged it to far end and side
Okay, remember now it is not the wifi if it stops on the crown. Something else is wrong. Unless…You still have all of those devices trying to connect at once, that will overwhelm the esp32.
Again. The connection is only needed to start a file, after that nothing is using wifi unless you are constantly refreshing it or trying to connect with other devices at once.
You are not using your mesh or anything else, you are directly connecting to the ESP32 over a wifi connection. Direct from the esp to your wifi enabled device.
You are on the most recent tested release so you should be good to go here.
Just to say it one more time, do your best not to constantly refresh the connection and I highly recommend only using one device, to make sure nothing else is trying to connect I suggest changing your ssid or password so nothing else can connect.
