Home arrow Dealer FAQs arrow Printer Setup Trouble-shooting
Printer Setup \ Trouble-shooting PDF Print E-mail
Printers can be run from both the Fedelta Server or Fedelta POS for convenience. JavaPOS and OPOS printers are supported. There are 2 setup requirements for each Printer:
  1.  
    1. Check the config\jpos.xml for the type of printer ensuring that the port\address is setup correctly.

      <JposEntry logicalName="Network U220 19">
              <creation factoryClass="jp.co.epson.uposcommon.util.EpsonJposServiceInstanceFactory" serviceClass="jp.co.epson.upos.pntr.U220BService"/>
              <vendor name="SEIKO EPSON" url="http://www.epson.co.jp"/>
              <jpos category="POSPrinter" version="1.9.4"/>
              <product description="EPSON TM-U220B Printer Device Service" name="EPSON Services for JavaPOS(TM) Standard" url="http://www.epson.co.jp"/>

              <!--Other non JavaPOS required property (mostly vendor properties and bus specific properties i.e. RS232 )-->
              <!-- Lines HAVE BEEN REMOVED here for concise documentation purposes -->

              <prop name="UsedNVRAM" type="String" value="0"/>
              <prop name="UdpRetryIntervalTime" type="String" value="50"/>
              <prop name="ReceiveTimeout" type="String" value="1000"/>
              <prop name="SlpReverseEject" type="String" value="0"/>
              <prop name="PortName" type="String" value="192.168.0.227"/>
              <prop name="OfflineRetryIntervalTime" type="String" value="100"/>
              <!-- Lines HAVE BEEN REMOVED here for concise documentation purposes -->
      </JposEntry>

      For OPOS Printers please ensure that you modify the following entry within the JavaPOS jpos.xml (unecessary lines have been removed):

      <JposEntry logicalName="Bridge">
          <creation factoryClass="au.com.afjsoftware.oposbridge.AFJOposJposServiceInstanceFactory" serviceClass="au.com.afjsoftware.oposbridge.impl.AFJOposJPosPrinter"/>
          <prop name="oposName" type="String" value="TM-T88III"/>
      </JposEntry>

      In this example you would need to put "Bridge" (without quotes) into the preference editor as JavaPOS name. You can copy and rename these entries to create multiple OPOS Printers if required (make sure the logical name is unique for each one). The oposName ("TM-T88III") should be changed to the device name setup in the OPOS utility.
      Please ensure that you have successfully tested the device with the OPOS utility as this is not supported.
  2. Launch the Preference Editor from [Installation Directory]\bin\config.bat. Ensure that the Printer type is JavaPOS or default. Ensure that the Printer Javapos Name is specified exactly as typed in the logicalName within the jpos.xml file corresponding to the Printer Required.

The following are our recommended printers and corresponding setups. The table lists dispwich bank followed by switch for each one required to be ON. All others should be OFF.

 Model Serial Ethernet 
 TMT88III  1-7 (9600 Baud)
 2-2 (Autocutter) 2-8 (Parallel)
 U220    2-2 (Autocutter) 2-8 (Parallel)
     

 

Trouble-shooting:

If the device is not capturing correct please ensure that you have the correct dipswitches setup on the printer that correlate with the jpos.xml settings.

To test the printer independanty of Fedelta please do the following e.g. for com1 (you change change the com port as appropriate for the printer):

  1. Go to Command Prompt (Start->Run... cmd)
  2. type: 'mode com1 9600,n,8,1' (without quotes) and hit Enter
  3. type 'echo this is a printer test > com1' (without quotes) and hit Enter
  4. Feed the printer and check that the output = this is a printer test. If it is anything else then you need to alter the dip switchs to match the com settings from step 2.

Error Message
Resolution
 The service is claimed by another process.  

Generally this means that another Fedelta device (POS or server)
on the network has captured the device or that the COM port for the
device is in use by something else (e.g. Windows printer driver).

The problem can also be caused by incorrect printer settings
(e.g. baud rate). Consult the above trouble shooting steps for this.

 
< Prev   Next >