The Rage (because) of the (Gateway) Machine
I have a soap box to climb on and something to say if it is deemed inappropriate I will submit myself for disciplinary action... but someone needs to say it and it might as well be me!
This letter was written because of several problems with Modbus to MSTP gateways factory installed and problematic since the day installed.
It was written to the Manufacture of the HVAC unit and the producer of the Gateway in a conference email.
Names have been removed to protect the guilty parties and from keeping the lawsuits down to a minimum LOL
Now on to my never to be humbled opinion.
I was doing this very same thing (fighting protocol gateways for accurate information, and trying to get manufactures to do what they said they would do.) way back in the year of 2000 working in native BACnet. I did expect problems in the infancy of the open area of BACnet, but now after all these years, why has the industry not improved after all this time of so called open BACnet?
Most control companies are small in nature and most work as a sub of a subcontractor in the field and simply do not have the resources or time to fight to get what they paid for. They just roll over and get it done by any other means they can. In truth if it was not for the customer based field I work for now I would have removed the gateway and did it myself just to get on to more fertile ground.
All of this is because (in my never to be humbled opinion) someone somehow does not do the homework needed to make these devices work in the way they are specified. Meanwhile the illusion of conformance and compliance is proliferated and no one really knows how bad the result is of a alpha or beta product being sold as a final gamma. Now that is not a slap at any one of your company’s products or personal,( I am assured you are the best in the field you work in.) It is however a slap on just how good your two companies work together to make it right. Before and after it gets to the field!
Gentlemen please forgive my candor in this matter but after dealing for 4 months with this issue and the last 20 years in this field, I simply do not have confidence in the way my issues have been dealt with.
After doing my research and knowing what has been told to me on how to communicate with these devices. I now find out I have been getting incorrect information.
This is why I started a dialog with XXXXX in the first place, and why I started doing my own research, and This is why my confidence level is at a 0.0%
I have found out during my research that I am not alone. There are so many other people in this industry that I have talked to that hold the same low confidence level as me about gateways in general and with So called open BACnet HVAC equipment in particular.
So many others I spoke to have either removed the gateways and did a modbus or native proprietary network connection or just installed their own Bacnet device to do a T-stat level of control all because of not getting the proper response to issues in the time required to make the job work under their construction time line. In essence the warranty to the customer eats up all of the profits of the project. Or in a working man’s parlance (The Juice is not worth the Squeeze)
This is why I feel the need to push this issue to the max. The way this is being played out for me and all of those building owners and control contractors… It almost seems to be designed or lack of design to be problematic. Or in other words…..Why is there always time to do the job right the second time?
Why cant we forget the days of monopoly and start playing on equal terms not forgetting who we are looking for... "the customer" after all he is paying for the product and deserves what he pays for!
The manufacture never gets called out in the middle of the night because of the command level control not getting its correct information. It is the Control contractor who is responsible for the network and devices of that network to operate properly.
So where is the incentive for the manufacture of the equipment to create a gateway and program it to operate properly when it is them that really wanted a full proprietary network running under their command and installed by their people running on their software getting paid to answer the service call? Just how open is a network when it is run by inferior devices designed to work just barely and only if you know the correct combination?
Feedback is desired