We wrote our own device driver module using the Ignition SDK and added a table to the Ignition internal database to store connectivity parameters and such.
But now I would like to access some of those parameters when running our Ignition project, mainly the IP Address, to make a separate connection to the device.
I’ll second @jpark recommendation. Since you already have a module providing driver functionality, adding a few scripting functions to retrieve values from the internal database makes sense. You’ll want to be cognizant of the call and leverage RPC’s (remote procedure calls) for client/designer scope calls.
A contractor wrote our driver module for us, so I was looking for a way to get the values without having to get in the module code. But what you say makes sense. I’ll jump in there and see what I can do.