Twinax Terminals Trouble Shooting Guide

Symptom Cause Action
Turn on base, gets no beep, or power LED Power cord loose, or no AC Replace AC power cord and verify source power ok.
Bad power supply in base LU Call CLI TS, or replace base LU.
Power OK, no video Video/power connectors loose, or damaged Inspect/Tighten video connectors, AC and SVGA to base LU.
Monitor out of adjustment Adjust brightness & contrast (turn both adjusters full clockwise).
Monitor pwr switch off (no LED) Turn monitor power switch on.
Monitor defective Call CLI TS, or replace monitor.
No video after monitor rplcd Call CLI TS, or replace base LU.
Cursor upper right No signal recvd on twinax line, or wrong address selected in off-line setup Detach Y-conn, restart, when cursor upper right, press Alt+CMD12, (will get inverse video) Reconnect twinax y-conn cbl. if screen changes, try a different address, if screen stays the same (inverse video), still no signal...change BALUN, patch cbl, or twinax cable.
Cursor upper right after troubleshoot address, twinax signal Move base LU only to different location, if pbm. follows base, replace base, if pbm. stays at location, go to troubleshoot cables, and addresses again.
Suspect defective base LU Call CLI TS, or replace base
Cursor upper left, characters appear when typed

Device type mismatch, or device varied off

Change the terminal emulation to match host configuration, or vary the device off/on.

LU address on device descrpt. doesn't match port/addr on rmt controller.

Change the terminal address to match the device description setting, and reset the remote controller.
Cursor upper left, no characters appear when typed Twinax signal strength weak, bad cable, or hub problem, termination pbm. on line Test all cables, hubs, controllers, verify only using 1 BALUN per terminal.
Cursor bounce from top right to top left Wrong address, or termination problem Correct address conflict, or twinax line termination problem.
Keyboard works, wrong characters appear on screen Base LU not detected the keyboard properly.

 

Power off LU, hold down spacebar, turn back on, until off-line setup screen appears, verify KBD type on bottom of screen, exit setup.
Keyboard type not matched on host configuration, or 5294 remote controller Verify/change keyboard type on HOST (S36 only) or reset remote 5294 controller into test mode 1st.
Bad keyboard Verify kbd is bad using OFF-LINE TEST WORKSTATION.
Garbage(strange chars or text) appears randomly on screen Twinax cable, or ends damaged

 

