|
| Features |
| Pricing |
| Download |
| Case Studies |
| Order |
| Upgrade |
|
Add-on Products |
Using the Socket Communications Scan Cards
with Pendragon Forms
Socket Communications scanner modules, including the CF In-Hand Scan Card and the SDIO In-Hand Scan Card. Once installed, these modules enable the user to scan bar codes with the module’s CCD scanner.
Pendragon Forms automatically recognizes these scanners and captures bar codes into the active text field (if any). These canners are also compatible with the SCAN event in the Pendragon Forms scripting language.
For compatibility, you will need Pendragon Forms 5.0 or 4.0 Service Pack 4 and you may need to install the appropriate software from Socket Communications. For compatibility with the Pendragon Forms scripting features, you will also need to disable the generic scanning feature via the SocketScan application.
On a Palm OS handheld, you can designate a hardware button to be used to trigger the scanning function using the new SOCKETSCAN scripting statement.
The SOCKETSCAN scripting statement can be used as follows.
Note: SOCKETSCAN TRIGGER NOW is the only scripting statement than can be used with Pocket PCs.
|
socketscan trigger now The trigger now option triggers a bar code scan immediately. This can be used to trigger a scan using an on-screen button field.
This option resets the scanner to its default settings.
socketscan set_trigger keycode Sets the hardware button keycode that will trigger the scanner. It is suggested that you use one of the following codes: 516 for DateBook/Calendar button 517 for AddressBook/Contacts button 518 for ToDo/Tasks button 519 for Memo/Notepad button This statement would typically be used in the following way:
open:
socketscan symbology value This statement is used to enable or disable the scanning of certain bar code symbologies, e.g., ISBN, CODE39, UPCA, etc. The value parameter is 1 to enable the specified symbology, 0 to disable it. The symbology parameter should be one of the following: UPCA UPCE EAN8 EAN13 BOOKLAND_EAN USS128 UCC_EAN128 CODE39 TRIOPTIC39 CODE93 I2OF5 D25 CODABAR MSI_PLESSEY CODE11 WEBC socketscan lengthparameter length This statement controls min and max length for various barcode types
The lengthparameter must be one of the following
CODE39_MIN CODE39_MAX CODE93_MIN CODE93_MAX I2OF5_MIN I2OF5_MAX D25_MIN D25_MAX CODABAR_MIN CODABAR_MAX MSI_MIN MSI_MAX CODE11_MIN CODE11_MAX WEBC_MIN WEBC_MAX
For example, to set a minimum length for bar codes with the CODE39 symbology, use the following statement:
socketscan setting value Use this variation of the SOCKETSCAN statement to set other parameters such as transmission and verification of check digits. The setting and value parameters can be set according to the following table. Please see the SocketScan SDK for Palm if you need more detailed information.
|
|
Setting |
Value |
|
DECODE_UPCEAN_SUMPLEMENTALS |
0 = UPC/EAN without Supplemental Characters 1 = UPC/EAN with Supplemental Characters 2 = Autodiscriminate |
|
UPCEAN_SUPLEMENTAL_REDUNDANCY |
This value ranges from 2 to 20. 5 or above is recommended when decoding a mix of UPC/EAN symbols with and without supplementals. |
|
TRANSMIT_UPCA_CHECKDIGIT |
0 = Disable 1 = Enable |
|
UPCA_PREAMBLE |
0 = No preamble transmitted 1 = Transmit system character only 2 = Transmit system character and country code ("0" for USA) |
|
CONVERTEAN_8TO13 |
0 = Type is EAN-8 1 = Type is EAN-13 |
|
UPCEAN_SECURITYLEVEL |
See the SocketScan SDK |
|
I2OF5_CHECKDIGITVERIFY |
0 = Disable 1 = USS Check Digit 2 = OPCC Check Digit |
|
MSIPL_CHECKDIGIT |
0 = Two Check Digits 1 = One Check Digit |
|
MSIPL_CHECKDIGIT_ALGORITHM |
0 = MOD 10/MOD 11 1 = MOD 10/MOD 10 |
|
CODE_ID_CHAR |
A code ID character identifies the code type of a scanned bar code. This may be useful when the scanner is decoding more than one code type. In addition to any single character prefix already selected, the code ID character is inserted between the prefix and the decoded symbol.
0 = No character 1 = Symbol ID code, one of the following is inserted:
A = UPC-A, UPC-E, UPC-E1, EAN-8, EAN-13 B = Code 39, Code 32 C = Codabar D = Code 128, ISBT 128 E = Code 93 F = Interleaved 2 of 5 G = Discrete 2 of 5, or Discrete 2 of 5 IATA H = Code 11 J = MSI Plessey K = UCC/EAN-128 L = Bookland EAN M = Trioptic Code 39 N = Coupon Code |
For example, the following statement sets the UPCA preamble to system character and country code:
socketscan upca_preamble 2
Socket In-Hand Scan Card Notes
1. Be sure to obtain the latest SocketScan software from Socket Communications. As of this writing, the current version is 1.02. Earlier versions will not work with Pendragon Forms.
2. After installing the SocketScan software, you must disable the generic scanning feature (on the General tab). The generic scanning feature sends bar code scans to applications as if they were typed on a keyboard. When this feature is active, Pendragon Forms cannot distinguish bar code scans from normal typed entry, and SCAN events will not trigger.
3. If you want to use a hardware button to trigger scans with the In-Hand Scan Card, use the SOCKETSCAN SET_TRIGGER statement in your form’s OPEN event.
4. If you need audio feedback for a scan, add a BEEP statement to your SCAN event.
5. The Pendragon Forms SCANTYPE scripting function will not work with the In-Hand Scan Card. It will always be “NONE”. This is because the SocketScan SDK does not report the symbology of the scanned bar code.
For more information about using Pendragon Forms to collect bar code scanner data, please see Chapter 15: Using Bar Codes in the Pendragon Forms Reference Guide (6.1MB, PDF download. Right- click on this link and choose Save Target As...).
© 2004-2005 Pendragon Software Corporation. All rights reserved. Copyright and trademark information.