Moxa Technologies C360 manual Hardware Cause and Solution

Page 46

Appendix B

Technical Reference

 

 

Hardware Cause and Solution:

aWrong IRQ setting. If the hardware and software IRQ setting do not match. MOXA driver will use a polling scheme and thus causes slow operation. Try to match the IRQ settings.

6Under UNIX, when respawning quite a few number of tty ports, the following error messages appear: "Time out table overflow", "File table overflow", "Region table overflow".

Software Cause and Solution:

The above error messages imply that the system resources are exhausted. User should tune the kernel parameters to a larger value and rebuild the kernel to be able to accommodate the new configuration. Refer to UNIX system manual about how to tune the parameters and rebuild kernel.

"Time out table overflow" "File table overflow" "Region table overflow"

:NCALL parameter too small.

:NFILE or NINODE parameter too small.

:NREGION or NPROC parameter too small.

7Under UNIX, the newly rebuilt kernel could not boot.

Software Causes and Solutions:

The C360 driver might not be built into the new kernel correctly.

a Please use the last good kernel backup to boot again. The kernel backup in UNIX is /unix.moxa or /stand/unix.moxa.

b Then remove the C360 driver. Refer to Section 4.3 for driver removal.

c Re-install the C360 driver once more.

~40~

Image 46
Contents C360 Copyright Notice Moxa Internet Services Table of Contents Appendix a Troubleshooting Page Introduction OverviewSpecifications Features and SpecificationsFeatures SystemControl Board Async ConcentratorCheck list C360 Control BoardRack Mount Kit Hapter 2 Hardware Installation Installation of C360Hardware Installation ∙ ∙ Chapter Hub Rack Mount KitDiagnostics LED IndicatorsSerial Number of the Async Concentrator ~10~ Hardware Installation ∙ ∙ Chapter Driver Installation Software Driver Installation and SetupControl Board Configuration Driver Setup Driver Loading~14~ Driver Removal Moxa Serial Port Naming ConventionDOS API-232 Library and Programming Languages AdministrationsAsync Concentrator Status Monitoring Async Concentrator Diagnostics Data ScopeDriver Installation For Unix UsersFor Unix Users ∙ ∙ Chapter Moxa TTY Ports Moxa TTY and Non-TTY PortsConvention of the Moxa TTY device name is Tty + a + B + C Moxa Non-TTY PortsConfiguration Async Concentrator Serial Number TTY or Non-TTYMonitoring DiagnosticsDriver Reset Concentrator RestartProgramming the Moxa TTY Ports Using Standard Unix API Terminal EmulationExtended Function List for Moxa TTY Ports Function DescriptionMobufed Mhwflow Programming the Moxa Non-TTY Ports Using Moxa Unix API-232 Function ListClose a non-TTY port Function DescriptionOpen a non-TTY port Read data from a non-TTY portNon-TTY port parameter setting Write a string of data to Tx bufferSend break signal Flush Tx/Rx buffer dataRead the length of data queued in Tx buffer Read the length of data queued in Rx bufferGet modem line status Set modem line control signal RTS Set modem line control signal DTRSetting CTS/RTS and XON/XOFF flow control Disable transmitting data Enable transmitting dataAppendix a Hardware causes and solutions Software Cause and SolutionSoftware Causes and Solutions Solution RTS DSR CTS DTRHardware Cause and Solution Under UNIX, the newly rebuilt kernel could not bootAppendix B Ethernet CablingAsync Concentrator and Serial Number RJ-45 Female Connector RS-232 Cable WiringDTE GND RTS CTS DSR Appendix C Appendix C ∙ Problem Report Form Customer name Company Date Tel FaxWarranty