Phil,
How does this driver treat Alias tags? They seem to be missing from the configuration when I import my L5X. (how do other drivers treat them - for that matter?)
My host driver discards them on import. I theoretically could support them there, but haven't taken the time to implement that.
My client driver treats them like independent tags because the processor browse protocol has some ambiguity about them. (Same as IA's driver.)
You should never target alias tags from Ignition, as they are totally unoptimizable. Like, will crush your connection performance. Which makes me want to not implement this in the Host Device type.
2 Likes
Automation Professionals is pleased to release a new BETA of this driver, with some bug fixes from the last beta, plus a bug fix for Logix "DT" aka "UTIME" data type support.
For Ignition v8.1.7+: v2.1.20.251471538
3 Likes
More bugfixes. Still BETA.
For Ignition v8.1.7+: v2.1.20.251532105
3 Likes
More bugfixes last week. Still BETA, but feeling pretty good about this one:
For Ignition v8.1.8+: v2.1.20.252681756
(Will be renumbered to v2.2.0 upon release--I've been cherry-picking back and forth with the v8.3 branch and these are very close to functionally identical.)
1 Like
@pturmel in another topic about sticking momentary buttons you mentioned your improved Logix Driver. Is this that driver? Will it help make momentary buttons more reliable?
I agree, that they should be avoided but I am not the one making the call to keep the buttons in place. We use our momentary buttons to jog a conveyor/s if needed.
Appreciate a response, thank you.
This driver module includes a high-reliability momentary button for Vision, which only works with the module's Class1 I/O buffers (Scanner or Adapter modes). It does not work with the Generic EtherNet/IP Client driver type, nor with any other driver.