I’m in favour. I was trying to figure out a combined LR/Primo firmware configuration, but I can’t get past the difference in homing the X and Z axes. Maybe with a dedicated Z probe, but even then…
X1, Y1, Z1, X2, Y2, Z2. If someone wants to use a channel for a rotary axis they can figure out which one gets to be “A” themselves, I figure. It isn’t a standard option in any event.
Edit: end stops are a bit less clear. Because for the LR, we end up with 2 Z_max stops and one Z_min (probe) stop, those might be better labelled differently. Keep the axis names out of it entirely.
Unless you can have a dedicated probe connector. If there aren’t any more pins, maybe jumper selectable? Have the Z probe port either be X2 or Z2 by setting a jumper? Then the 6 regular ports can be labelled to their nominal motors. Of course this requires hardware changes…
If not, then it would be best if firmware uses Z2 for Primo machine config, and X2 for LR machine config. (Basically the motor port we aren’t using.)
I agree with @azab2c . If the purpose is to be Fluid (…) with the machine it is used on then straight up Motor1, Motor 2, etc makes much sense. BTT did a good job with their new ports and the port labeling and pin mapping diagrams IMHO
I kept the important ones that you might use on the front so you can see them and the rest on the back. I have been thinking about labeling the ESP pins but almost every board I have seen has them labeled already.
I like this as well. Each driver is independent, and the configuration determines the use of each driver.
So, labeling motor 1, 2, 3, etc on a board expected to support multiple and different use cases seems to make the most sense and have the least number of user-induced errors from hooking it up “as labeled” instead of “as needed.”
Noticed some minor tweaks needed on the V1E store. One is a general matter, and the other is specific to the new custom board.
Re: general tweak: On any listing that is out of stock and offers to sign up for notification when back in stock, the resulting confirmation is light text on light background and not readable. This may well be related to me running in dark mode, and there would be a CSS method of handling, but it may or may not be worth the effort:
AP mode works great.
Station mode (joining my home wifi) is very bad.
I am guessing maybe when my local network is very quiet, station mode sorta works, but if there gets to be some chatter on my LAN then the ESP32 network stack gets messed up, even if there is no visible Low memory error.
The AP mode keeps it quiet and the only devices are the ESP32 and my PC with wifi dongle.
It’s a relief to have found this. I won’t be using station mode for the foreseeable future.
Are you getting specific errors? Or the out of memory?
I was researching, the problems i saw were is ap and station were on together or bluetoooth and station. So i may not be looking for the correct thing. If i were to buy just an esp would i get the same problems? Or is it happening only when machine is running?
I am pretty sure AP and station are not on together, although there is a mode where station falls back to AP if it can’t connect to existing wifi. In my case it was successfully connecting to my home network and FluidNC was not offering an access point.
I don’t believe bluetooth is on. I am using the wifi version “FluidNC v3.7.5 (wifi)” and I am not seeing any mention of bluetooth anywhere in the boot messages. I think that means there is no bluetooth active although the absence of mention doesn’t prove that bluetooth is off, but I think it is off.
In station mode I was getting lots of inconsistent behavior, not just problems when running a job. In AP mode, I have not seen a problem yet.
So i just went over to discord. I saw the post you referenced. I am sure you already did it but the part about disabling bluetooth? Also it was interesting about broadcast as many devices use that, in fact older versions of network protocol almost all was broadcast, hey who has ip …, oh i have ip… It is chatty. Only way to avoid that and use station would be a vlan and most will not know how. Then the addition of please sponsor because i have 2 days makes me wonder if it get fixed!
have you had any issues with jobs loosing connection half way through?
It says they are using expressif stack, i will see if i can find that
I found the expressif stack. Wow. They have alot built in. It can handle ipv4 and ipv6. I am looking to see if somehow you can drop one. In memory terms you would want this as simple as possible. They also have ip blockers. I just saw it and not sure how to use yet but if something were chatty ( browser based as above ) you could block that communication. (a primitive firewall). I am on my kindle. I will try to get to garage and do some more research!
Anyone tried alternative WebUIs for FluidNC?
The default one is pretty good but I feel it lacks some functionnalities in tablet mode (feed rate and movement speed adjustment, file list needs to be manually refreshed, …)
I was thinking about trying this one:
Looks a lot more complete, plus it has keyboard bindings for Jog and such…
Easy way to make a pendant…
Helped add/tweak custom keyboard bindings for jogging and macros to ESP3D Web UI earlier this year (~Jan), am using for my LR3. Was hoping Fluid NC continues to forward integrate ESP3D changes, and wasn’t one time forked off an old snapshot?
I should probably RTFC and dig through fluidnc discord to better understand.
