# Issues with version 1.4.9 upgrade
**URL:** https://forum.sienci.com/t/issues-with-version-1-4-9-upgrade/14214
**Category:** š Bug
**Created:** [October 18, 2024, 9:19pm UTC](https://forum.sienci.com/t/issues-with-version-1-4-9-upgrade/14214 "2024-10-18T21:19:06Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@wwitm777](https://forum.sienci.com/u/wwitm777)
#### Post date: [October 18, 2024, 9:19pm UTC](https://forum.sienci.com/t/issues-with-version-1-4-9-upgrade/14214/1 "2024-10-18T21:19:06Z")
The 1.4.9 version has lost some features, damaged others and has a VERY confusing Save data option !!
1. First and foremost are issues with the internal Surfacing functions. This is great for not just surfacing a board but a variety for leveling functions. We run it several times in a row on the same work piece. This successive usage has shown problems we did not have before in prior versions:
a) **Surfacing setups are lost** - in older versions, the last settings used, were
saved as the defaults for the next use. VERY helpful. However, new version
defaults to random numbers for all fields !! X an Y never return the previous
number, but are āroundedā up/down (randomly) by as much as 0.5.
Example: User Sets X=7.0 Y=3.0
Next Surfacing defaults to X=6.76 Y=2.83
itās never the number originally entered and usually NOT the
same random number
We REALLY would like ALL fields to re-populate with EXACTLY the
previous settings - like it used to.
```
b) **Surfacing Step Over** - any value greater than 78% results in a cutting
pattern that does NOT make the last pass to clear any remaining material
when using the Spiral pattern. It always leaves a thin line standing.
Not tested for the Back and Forth pattern.
```
1. **Save SETTINGS vs. Save FIRMWARE** - We figured out why gSender always
loses the āsavedā user data.
Both menu functions SETTINGS and FIRMWARE have a āSave SETTINGSā
function, but each menu function is completely different in what it
does and each āsavesā completely different user data. This is deadly since they
both save to the SAME output file !!! Thus, each Save function KILLS the data
from the other function - WITHOUT the user knowing it.
Obviously multiple programmers worked on the gSender program - WITHOUT
first defining common use of words and the user functions. This is further
complicated because each menu function uses a different User Interface and menu
structure. One has menu Selections and the other has Option Buttons.
The words Save Settings in both do NOT mean the same thing.
In ALL other programs - saving User Data means saving ALL user data - not just
the data from one module or the other. The user rightfully assumes (and expects)
Save Settings to save ALL user data from the ENTIRE program regardless of where
the data was captured or how itās used.
Currently - saving FIRMWARE will kill ALL saved SETTINGS data.
- saving SETTINGS data will kill ALL saved FIRMWARE data.
You can never have ALL of your data saved.
2. Restoring the PROBE Touchplate Type in the SETTINGS menu always defaults to
factory option Standard when importing āSaved Settingsā.
On second thought - This maybe related to the issue in #2 above.
We save using the FIRMWARE function. Guess we are shooting ourself in the foot ??
3. Whenever we hit the PAUSE button or the EMERGENCY stop button, all motion stops
leaving the bit burning into the wood. Is there a way to force the Z to back off the
the wood when these happen ?? We need something like the Safe Clearance option
used in jogging for these kinds of āstopā functions. Most of us do not have the
for SuperDuper controller board.
4. If the Surfacing function is used too many times in a row the program crashes !!
At some random point if you go in and out of Surfacing too many times (our guess
at the cause), selecting Run on Main Visualizer will result in the work area turning
all white with NO data or program info or buttons (Test, Run, etc) . At that point the
program can still can reenter Surfacing but the work area never recovers. A complete
closure and restart of gSender is required and all data is lost.
Looking forward to any and all feedback on these. Anyone else have these issues ??
---
### Author:  [@chrismakesstuff](https://forum.sienci.com/u/chrismakesstuff)
#### Post date: [August 12, 2025, 3:57pm UTC](https://forum.sienci.com/t/issues-with-version-1-4-9-upgrade/14214/2 "2025-08-12T15:57:29Z")
Hi @wwitm777 thanks for all the feedback, Iāll see if I can help out:
1. Regarding your a) point, this was definitely an issue in some older versions which I just double-checked in 1.5.3 and itās confirmed as being good to go again. To your point b) we also just made an adjustment as of 1.5.3 for this final piece of material, and it should be getting cleared now
2. I agree this is confusing which is why we redesigned 1.5.# versions to make this process much easier to understand. There are still two different save options, but basically one of them is saving your machine configuration (the firmware settings that stay with your machine) and the other is saving your gSender settings (these stay with your computer), thatās why it exists as two separate files. Depending on your situation, someone might want to save only one, or the other, or both
3. My explanation for 2 is likely the cause of the issue youāre seeing for this
4. Unfortunately this isnāt possible without having the SuperLongBoard since itās a limitation of the older grbl firmware where moving up and out of the way in an emergency just isnāt how the firmware is designed to work, aand there arenāt really any easy workarounds for this. gSender is also not capable of solving this issue since once you pause or stop the machine the firmware doesnāt allow gSender to talk to the machine anymore
5. I think that this shouldnāt be an issue anymore. I remember having an issue where we realized the surfacing was using up more and more memory in the background but thatās since been fixed.
I think most of what you mentioned not many other people had these similar issues seeing as no one else commented on this post, but I hope my explanation clears up most of what you were experiencing š
---
### Author:  [@chrismakesstuff](https://forum.sienci.com/u/chrismakesstuff)
#### Post date: [September 3, 2025, 9:49pm UTC](https://forum.sienci.com/t/issues-with-version-1-4-9-upgrade/14214/3 "2025-09-03T21:49:15Z")