Hi all,
Since folks have occasionally brought up using firmware commands for Hamilton robots, Eric and I thought it would be good to share some guidance relating to them.
Using firmware commands to control a Hamilton robot is not endorsed by Hamilton and may result in damage to your system as well as voiding your warranty. As with all advice on this forum, make sure you know what you are doing before you try something you read here.
Hi Stefan,
How does this guidance implicate the use of PLR?
PLR is not endorsed by Hamilton
Thanks for the fast reply Stefan! Given that use of firmware commands (such as through PLR) may result in damage to my system, does this definitively mean that a warranty would be voided if damage was to occur? And with that said, what does it mean for service contracts? Thanks
See below for the general policy for use of firmware commands on Hamilton platforms. This policy applies largely for systems sold and supported by Hamilton US so for other territories, it’s best to confirm with your direct support contacts.
The use of low level firmware commands bypasses the collision avoidance scheme built into VENUS software. Repair of resulting damage from this type collision is outside the warranty and service agreement. Be advised the agreement and warranty will remain intact, only damage from the incident is not covered.
Fair enough. But aren’t collisions caused by any user based programming or mistakes (e.g. loading errors) not covered anyway, even if it were to happen under Venus?
How about using quasi firmware commands such as channel moves?
Yes, there are other ways to damage the system aside from using firmware commands that aren’t necessarily covered by the agreement either.
In general, there are fewer safeguards and built-in error handlings when using firmware commands so the risk increases.
My recommendation would be to use at your own risk and consult with your Hamilton support contacts who best know your system setup and needs.