Version Differences for P
|
(→SDK)
|
(→Downloads)
|
| Line 17: | |||
| - | ==Downloads== | ||
| - | {{EULA_Block}} | ||
| - | === OpticonRL Utility === | ||
| - | *[[OpticonRL]] is an application developed separately for multiple platforms that converts barcode data coming over a serial port into key presses. Since the majority of our products support serial communication in one way or another this can be especially useful. In effect, the barcode data is wedged into whatever application is at the forefront and has text focus, as if it were typed | ||
| - | === NetO32 Utility === | ||
| - | *[[NetO32]] (Net-Oh) is the name for Opticon's protocol used for transferring data from our terminal devices to a host PC. Data is transferred as an entire file. Note that NetO must be supported on the application running on the terminal device and a host application must also be running such as NetO32. The necessary libraries to implement NetO protocol on the terminal devices are provided by Opticon in our C-Library Kit. A host SDK is also available to implement NetO within your own application. | ||
| - | === OSE Comm Utility === | ||
| - | *[[OseComm]] (Oh-ess-e-com) is the name for Opticon's revisioned file-transfer protocol developed to transfer data from our terminal devices to a host computer. This is a utility that is similar in function to the NetO32 utility, but is newer and has a bit more functionality than NetO32 does. Like Neto, the d in the data in the reader is transferred as an entire file to the host system. The necessary libraries to implement the OseComm protocol on terminal devices are provided by Opticon in our C Library Kit. A host SDK is also available to implement OseComm within your own computer application for the native Win32 platform as well as .NET. | ||
| '''NOTES:''' | '''NOTES:''' | ||