Page 1 of 1
Sofware release, 23/11/2015
Posted: Mon Nov 23, 2015 1:34 pm
by JuKu
Build date 23/11/2015:
New features:
• Added diagonal jogging with NumPad keys
• It is now possible to disable mouse wheel and num pad jogging
• Show part nominal position, show part measured position and show part on tape setup functions now show orientation of the part
Bug fixes:
• Setting a value using num keys no longer jog the machine
• Connection to TinyG is no longer cut on error; instead there is an error state. This allows to change TinyG settings, possibly correcting whatever caused the error.
Re: Sofware release, 23/11/2015
Posted: Mon Nov 23, 2015 4:20 pm
by mrandt
Thanks Juha - looks great.
Part orientation preview saves a lot of time (and prevents errors) when setting up a new job and / or tray
Have you also fixed Github issue #22 - reset tape does not reset next position error?
My wishlist for next release would certainly include #28 and #29 for component management and #34 for placement operations
Cheers
Malte
Re: Sofware release, 23/11/2015
Posted: Wed Nov 25, 2015 7:06 am
by RMM
Thank you for continuing to develop the software!
Re: Sofware release, 23/11/2015
Posted: Mon Nov 30, 2015 6:51 pm
by mucek
There is a bug regarding to adding components and "Next hole" calculating.
If you:
1) Move to first component's hole
2) Add component
3) Set component hole
is works fine.
BUT, if you:
1) Click Add component
2) Move to first component's hole
3) Set component's hole
then program (wrong) takes "Next" position from the last hole added (previous component) and when you set component's hole, "next" position isn't turned into component's hole, but stays the same.
Probably an easy bug to fix, but took me a while figuring out, why some components have wrong valves ...
Regards,
Gregor
Re: Sofware release, 23/11/2015
Posted: Mon Nov 30, 2015 7:10 pm
by mrandt
Hi Gregor,
this is related to issue #22 I suppose...
I added your remarks:
https://github.com/jkuusama/LitePlacer-DEV/issues/22
Thanks
Malte
Re: Sofware release, 23/11/2015
Posted: Mon Nov 30, 2015 8:22 pm
by mucek
Could be, but not necessarry. If I understand ticket description right, it describes modifying current element. What I found is, that this also happens when you make a completely new element, but hole is not positioned when creating it.
Regards, g