Test/replace bad cables, or ends, or baluns.
Twinax line termination pbm Troubleshoot twinax termination.
Dup address on active hub Change to correct address.
Screen gets distorted video when delete recorded "Fkey" Corrupt CMOS memory RESET CMOS (supported on current versions only) Press RESET + TAB + DELETE + F12 after power on, when "Press spacebar to enter offline setup msg appears".  Detailed instructions in PDF
Not allowed to record data to any "Fkeys" Macro buffer memory value reads R0000 Delete recorded FKEY(s), user manual section 4.3 record/play mode.
Keyboard no response, base beeps when type Some error message flashing in lower left corner of screen Press the reset key, or refer to manual appendix for error message description.
Macro recorder left on, shows RXXXX below status line Delete the "bad" Fkey, or turn off macro record function.
Keyboard detect problem Re-cycle base power, while holding down spacebar, exit setup.
Keyboard no response, or screen is "locked up" no error messages, no beeps, no action at all, and no input inhibit indicator. Unplug, replug the keyboard to continue Replace keyboard if problem persists.
Excessive interference, static, or transient received. Check for & eliminate static source, eliminate interference source, AC power source add surge protector.
Kbd port on LU is loose Kbd port is broken, or loose, replace the base LU, call CLI Tech Support.
Device type mismatch Delete the device on the host, recreate the device to match the terminal type.
Terminal session drops off line, recycles, to sign on screen, losing session...Device lost comm/pwr error msg in QSYSOPR MSG QUEUE Macro buffer value invalid, or corrupt CMOS Delete the "bad"(record/play) fkey(manual sec 4.3), or reset CMOS (call CLI TS).
Device type mismatch Delete the device on the host, recreate the device to match the terminal type.
Intermittent AC power Verify AC power source/cbl is good, change AC source, or cable
Electrical short circuit Try different keyboard, if persists, try a different base LU, or move this base to different port.
Marginal twinax signal Replace bad twinax cables, baluns, patch cables, etc.
Problem follows base, different base this location works ok Call CLI Tech Support.
CLI Logo screen... displays message... SETTINGS HAVE BEEN RESET TO DEFAULT VALUES Terminal settings have been reset and lost, "Battery" message in lower right corner of setup screen Power off/on base LU, press spacebar...reset terminal settings, investigate/repair cause (unprotected AC power, shorted twinax lines).
5488V ONLY drops offline back to sign on screen when using shared addressing Wrong emulation selected Select 3488 emulation when using shared addressing. Delete the device, let autoconfig re-create all physical devices when terminal is powered back on.
Terminal causes others to fail on line Wrong address selected Resolve address conflict.
Improper termination on twinax Replace Twinax Y-Connector, troubleshoot cable problem.
Printer session configured on some terminal, no printer attached De-configure printer session on terminal that has no printer attached.
Electrical transient received, zener diodes blown on motherboard Investigate AC source, Twinax line source... repair/protect from source, replace the base LU.
Location causes others to fail on-line Move base LU only to different port, if follows base, replace LU
Terminal drops off line to cursor upper right Defective twinax Troubleshoot twinax lines, Y-conn, baluns, etc...see above for more on cursor upper right.
Terminal drops off-line to cursor upper left, and when type characters appear Device lost power or was reset while in use Vary on, to recover the device, investigate cause of power loss.
Cursor left after recovery attempt Vary off/on the device, try SYSRQ, then enter, if still crsr upper left...delete device on host config, create new device, turn terminal back on. Or, let AS400 autoconfig create device when LU is pwrd on.
Terminal LU makes "buzz" sound Vibration inside LU case Replace base LU, call CLI TS.
Terminal will beep constantly when turned on, and gets no video RAM memory corrupt Replace the base LU, call CLI TS.
Screen shrinks in 132 column mode on color monitor 132 column mode not set properly on monitor Adjust screen size while in 132 mode, then power off/on monitor to save settings.
Blank screen when using passthru, on-line but OK when local 80 column emulation selected Reconfigure terminal for 132 column emulation...3197D, 3477, 3486, 3487,or 3488.
Terminal displays wrong colors on screen Color monitor not properly detected Leave monitor on, turn base power off/on...when in setup should read 5476-C, or 5488-C at top of setup screen .
Device type mismatch Re-configure terminal to match host config.
Wrong emulation selected Re-configure terminal for 3197C, 3477, or 3486,8 (if available)
Terminal will not exit on-line setup screen Printer session configured, but no display session Turn off base power, hold down spacebar, restart, configure display session.
Attached printer will not print No printer session configured Configure printer session with valid address, emulation...printer is online, ready to print.
Printer session, and device configures on host, but no print Monitor printer ready indicator (online setup) "display printer information", if no printer ready indicator, change parallel cable, make sure printer is on-line, and ready to print. You must have printer ready indicator before HOST can see the printer.
Attached printer will not print, cannot start writer Printer ready but no System available indicator (Online setup "Browse printer information" selection) The printer is not using the correct address, or another device is using this address...correct address conflict, and/or re-connect twinax cable.
Device type mismatch Delete old printer device, recycle pwr on base LU/printer let AS400 autoconfig create new printer device at that address, or manually create printer device on host. (If using remote controller, see controller manual for adding new device)
Address conflict Another twinax device was/is configured to use this address, delete/ re-create the device, use different address.
Prints, but not correctly Device type mismatch Delete old printer device on host configuration...recreate device
Wrong printer type selected Select the correct printer on the PRINTER CONFIGURATION menu in off-line setup
Not using Host Print transform Enable Host Print Transform, (*YES) and select the right AS400 driver for this printer in the device configuration.
Puts "garbage" characters on printout Match host print transform driver, within device configuration, with the model/type of the printer. Match printer emulation with device configuraiton on host, and/or replace parallel printer cable.