Why Can't I Find My Driver When Binding Data?
It's important to remember that ARDI needs more than just a driver when connecting to external data. You need data sources too.
It's the data sources that define the specific places your driver needs to talk to - such as the particular Prometheus server, Modbus/TCP device or SQL database.
One way to think about it is that the ARDI driver is responsible for providing your telephone network, but it's up to the individual data sources to actually dial their friends and talk. This is because with ARDI systems, you're often organising a party - there might be many people on the line all at once.
Related Articles
Resolving Issues with Incorrect Sensor Data
Incorrect sensor data is quite easy to ignore in traditional systems (such as your 2D HMI), but it can be very glaring when you have a 3D visualisation. If you've got valid but incorrect data coming from a sensor (ie. the sensor is still active, but ...OPC-UA
ARDI can connect to OPC-UA clients using the new OPCUA driver. Note that OPC-UA is only a live driver. Historical data access is not currently available. Performance Note The driver does take a while to establish the initial connection - it takes ...Restarting Driver Services
If you have suspicious that a driver isn't working, hasn't been updated correctly, or you're seeing errors in the diagnostic reports or when running the driver interactively, you might want to start, stop or restart your driver services. There are a ...Aspentech IP21
ARDI can connect to Aspentech IP21 using the new IP21 driver. This includes both a Live data driver, which extracts the most recent information out of the historian, and the Historical driver to be able to access points from history. Performance of ...Running Drivers Interactively
This documentation can also be found as part of the standard ARDI documentation - it is reproduced here. If you're having trouble with a driver or a connection, you can try manually launching it, otherwise known as running your driver interactively. ...