User Tools

Site Tools


faq:pole_display_setup_and_configuration

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
faq:pole_display_setup_and_configuration [2009/05/25 11:05 (15 years ago)] clifffaq:pole_display_setup_and_configuration [2009/09/11 15:09 (15 years ago)] (current) bob
Line 2: Line 2:
 ===== Logic Controls ===== ===== Logic Controls =====
  
-==== PD9000U ==== 
-=== Call Notes === 
  
-May 25, 2009 
  
-Contact: Nick 
  
-Technician: cm +==== PD9000U ====
- +
-Version: +
  
 Problem: 1) Logic Controls, LD9000U pole display to be setup over terminal services. Not displaying a full 20 characters properly. Problem: 1) Logic Controls, LD9000U pole display to be setup over terminal services. Not displaying a full 20 characters properly.
Line 17: Line 11:
 Solution: 1) The device would not work at 20 character width. First I made sure the device worked a full 20 characters by testing in the Hyper Terminal application. When talking to my technical manager, and the programmer I found that the reason for the wierd behavior is because it is common for this model of pole display to emulate another pole display type and it is not something that can be re-programmed. Due to this we needed to install the OPOS drivers. We installed the OPOS drivers from the DVD and then I installed the OPOS Common Control drivers. This was done on the machine local to the pole display. When I did the setup and test I used the COM Port settings instead of USB settings. I did this so that COM Port redirection could be used to allow the device to work. Once the local machine was tested I installed Logic Controls OPOS drivers and the OPOS Common Control drivers on the terminal server. Testing worked great. Solution: 1) The device would not work at 20 character width. First I made sure the device worked a full 20 characters by testing in the Hyper Terminal application. When talking to my technical manager, and the programmer I found that the reason for the wierd behavior is because it is common for this model of pole display to emulate another pole display type and it is not something that can be re-programmed. Due to this we needed to install the OPOS drivers. We installed the OPOS drivers from the DVD and then I installed the OPOS Common Control drivers. This was done on the machine local to the pole display. When I did the setup and test I used the COM Port settings instead of USB settings. I did this so that COM Port redirection could be used to allow the device to work. Once the local machine was tested I installed Logic Controls OPOS drivers and the OPOS Common Control drivers on the terminal server. Testing worked great.
  
-Next Agreed Contact Date: Resolved. +
  
 === Additional Links === === Additional Links ===
-Link for Installing OPOS drivers:+  * Link for Installing OPOS drivers: 
  
 http://wiki.wws5.com/doku.php?id=pos_devices_-_opos_drivers http://wiki.wws5.com/doku.php?id=pos_devices_-_opos_drivers
  
-Link directly to the Generic OPOS Drivers also known as the OPOS Common Control Objects:+  * Link directly to the Generic OPOS Drivers also known as the OPOS Common Control Objects: 
 + 
 + 
 +ftp://ftp.windward-ca.com/pub/special/OPOS_Common_Control_Objects.EXE 
 + 
 +  * Link to Logic Controls website to get the drivers for Customer Displays: 
 +http://www.logiccontrols.com/web/sd.htm
  
-ftp://ftp.windward-ca.com/pub/special/OposCCOs-1_8_001.EXE  
faq/pole_display_setup_and_configuration.txt · Last modified: 2009/09/11 15:09 (15 years ago) by bob