====Manually Launching Drivers====

If you're having trouble with a driver or a connection, you can try //manually launching// it, otherwise known as running your driver //interactively//.

This way you'll see any errors that occur, without them being hidden by the service layer on Windows or Linux.

On Windows, drivers are located in **C:\Program Files (x86)\Optrix\ARDI\drivers**, while on Linux they are in **/opt/ardi/drivers**.

//Live// drivers are located in the 'live' subfolder.
//Historical// drivers are located in the 'hist' subfolder.

Each driver is then located in its own subfolder.

Most drivers are python scripts, although some windows-specific drivers may be executable files. Either way, they are manually launched from the terminal/command-line using the same syntax.

//<driver_file>// //<port>// //<host>//

You can find the correct port number for each driver in 'Administration | Drivers'.

For example, if we wanted to manually start the live **text** driver that is set up for port **9102** on the **testing** database found on the local machine, we would...

   * Open a Console/Terminal
   * Go to the appropriate driver directory for our platform (ie. cd "C:\Program Files (x86)\Optrix\ARDI\drivers\live\text\" )
   * Enter the command below

<code>
text.py 9102 localhost/s/testing
</code>

If the command fails because Python isn't in your command-line, you could try the following...

<code>
c:\python27\python text.py 9102 localhost/s/testing
</code>

Note that if you only have one ARDI database on your system, the name for the database is //default//. So your command would be...

<code>
text.py 9102 localhost/s/default
</code>

===Notes on Windows Drivers===

Note that some Windows drivers may need to be run with administrative privileges. We suggest running them directly from an //administrative command prompt//.

===Closing Drivers===

Use CTRL+C to close your driver. There can be a small delay between pressing the keyboard combination and the driver actually stopping. If for any reason it is unresponsive, you can also stop the driver from the Task Manager on Windows, or using 'kill -9' on Linux.

===Substituting Drivers===

You can also use this technique to substitute //different// drivers that use the same connection data - or testing drivers such as the **zero**, **rnd** or **bad** drivers.