Firmware 1.14 is out, you can find it here: Release v1.14 · BarbourSmith/FluidNC · GitHub
We let a lot of changes into 1.13, which is great for making progress, but we let some bugs in at the same time. I am going to work to do a better job of reviewing things and slow things down a bit to prioritize stability and reliability over new features.
Same issue for me as well.
Both of those are things which got added in 1.13, they’re annoying but they are safe to ignore.
The low memory warnings are caused by the machine checking for if there is a new firmware version available which uses a lot of memory and the version compatibility popup is pretty disruptive.
Literally the very first thing that I did after publishing 1.14 was to remove both of those. I didn’t want to change anything else before putting out 1.14 because I just wanted to fix the bugs which were really making things not work and test it. Both of those are annoying, but ignorable.
The popup is so annoying that I actually did update the index.html.gz file in the 1.14 release to make that go away, but if you do the USB installer you won’t get that.
One other change that happened that we might want to roll back is that a lot of the build process is now automatic in terms of adding version numbers which is nice in theory but it makes the system much less flexible in terms of me being able to adjust things.
I agree, I don’t think this is advantageous. Maybe it could be accessed via the setup menu as a check for latest releases.
With the new functionality of being able to power down without having to Retract, Extend,Apply Tension, maybe its time to bring the Apply tension to the front menu. Release tension is fine on the Setup menu.
The new version has changed the trace boundaries to use curves. I preferred the simple rectangle as it was quicker, less jerky and gave the extremes of the outline.
Bar wrote:
Both of those are things which got added in 1.13, they¢re annoying but they are safe to ignore.
The low memory warnings are caused by the machine checking for if there is a
new firmware version available which uses a lot of memory
that should not be using much memory.
There is an option to auto-update now when a new release comes out (if you are
on an internet connected wifi, not if you are in AP mode) and I did that many
times in testing without any memory issues.
and the version compatibility popup is pretty disruptive.
if the versions don’t match, that is correct. how about ‘don’t bug me again
until versions change’ that stores something in preferences?
Literally the very first thing that I did after publishing 1.14 was to remove
both of those. I didn¢t want to change anything else before putting out 1.14
because I just wanted to fix the bugs which were really making things not work
and test it. Both of those are annoying, but ignorable.The popup is so annoying that I actually did update the index.html.gz file in
the 1.14 release to make that go away, but if you do the USB installer you
won¢t get that.One other change that happened that we might want to roll back is that a lot
of the build process is now automatic in terms of adding version numbers which
is nice in theory but it makes the system much less flexible in terms of me
being able to adjust things.
you should be able to just delete the old v1.14 tag and tag the new commit as
v1.14 (or v1.14.1 if you want)
what other issues are you running into?
David Lang
Ian Abbott wrote:
[quote=“bar, post:4, topic:25182”] One other change that happened that we
might want to roll back is that a lot of the build process is now automatic in
terms of adding version numbers which is nice in theory but it makes the[/quote]
I agree, I don¢t think this is advantageous. Maybe it could be accessed via the setup menu as a check for latest releases.
please explain?
The new version has changed the trace boundaries to use curves. I preferred
the simple rectangle as it was quicker, less jerky and gave the extremes of
the outline.
I can see cases for both, is this worth having a preferences option?
David Lang
I personally prefer to decide when and if I upgrade to a newer version of software (any software), so I think moving a check for updates to a button on the setup menu makes more sense, especially when it generates error messages.
I think so
I do as well, which is why I made doing the upgrade an option, defaulted off.
I do think that people should be notified when there is a new version, rather
than having to go and look. And I don’t think it being in the log is enough, we
already see enough reports where the deatils of the problem are clear in the
logs that are posted, but are missed or not understood by the users.
I would not at all object to the alert/popup only happening once per new release
rather than once per boot.
But I also think that we should be able to make it so the version mismatch does
not happen except for people doing manual updates who don’t update both.
David Lang
I don’t think the defaulted to off change made it into the firmware, I couldn’t figure out how to turn it off at all.
I ended up moving it to run as part of the self test, and got rid of the popup. That way if someone is having an issue and runs test they will get a text alert that they have a new firmware version they could try, but it won’t be something that happens in an unsolicited way
Bar wrote:
I don¢t think the defaulted to off change made it into the firmware, I
couldn¢t figure out how to turn it off at all.
the default off is in the firmware, if it wasn’t, it would auto-update and not
give the popup.
The popup only happens if autoupdate is off and there is a new version.
I think the best thing to do is that when there is a new version and the user
opts to not update is record what new version was available in the preferences
file and not give a popup until there is a new version after that.
I ended up moving it to run as part of the self test, and got rid of the
popup. That way if someone is having an issue and runs test they will get a
text alert that they have a new firmware version they could try, but it won¢t
be something that happens in an unsolicited way
there is too much noice in the logs, people don’t read it, so I think we need
something more than that (even if it’s less than the popup each time)
We should also give instructions on how to enable the auto-update (it’s in the
maslow.yaml settings, both what URL to check for updates (which will change when
you move the repo to be under maslow rather than your account), and if it should
auto-update.
David Lang
For the warning, see GitHub:
I like to report things there and for easy problems, CoPilot seems to be able to generate a fix.
