User's Guide - LINX Data Terminals

More documents

Recommendations

Info

• Synchronous DRAM TestsSDRAM Test #1;This test will destructively test the SDRAM. The following data patternswill be used to verify memory integrity:DATA: $55555555, $AAAAAAAA, $00000000SDRAM Test #2;This test will destructively test the SDRAM by initializing all uniqueaddresses with data to verify the integrity of the SDRAM address lines.• Battery-Backed SRAM TestsSRAM Test #1;This test will destructively test the SRAM. The following data patterns willbe used to verify memory integrity:DATA: $55555555, $AAAAAAAA, $00000000SRAM Test #2;This test will destructively test the SRAM by initializing all uniqueaddresses with data to verify the integrity of the SRAM address lines.• COM1 External Loopback TestThis test will detect if a “Loopback” plug has been installed. If it is found,then data 00-FF will be transmitted and then received to verify that UARTport #1 is operational.• COM2 External Loopback TestThis test will detect if a “Loopback” plug has been installed. If it is found,then data 00-FF will be transmitted and then received to verify that UARTport #2 is operational.• Ethernet Internal Loopback TestThis routine will verify that the Ethernet circuitry is operational. This willtest the Coldfire Ethernet MAC and the Level-One (Intel) 10/100mbPhysical Interface by executing an internal TX/RX loopback via the IntelLXT972A Physical Interface.• Keyboard LED testThis test will cycle through all of the keyboard LEDs. First turning all“ON”, then all “OFF”. Note: This test must be visually validated by theuser.• Keyboard ID TestThis test will prompt the user to “Press the Zero key”. This is used todetermine the type of keyboard installed on the terminal. This test will takeabout 3 seconds. Press and hold the “Zero” key repeatedly until a messageappears that indicates success or failure. If the detection process fails, thenthe terminal must be rebooted to try again. The terminal will NOT continueto boot until the keyboard type has been determined!NOTE: If any of these tests should fail, an error message will bedisplayed on the LCD to indicate failure mode.10 • Preface LINX 7-5 User's Guide
Once the 'BOOT' diagnostics have passed, the Linx7-5 will bootnormally.The Linx 7-5 Terminal Normal boot sequencePLEASE NOTE:The Ethernet cable MUSTbe plugged in beforepowering up the unit inorder for the TCP/IP stackto initialize properly.If the boot diagnostics have already been executed, the boot code willverify the integrity of the flash code blocks. A series of status messageswill be displayed for a brief time during these checks. The following isa brief description of these messages:1. A hardware version string will momentarily be shown.2. Main flash block validation will be indicated by the message:"Firmware Validation in Progress.." for 2 seconds.3. At this time, if a flash update is desired, press the "CLEAR" keyand the COM1 Upload utility will be started.(See Appendix B)- If the validation fails, the display will cycle the following error messages: (cycletime approx. 2 seconds)If these messages appear,the flash blocks MUST beloaded via the COM1 Portand the code will stay inthis message loop until adownload is started. (SeeAppendix B for moreinformation on flashupdating).WARNING: MAIN Code Checksum INVALID!Calculated checksum = xxxxxxxxand.NOTICE: MAIN CODE UPLOAD REQUIRED.Upload from COM1 Port: 9600 BaudAfter the boot code has determined that the flash blocks are valid. The normal bootsequence for the Linx7-5 consists of a series of status and information messages toinform the operator of the current configuration and/or status of the Linx7-5terminal. Following is the messages that are displayed:First Screen: Displayed for 1 secondLDT Linx7-5 - V1.0March 21 2004 10:31:21Line1: Terminal firmware VersionLine2: Firmware build date & timeSecond Screen: Displayed for 1 secondsssssssssssssssLINX 7-5 User's Guide Preface • 11
Page 2: March 12, 2007Copyright LINX Data T
Page 8 and 9: Using the Linx 7-5 Data Collection
Page 10 and 11: perform local validation of input;
Page 12 and 13: Linx7-5 Block Diagram8 • Preface
Page 16 and 17: Line1: ssssssss=Terminal Serial Num
Page 18 and 19: Linx7-5 Terminal Status DisplaysThe
Page 20 and 21: 'zzzz'This field displays (in Kbyte
Page 22 and 23: 3-Diagnostics< for next menuPress '
Page 24 and 25: NOTE: “User ‘C’ APP w/EVO”s
Page 26 and 27: Although this test menu can be oper
Page 28 and 29: Time DisplayLED Lamp TestThis test
Page 30 and 31: Linx7-5 Web ServerWeb Server Overvi
Page 32 and 33: 28 • Linx7-5 Web Server LINX 7-5
Page 34 and 35: Secured “Terminal Setup” PageIf
Page 36 and 37: Secured “Network Setup” PageIf
Page 38 and 39: DEFAULTVALID MIN/MAX RANGE"Code 39
Page 40 and 41: Secured “Password Control” Main
Page 42 and 43: Installing PeripheralsBack Plate co
Page 44 and 45: Wand/Laser (special DB9-M) port pro
Page 46 and 47: Appendix BFilename MUST be the name
Page 48 and 49: Appendix CUsing FTP.EXE - Windows C
Page 50 and 51: TABLE 1Most useful Windows FTP clie
Page 52 and 53: Appendix EBefore setup,please read:
Page 54 and 55: APPENDIX FCabling requirements to u
Page 56 and 57: d. If "Green" the FIU diagnostic sh
Page 58 and 59: ANSI/VT52 ModeWraparound ModeKeyPad
Page 60 and 61: # Function Key # to provide (IP) "I

User's Guide - LINX Data Terminals

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?