Beta Testing Context Thank you for helping test the native Ignition Mitsubishi drivers. This is a tight window (April) as we are aiming for production release in 8.1.28 (May 30th). Please provide feedback here as soon as you have it. Non-bug feature requests will be most actionable in the first few …

I don't have anything to test with, but I have to admit concern over some of the above. First, and most concerning, is the use of "tag path" terminology in a driver. Everywhere else in Ignition, a "tag path" refers to the hierarchy in a tag provider, not in a driver. Drivers have OPC "item paths"…

[image] pturmel: Drivers have OPC "item paths". 100% agreement here. OPC UA drivers expose opc items. [image] pturmel: Second, you have to "Import a CSV" and/or have to configure specific addresses and ranges, yielding new names, to have browsable items. Just like the Modbus driver. Utte…

[image] bmusson: I'll be honest, I have no idea what the use case is for address mapping. What's the advantage of abstracting away the PLC address with an arbitrary item name? It's just double data entry with no real gain. I tend to agree with this, and our Modbus driver address mapping is es…

[image] Kevin.Herron: CSV import/export is primarily in response to a demand for "CSV support" from users. Does this mean it's optional, like the Modbus mappings are optional? The text above is unclear. [image] Kevin.Herron: I don't like the "Item Path" terminology I'd be perfectly h…

[image] pturmel: Does this mean it's optional, like the Modbus mappings are optional? Yes, totally optional. Just create tags that have a NodeId (OPC Item Path) with the syntax described in the docs. [image] pturmel: I'd be perfectly happy to see "Node Id" replace "Item Path" everywhere.…

[image] Kevin.Herron: Yes, totally optional. Ok. But still annoying to not be able to browse the well-defined linear address space.

I might actually agree with you on this driver, but only because I don’t have enough experience to know how these memory layouts are used. If people stick to the “native” DataType of each memory area and don’t combine them into multi-“word” types, sure, it would be useful. But GX works seems to have…

[image] Kevin.Herron: I’ve seen uses multi-register types, at who knows what alignment within the memory Did you notice my driver offers the multi-word types in the node with the "plain" register? So, you literally just drill in one layer further to get the other types (or bits of registers). …

Yes, fiends indeed. Back to the whole import / tag list thing, another pain point is that in all of these implementations we end up fielding support calls from users who think they are assembling some kind of tag polling list, not just creating a browse model. This confusion seems especially common…

[image] Kevin.Herron: This confusion seems especially common with DNP3 users. I've not had to work with DNP3 devices yet, or their users. I suppose I can wait.

Inductive Automation Forum

Mitsubishi Driver Beta Test Open Now! Test through April

Ignition Early Access