rlp122

MrPLC Member
 View profile  See their activity

  • Content count

    79

  • Joined

  • Last visited

Posts posted by rlp122

  4. Posted · Edited by rlp122

    Do-more BRX firmware changes only a few times per year.  If you are concerned about it, go over to https://forum.hosteng.com and talk to the guys that make it.  They love talking to their customers.

    For the record, here are the dates of the last few firmware changes.  Most coincide with new hardware releases.  https://hosteng.com/HW-Products/DM1/BX-DM1.htm#Firmware

    8/14/2019

    6/19/2019

    3/27/2019

    8/30/2018

    6/13/2018

    5/31/2018

  10. Posted

    Write it out as a series of If/Then statements. Then try translating those to ladder logic. Maybe this will get you started. If Y3 is off and X3 is on and X1 is off then turn on Y3. If Y3 is on then turn off Y2.

  11. Posted · Edited by rlp122

    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.
    1 person likes this

  22. Posted

    It can be done over MODBUS TCP. Is it easy? No. First it depends on what version of Think and Do you are at. Second it takes some programming on either the 260 or the TnD side. Possibly both. I personally have never tried to do this, although I know it is possible. My biggest suggestion with this is buy a support agreement with Think and Do and talk to their tech. He has done this many times and can help you out with the right steps to take.

  24. Posted · Edited by rlp122

    You need to add some sort of CEMF protection to the Solenoid. Either a diode (1n4004 or similar), varistor, etc to reduce the "kickback" when the solenoid de-energizes. See the Click Hardware manual Page 3-30. I know it says for Relay Outputs, but it is required for any output.
    1 person likes this