Version Differences for OPN2005

(→OSE Comm Utility)
(→OSE Comm Utility)
Line 64:
  === OSE Comm Utility ===    === 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.    *[[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:'''  
- **''Use only [[NetO32]] or [[OSEComm]] utility on the host computer NOT both.''   + * ''Use only [[NetO32]] or [[OSEComm]] utility on the host computer NOT both.''  
- **''If OseComm is used, then it must be supported on the application running on the terminal device and an application must also be running on the host computer using OseComm32.''   + * ''If OseComm is used, then it must be supported on the application running on the terminal device and an application must also be running on the host computer using OseComm32.''  
  ===Documents===    ===Documents===