NavBar.jpg (18411 bytes)
About Us  Solutions  Products  Download  Support  Contact Us

IDCServerHeader.gif (30069 bytes)

The absolute solution for integrating data collected through Intermec 9154, 9161 and 9180 RF controllers or Direct reader serial connections with your host database application.

IDCServer.bmp (139254 bytes)

KEY FEATURES

Simply Interact With Your Portables via Two (2)  simple ActiveX .OCX Method Calls.
Allows For Fast Real Time Interactive Data Collection Integration.
Unlimited Number of Devices Supported for Network Controller Per license.
Supports Direct Serial (RS-232) Reader Connections for Batch System Integration.
Allows For Flat File Batch Upload Systems (No Host Programming Required).
Provides Standard for ActiveX Programming Languages.
Greatly Reduces Development Time.
Develop JANUS/Trakker Apps with tool of your choice (IRL, EzBuilder  or C++).
Thorough On-Line Windows Help System.
Visual Basic Program Examples Included.
No Charge Technical Phone Support.

Don't waste man weeks maybe months trying to develop a stable communications middleware program to collect your mission critical data from your Intermec devices.
ActiveX.gif (41056 bytes)

Enabled


Product Overview

The IDC Server is a Windows 95/NT based communication tool that handles the cumbersome communications to all 91XX model
Intermec controllers and Direct to Reader Serial connections. Using the provided ActiveX OCX objects and the IDC Server, you can easily exchange Real Time Interactive data between your JANUS/TRAKKER portables and custom host database application.  Because of the ActiveX interface you can develop in any of the popular visual development tools such as Visual Basic, Visual C++, Microsoft Access, FoxPro, Power Builder or any other that supports ActiveX Objects.  Now, with today’s Client/Server Technology, you can quickly develop a Real Time Interactive data collection Interface to any ODBC compliant Database System. If Real Time is not what your after, you can be collecting data immediately with it’s unattended batch upload feature.  As transactions are uploaded from the portable, they are logged to a flat ASCII file on the host PC.  The batch path and filename is user definable, putting you in total control.  If the file is renamed to be processed by a batch program, a new file is created when the next transaction is uploaded.  In either scenario, our tool will have you collecting transaction data from your Intermec Multi-Drop, Radio Frequency or batch data collection devices in less than 15 minutes. "We Guarantee it".


A Few Words From Our Product Team

In the past CremSol Tech pioneered host interfacing through DDE (Dynamic Data Exchange) technology which our competitors are still doing.  In the 16 Bit applications of the Windows 3.1 environment,  this was a viable solution.  Unfortunately,  this model of programming (DDE) in the 32 Bit environment is slow and being phased out because Microsoft and technology has moved on to a more structured model of development "ActiveX Class Objects".  As in the past,  CremSol is proud to be the pioneer of ActiveX Class Objects for programming Intermec Data Collection Systems.

                                                                       Michael A. Cannon
                                                                       Product Development


Check Out How It Works  

From within your selected development tool that supports ActiveX .OCX components,  simply reference our ActiveX Methods.  This will provide you the programmer, two simple methods of communication, "IDCTools.GetIDCTrans" and "IDCTools.PutIDCTrans" for sending and receiving Interactive transaction data to and from your Intermec devices through IDC Server.  Check out the following sample Visual Basic code:

Dim ReaderTrans As String                            

ReaderTrans = ""
Do Until ReaderTrans <> ""
        ReaderTrans = IDCTools.GetIDCTrans( )
        DoEvents
Loop

(Parse the transaction for the Reader Address & Transaction Code)
ReaderAddress = Left$(ReaderTrans,2)
TranCode = Mid$(ReaderTrans,3,3)

(
Parse the collected data based on the transaction code received and process it to your database here. This Example is very basic but any number of Transaction Types and database actions could be performed.)
Select Case TranCode
Case "PTW"    'Put Away - Add To On Hand Inventory
    BinNumber = Mid$(ReaderTrans,6,5)
    ItemNumber = Mid$(ReaderTrans,11,12)
    Qty = Mid$(ReaderTrans,23,5)
    Select OldQty=TheQty Where TheBin=BinNumber
    Update MyDatabase Set TheQty = OldQty+Cint(Qty)
    Where ItemNo = ItemNumber And TheBin=BinNumber
Case "PCK"    'Pick - Reduce From On Hand Inventory
    BinNumber = Mid$(ReaderTrans,6,5)
    ItemNumber = Mid$(ReaderTrans,11,12)
    Qty = Mid$(ReaderTrans,23,5)
    Select OldQty=TheQty Where TheBin=BinNumber
    Update MyDatabase Set TheQty = OldQty-Cint(Qty)
    Where Where ItemNo = ItemNumber And TheBin=BinNumber
End Select

( If necessary, you can easily send a response to the Intermec reader based on the action to your database.)
If MyDatabase.RecordsAffected > 0 Then
    ReaderTrans = ReaderAddress & "GOOD TRANSACTION"
    Do While Not IDCTools.PutIDCTrans(ReaderTrans)
             DoEvents
    Loop
Else
    ReaderTrans = ReaderAddress & "BAD TRANSACTION"
    Do While Not IDCTools.PutIDCTrans(ReaderTrans)
             DoEvents
    Loop
End If

The flexibility of this model is tremendous and your hands will never be tied as to what you can achieve with your data collection system.


For Additional Information

Contact
sales@cremsol.com or Call 1-888-CREMSOL


MINIMUM SYSTEM REQUIREMENTS

Computer: 486 IBM Compatible  (Pentium Recommended)
Memory: 16 MB RAM
Disk Space: 5 MB
Operating System: All Microsoft Windows Platforms


Download 15 Day Trial


Copyright © 1996 CremSol Technologies, L.L.C. All rights reserved.
Information in this document is subject to change without notice.
Other products and companies referred to herein are trademarks or
registered trademarks of their respective companies or mark holders.
Last Updated: January 20, 2007 08:59 AM.