Software release 08/01/2019 (withdrawn)

[JuKu]

Build date 8/1/2019

Download link: withdrawn, corrected version at viewtopic.php?f=10&t=6255

New Features, Significant Changes

* Slack correction distance is now editable, correction always applies
* Show pixels is moved to be always visible
* Goto Park now happens with A=0
* Added a label for CAD file load and placed status reset
(The operations are still slow, thanks to MicroSoft
and the UI component used)
* For developers: Now using Visual Studio 2019 and C# 8.0:
this should improve stability.

Bug Fixes

* Show pixels doesn't reset when changing tabs
* Pump and vacuum statuses are now "off" when recovering a board reset
* Homing is now more accurate in certain conditions
* On tapes grid, several rows can now be selected, Z reset
only affect the selected rows
* It was possible to jog with numpad keys even when nozzle was down
* Clicking the picture now produced the expected amount of movement
with showpixels on or off (triangular error is still there)
* Manually moving Z with F11/F12 no more triggers nozzle down error
* Fixed issue on identifiers on panelisation with more than 10 repeats
* Camera zoom factors are now forced to be >1.0
* Motor power checkbox now more accurately reflects the true status
of the system
* Tickmarks now show properly with show pixels on

Notes

This is mostly a bug fix release. As always, feedback and bug reports are appreciated. If possible, take a copy of the log window content for a bug report (click inside the log window, ctrl+A to select all, copy and paste to a text document).

[Krzys]

Welcome.
Unfortunately, the new version does not start with my Windows 10 64bit.

[JuKu]

My apologies! The development machine had an updated DLL. Of course, your machine doesn't (yet). I fixed the installer, and the link in the first post is updated. Thank you for letting me know.

[Krzys]

Welcome.
The revised program now starts.
I will have a free moment, I will test the new features of the program.
Thank you JuKu.
Best wishes.
Krzysztof

[Krzys]

There is a problem.
Setup Camera does not switch images from cameras.
I have a frozen picture.
When I go on tapes, the camera image does not change.

Krzysztof

[JuKu]

Odd, I didn’t touch the camera starting code, and it works on two machines I have here. Let’s take this to email (I’ll send the result here). To start, please send me the log of startup and changing tabs; thank you!

[pete0]

This is mostly a bug fix release. As always, feedback and bug reports are appreciated.

Unfortunatelly Issue #58: Software release, 07/09/2018: Manually assisted placement problem is still not fixed.

This bug, worst case can harm the maschine since nozzle movement while nozzle is down is possible! Best case nozzle can hit already placed parts.

I am the author who contributed the function for manually assisted placement. With pull request #60 I have created 6 months ago a fix for the problem which is by the way a trivial merge. The pull request includes a description of how the error can be reproduced and the root cause.

Since the bug is not fixed in the actual release I would ask you to at least include a warning in your release note.

pete0

[JuKu]

There is a problem.
Setup Camera does not switch images from cameras.
I have a frozen picture.
When I go on tapes, the camera image does not change.

Krzysztof

FIxed in 08/14/2019 release (out in a few moments)

[JuKu]

This is mostly a bug fix release. As always, feedback and bug reports are appreciated.

Unfortunatelly Issue #58: Software release, 07/09/2018: Manually assisted placement problem is still not fixed.

This bug, worst case can harm the maschine since nozzle movement while nozzle is down is possible! Best case nozzle can hit already placed parts.

I am the author who contributed the function for manually assisted placement. With pull request #60 I have created 6 months ago a fix for the problem which is by the way a trivial merge. The pull request includes a description of how the error can be reproduced and the root cause.

Since the bug is not fixed in the actual release I would ask you to at least include a warning in your release note.

pete0

It was included, but not in the release notes , my bad! The pull request didn't cover all cases, release on 08/14/2019 does.