I get that, and certainly understand the risk. I just wanted to feed that back to Ryan while the thread was focused on people making that choice.
In a perfect world, I like to assume people that are competent enough to think they can tackle building themselves a CNC are also competent enough to come ask for help with issues they can’t solve on their own, but I also know that is maybe asking too much
Edit: In re-reading this, I just wanted to make sure this didn’t come off as condescending, as I didn’t intend it that way. I just meant that it’s a big project to attempt, and this forum is one of the only reasons I was willing to risk the time and money I was going to need to put into it to use this as an entry project into this world.
Hopefully, I’ll get using it a bit more soon and can help feed back any issues and help bring the confidence up.
I haven’t run with 3.7.8 yet, so I don’t know if this has changed, but my experience with prompts is only that it’s some text down in the log. It also took me a bit to realize that there was a little “Play” button to resume, so originally I was going to manually send the “~” command every time.
I also prefer a screen local, so I have been toying with the idea of taking on a project once my other ones are done to take this project as a starter:
And make me something better suited for how I use it. If I do, I will start a thread and maybe it can be a bit of a collaboration if someone wants to work on it as well
I see a new email or forum post about them switches every 50-100 boards.
So far most have been happy to just pop off the LED and keep going. The LED obviously doesn’t do anything. It will still turn on and off even if the board doesn’t recognize it. So no harm in popping it off.
Yeah, I am not super confident in a test. It seems it is pretty hit or miss. But yes, if I get a batch right now…I guess maybe I will get a small batch…the next batch should be fixed.
Is there some kind of fixture or test jig that we could come up to make your loading/testing process more robust? So you catch those 1-2% and never get them out the door? Maybe this would be a “good thing to work on” note your poll about that… and maybe it is something some of us could help you with ideas on.
How big is a big batch, and how reliable is the supply chain for you at the moment?
My worry is they fix the board and that revision ends up breaking something else. No one ever just changes one minor little thing even like that goofed endstop circuit. They always change other stuff too.
Maybe a big batch now, lets figure out how to get your defect rate at shipment to zero without major workload increases for you, and meantime a small batch of the new boards so you can learn what issues those might have.
Also, at some point you’re going to have to bite the bullet and figure out how to do kits with the Jackpot.
They are just changing some resistors they are not even going to edit the revision number of the board (they should), so they should not be changing anything else.
Oh that is coming soon. This week 25 or so went out the door, the firmware is working good, it’s coming soon. Just want to see how everyone’s unique shop workflow handles Wi-Fi connections.
I’m going to start testing station mode with 3.7.8 later this week. My PC is a desktop, so I can’t carry it out to the shop with me. My WiFi doesn’t reach the shop though so I have another router on order to set up a mesh node to extend it. Should be delivered tomorrow.
It’s roughly an 80-100ft walk each way to make changes/upload/etc with the SD card…And that is getting old real quick while trying to test and work out my process lol
I did a short test with a spare router local in the shop last night and it seemed ok, but I couldn’t get my Desktop to connect to it through that older router in working in repeater mode.
Just remember after any testing you are doing that turns into make my gcode file, walk to the CNC insert the sd card and watch the machine work. There should never be a ton of back and forth in daily use. If people are worried about walking to get the card to load the file initially get a second card and always have one at the Gcode computer. That seems so much more simple than setting up a whole separate network to me (but that is just me). Sometimes I work upstairs on the other end of the house but I still have a SD card with me.
When I use it, my use case, I log in to board to start the file, stick around and clean or answer emails, then sign in to do any tool changes and that’s it. Just like with the SKR, rambo and ramps. To me the benefit is the user interface is fully featured (easier to use, half the price, and easier to update and configure), not that I can push a file remotely.
BUT, this is why I am not pushing this board hard yet. I do not understand everyone’s workflow. Also probably why we are in this situation. I never cared to test STA mode more than one time, I don’t want it on the same network as a bunch of rowdy/curious kids on random devices.
I agree that as time goes on it won’t be as much of an issue, but I’ve been doing a bunch of short tests and having to walk back and forth a lot as I’m just familiarizing myself with it.
In the end I suspect the convenience of STA mode will dwindle, as I would have to go power on the machine first anyway, but it’s just enough for now to help not have to park the machine in a safe spot so the router doesn’t crash down, power down, and replace the card so many times.
I’ll check, I think I already had the August 10th version and there were no newer builds when I upgraded.
Edit: I see you committed some yesterday. I’ll update tonight.
But this is another reason for STA mode for me. I keep having to go steal my wife’s laptop to do config changes etc that, as far I’m aware, can’t be done from the SD card. Or can it? I didn’t find any way to copy files from the SD card to the file system in the interface
They said they are finally fixed, they changed these resistors from 4.7k to 1.5k. I can’t find the original thread where this was worked out. Is this correct?
Oh, dear lord. I’m not even an engineer, and that makes my teeth itch. Of course, my next big project, after moving our application to the cloud, is basically rewriting it as a massive revision control system for tolerance analysis…
Had some long and involved discussions with real engineers about versions, revisions, documents, drawings, illustrations, sources of truth, etc.
This is going to make future troubleshooting a nightmare. No way to know if the user has the new resistors or not. Most of the time its faulty wiring. But will be harder to prove when we dont know for sure which board they have
Anyway, lowering the pullup resistor value is the answer. I used a second 4k7 on my MKS board having the same issue and it worked (I think I listed it as 470 in my thread) because it was basically halving the series resistance.
We’ve been addjng a 1k5 resistor in parallel with that 4k7 which I get about 1k1 effective resistance, so this is a little higher than the “known good” solution, but still in the ballpark.
Someone remind me if my math on parallel resistance isn’t right… 1÷((1÷R1)+(1÷R2))
The resistance value just has to be high enough that the pin will still drop to logic low when the switch is closed. Any higher than that is basically power/current saving while the switch is closed. As a result the boards with the 1k5 will draw a little more power than the ones with the 4k7.
Given that it is still an intermittent problem, 2k2 or even a 3k3 substitute would almost certainly solve it (just choosing E12 series values.)
