williamlove
Member
My company imposes programming standards and insists on using AOIs for AI, AO, DI, DO points. I like AOIs and use them as subroutines when I have code I'd repeat otherwise. Like twenty burners....they really deliver for stuff like that. But I can't stand using them for I/O handling. I've heard some companies actually try to block/ban their use and I can easily imagine why. They make it hard to find the actual I/O and maintenance people hate them. Maintenance derives none of the ostensible value they provide to ... to who exactly? I don't see their value for I/O. I use aliasing and SCPs, but I put those a rung with the aliased I/O clearly visible so we can FIND it. Yet people I respect use super fancy AOIs, sometimes with mind blowing levels of nesting and indirection. I think they're just showing off or enjoying the learning process ... at the expense of the end users and others. Thoughts? I'd like to present an argument against their routine use for standard I/O. One of the suggestions I've heard goes like this: Whenever anything is off widespread value without customization required, Rockwell will make an instruction for it. I've also heard Rockwell is abandoning the AOI approach to PlantPax and that seems favorable to my thesis.