Well, when I developed to work with these tightening controllers, I did not need to use every single MID from their docs, I would only implement by 20 or less (and there are a bunch of MIDs). So the library is divided by that, once we know in which category it is, we only iterate through MIDs from that category. Open protocol documentation divided MIDs by categories, such as: Job Messages, Tightening Messages, etc. How It Was Built?įor information and better use, it was basically done over the Chain Of Responsibility design pattern, that will iterate through MIDs and find the right one.įor sure it is, if you iterate through EVERY SINGLE MID, but some solution/workaround could be done.
Only Revision 1 packages were implemented in this library, but yes, I'm looking forward to implementing other revisions. Or "Well, I've received a package, translate this for me, please!", and then it will get all those chars inside that string and give you an object to work with. It's like building your MID by telling the library "Build it as a string, please!", and then it will do everything for you, so you can only send it up through your socket! In few words, the library does only two things, build packages or translate them. His article is a good introduction to what this article about the Open Protocol is all about, it might give you some knowledge to be aware of what we're talking about or solving in this article. You might remember or have found this article made by Syed Shanu. I've worked for some time developing to integrate these guys to our system and one of the most boring/annoying things was substringing every package and generating some "workable" objects, or at least translate those string packages to something that was easier to work with.īy then, I decided to build a library that would do all those boring things to me, then I should only work with some objects which we should call MIDs. Many reasons lead me to do that, such as helping the community because there is little about this on the internet.
In few words, you will exchange packages via Ethernet or Serial by sending what is specified in every MID (MIDs are packages). The most common Tightening Controllers you will hear from Atlas Copco company are PowerFocus4000 and PowerMacs.Īlthough, some other companies adhered to use the same protocol. Open Protocol, as the name says, is a protocol to communicate with Atlas Copco Tightening Controllers or whatever equipment implements that protocol.
0 kommentar(er)
