The Jogging resets to 0ās out of the blue for the āNormalā speed, and jogging on the Y axis would sometimes throw a Homing error that wouldnāt let me get out of it.
Not going to lie, I was flustered by these bugs, I thought 1.5 was an update/upgrade to 1.4x and nothing to be concerned about updating, not a new (essentially 2.00) version on beta testing with bugs and kinks to work out.
I was going to work today on a piece, but will wait to either see a more stable 1.5x or revert back to 1.4 if even possible.
I have worked long enough in the field to know there was a time when updating was not something that was normal. If a product worked, it could become better, risking it got worse. I always keep in mind that in worse case the thing being updates will stop working. And with that, I do not update unless I see improvements I need, or I have new hardware that will need a new install of the software that has new updates.
I do not need grblhall, darkmode, new looks, autoconnect, or anything that was added after gsender 1.2.x.
If I would see something I am willing to take the risk of updating and things didnāt work after that, I would see it as my own fault. I hĆ”d a workimg machine, I updated, thus it is I who broke it.
I will never update unless there is a backup plan, like going back to the old version. This would mean having a known working install on a secondairy pc or at least access to the old software and a manual that will guide me to mitigate known problems asociated with re-installing a known working version.
Would I be frustrated if I updated and my machine stopped working? You bet ya. I would be frustrated because I clearly didnāt do my homework on my backup plan.
Would I direct my anger at the developing team? Only if the update was mandatory, pushed through without notice or if I payed big bucks for the software.
Luckaly sienci is open source and any older version of the software is available on github. Hereās the 1.4.12.
First, thank you for pointing out Version 1.4.12 and the additional need-to-know piece, I appreciate it, saves me research time.
But secondly, kindly do not put emotions in my post that are not there, Iām not angry, and I did not direct anger towards anyone.
The previous release had bugs of itās own that Iāve been struggling with as coordinates reset upon pausing or stopping a job (for which I was provided a solution that didnāt exactly work, no biggie, I worked around it), so I did update in hopes that would get fixed as said workaround does imply a bit more work (in a nutshell, making sure I can always use the probe to reset coordinates, and thus not being able to use the center of a piece as I wonāt be able to get back to said coordinate once a job starts and loses the coordinates).
Iām not running a business (though I do hope I will soon) and thus this isnāt a showstopper for me, however, it was flustering (and it shouldnāt be a sin, nor unprofessional to mention it) seeing those errors, especially as this is not listed as 2.0, but still 1.x update.
Actually, and funny that weāre talking about thisā¦ I specifically chose the word āflusteredā because I felt the word āfrustratedā to be too strong and not what I wanted to convey, so again, not angry by a far shot, but emotions in written word can be easily misinterpreted.
Having said that, I completely understand gSender is free (for which Iām extremely grateful, especially given the quality of it), I expect bugs to happen, and similarly, I expect said bugs to take time to be addressed.
I was experiencing this as well. I went into the setting under Jogging I believe and there you can set the speeds for Rapid, Normal and Precise. I havenāt run the CNC yet to see if they persist.
Often when emotions get read in tekst, itās pointing towards the reader and not always towards the writer. Itās the first law of poetry (when the poetry goes a bit more deeper than roses are red..)
I am an old man reading in my thirdish language and am not always taking the time to dive into the poetry ending up reading what is not written. I took flustering for a typo, didnāt even know it was a word. So Iām sorry I brought my inner brewings out to you. I should have listened to my itch to delete it and keep the positive core -the links-
Anyhooo, that out of the way. I am a centre zeroĆ«r aswell. I often have stock that isnāt square or even organic in shape and then the ācentreā is the ultimate place to be. Since I like to have a set workflow, all my stock gets centre zeroed (the odd one out being tiling jobs.) I donāt have limit switches so thereās no recovery possible after bleepups. I also do projects that include both laser and milling jobs, sometimes needing to remove the project of the machine bed inbetween steps to baptise it in holy water or do some magic dance around it, or something like that.
When first setting the xy zero, I place a single V60 dimple on the exces material that gets cut of at the end and write down its x or y offset near it. When in need to rezero I use that one dimple and a mounted V60 bit or laser firing at low power.
Itās a bit of a hasle, but it works and works every time as long as you can reposition your now glowing stock square to the machine using fences or something with that function.
There are other ways to be able to regain lost zeroes that you cannot rezero with a block, but this -to my knowledge- is the most dimple one.
Hey Eddie, no apologies needed, and thank you for your kind words, what you said about poetry is very true, one tends to read and project the self.
Iāve read novels Iāve enjoyed more when I was in a better mood than when not.
Yes! same here, I use PixelCNC for 3d Carving, F-Engrave for inlay carving, and Estlcam for regular CAD drawing carving, and out of the three, just the latter allows me to place an origin outside the carving area, and as you say, sometimes pieces are not square, so not being able to rely on a job to complete w/out resetting the coordinates, makes it necessary to have a piece of the wood as my 0,0 coordinate with the probe.
āGajes del oficioā (kinks of the job) as we say in Mexico.
Yes, if you go to Config and then activate the āView Modifiedā slide button, itāll conveniently show up there, and even more conveniently will allow you to reset the settings, itās just a bit of a hassle having to do this so frequently (almost every time I open up gSender)
Just to note, now that 1.5.1 addressed this issue Iāll close the topic - but anyone seeing this thread whether in 1.5.0 or later definitely follow what @NCNC wrote above to reset the setting for the āNormalā jogging preset
