Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
ardiadminguide:manually_launching_drivers [2018/10/25 11:49]
optrix 		ardiadminguide:manually_launching_drivers [2020/05/22 00:30] (current)
optrix
Line 1: Line 1:
 ====Manually Launching Drivers==== ====Manually Launching Drivers====
  
-If you're having trouble with a driver or a connection, you can try //manually launching// it.+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. This way you'll see any errors that occur, without them being hidden by the service layer on Windows or Linux.
Line 32: Line 32:
 <​code>​ <​code>​
 c:​\python27\python text.py 9102 localhost/​s/​testing 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>​ </​code>​
  
Line 41: Line 47:
  
 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. 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.