jcvel

KOYO Brick PLC Bugs

5 posts in this topic

Hi guys: I have come across some bugs with Brick PLC's. I understand things happening in the programming world, but can't accept the fact that after submitting the bugs to AutomationDirect for almost a year nothing has been made to resolve them.... Same firmware version still. I wonder if anyone knows what is the fate of the Bricks ? AutomationDirect service is good, but doesn't seem well supported by Koyo. Thanks JC

Share this post


Link to post
Share on other sites
Can you explain the bugs you are speaking of so we can be aware of them?

Share this post


Link to post
Share on other sites
Since thee original poster has not returned with specifics of the claims (bugs or 'non-response') then I think we can safely ignore this thread.

Share this post


Link to post
Share on other sites
Yes I've always gotten quick responses to support questions from them.

Share this post


Link to post
Share on other sites
1. Sometimes 'bugs' are working as intended. Working as intended is not always how the user wants something to work however. Corollary; sometimes 'bugs' are considered 'features' by users and taken advantage of in code. When this 'bug' gets fixed it really upsets some folks apple carts. There is a delicate balance of what to 'fix' and what to leave alone. 2. In most companies that I have dealt with, minor issues or complaints don't get addressed until: a. There are enough of them to warrant a separate build, something which is very time consuming due to testing, deployment, etc. b. Something major comes up that warrants all of the labor that goes into a new software build. While almost everyone thinks they want issues addressed as soon as they pop up, I have met not one single person who wants to update software/firmware nearly every day or even every week for that matter regardless of what is 'fixed'. 3. Occasionally an issue just isn't something that can be dealt with easily. In the past I have ran into issues that required years of rework to fix. Obviously this is the exception rather than the rule, but long story short; things take a lot longer in the software/firmware world than we would like for them to take at times. Tangent on the testing, deployment, etc. There is a lot more to this than most lay people realize. It can take weeks to months to drop a new piece of software or firmware depending on what was changed or modified. Having seen firsthand a PLC software/firmware test suite; the amount of code and hardware required for testing a PLC software/firmware release is staggering. The kicker is that every time an error is found, it has to be fixed and the test suite re-ran from the top again. Considering that I was told that one (there are many) of the modules in this test suite took 3 days to run; well... you get the picture. Edited by rlp122
1 person likes this

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now