instructions for the operation of hullmos

Instructions for the Operation of Hullmos

2

VERSION HISTORY

Version Date Description Author Reviewedby

Approvedby

Distributedto

1.91 2005-06-03 Final version RK - - External2.2 2006-01-20 Additions and

clarificationsRK - - -

3.0 2008-08-18 OperationalDisplay added

TR - - -


3

TABLE OF CONTENTS

1. HULLMOS OVERVIEW __________________________________5

1.1. SOFTWARE GENERAL ARRANGEMENTS ______________ 6

1.2. MAIN DISPLAYS ______________________________________ 7

1.3. STARTING HULLMOS _______________________________ 11

1.4. MAIN MENU ________________________________________ 12

1.5. STARTING MODULES _______________________________ 13

1.6. ALARMS ____________________________________________ 14

2. CONFIGURATION OF HULLMOS ______________________ 16

2.1. HULL MONITORING CONFIGURATION ______________ 17

2.2. VESSEL CONFIGURATION __________________________ 21

2.3. USER CONFIGURATION ____________________________ 23

2.4. SYSTEM SETUP AND MAINTENANCE _______________ 24

3. HULL MONITORING MODULE _______________________ 26

3.1. HULLMONITORING DISPLAY _____________________ 27

3.2. SIGNAL HISTORY DISPLAY _________________________ 29

3.3. SENSOR DISPLAY __________________________________ 31

3.4. GENERAL __________________________________________ 32

3.5. LOG FILES _________________________________________ 33

4. GENERAL CONSEPTS ________________________________ 35

4.1. TIME FORMAT _____________________________________ 36

4.2. LOGGING __________________________________________ 37

4.3. ARCHIVING ________________________________________ 38

5. OTHER MODULES ____________________________________ 39

5.1. HULLMOS GENERAL SERVICES MODULE __________ 40

5.2. ARCLAN ____________________________________________ 41


4

5.3. STRAINA ___________________________________________ 425.4. HAM _______________________________________________ 43

6. ALARM LIST AND ERROR CODES ____________________ 44

6.1. HGS ALARMS ______________________________________ 45

6.2. SAM ALARMS ______________________________________ 46

6.3. LAN ALARMS _______________________________________ 47

7. CONFIGURATION FILES ______________________________ 49

7.1. HGS.INI ____________________________________________ 50

7.2. SAM.INI ____________________________________________ 51

7.3. LAN_RS422.INI _____________________________________ 53

8. ACCOUNTS AND PASSWORDS ________________________ 55

8.1. HULLMOS PASSWORDS ____________________________ 56

8.2. WINDOWS XP PASSWORDS ________________________ 57


5

1. HULLMOS OVERVIEW


6

1.1. SOFTWARE GENERAL ARRANGEMENTS

Picture 1 – Hullmos software general structure

Basic installation of Hullmos contains Hullmos Server PC. One or moreclient PC’s may connect to the Sever PC via Ethernet connection andhave the exactly same displays available as on the Hullmos Server.There is 5-10 second delay between the Server and Client depending onthe Ethernet speed.

Log files are stored on the Hullmos Server PC. Log files may betransferred to the Client computers via Ethernet or by using removablemedia (Removable Hard Disks with USB connection are recommended.Also USB Memory Sticks are convenient for small amount of data).


7

1.2. MAIN DISPLAYS

Hullmos software has two main displays intended for the normal users.User is able to switch between the displays.

1.2.1. HULL MONITORING SENSOR DISPLAY

Picture 2 – Hull monitoring sensor display

The overview of strain sensors shows the maximum, minimum, andmean of total measured strain and minimum and maximum of wave-induced strain. The type of strain (longitudinal hull bending, vertical hullbending, etc.) is shown on the scale.

For accelerometer(s) is shown maximum, minimum and meanacceleration and slam count. The type of acceleration (verticalacceleration, longitudinal acceleration etc.) is shown on the scale.

On the bottom of the screen is the sensor locations.

The height of the bar indicates the amount strain. The actual value isshown under the bar as numerical value.


8

As a reference, on the display is shown the following values ashorizontal color lines:

Alarm limit (Red line) User adjustable warning criteria (Yellow line) Load calculator reference value (white line)

These values are updated based on the update interval defined in theconfiguration. This is normally between 5-30 minutes depending on theclass rules.


9

1.2.2. HULLMOS MAIN OPERATIONAL DISPLAY

Picture 3 – Main display

This display is intended to be the main display for the operatingpersonnel.

On the main display there are shown two bars: instantaneous stress andmaximum stress in a user selectable time window. For this display thereading of every sensor in the installation is compared to the referencevalue for that sensor and the maximum of those is shown as percentagefigure in the bars. In the system set-up the reference value can beselected to be maximum value accepted by the Class, the design valueor material limit e.g. yield limit.

Instantaneous stress is the selected maximum valuefrom all the sensors in the system The color and theheight of the bar indicate the severity. The reading isshown as numerical %-value.

Maximum stress over past n minutes is the nminute’s maximum reading; where n can be userselected. Range of n is 1-120 minutes. The height


10

and the color of the bar indicate the severity and thereading is shown as numerical %-value.

On the time history i.e. on the trend are the maximum severities forselected time history length. Time history length can be user selectedfrom predefined values: One minute, 30 minutes, One hour, Two hours,8 hours, 24hours. User is able to change the time offset with scroll bar.Time offset is returned to present time after 30 seconds of inactivity.

User selectable alarm limit is shown as yellow line and is the same for allvalues on the display. User selectable alarm limit may be adjusted bydragging the red triangle attached to the alarm line.


11

1.3. STARTING HULLMOS

1.3.1. STARTING THE APPLICATION

Picture 4 – Starting Hullmos

Hullmos is started from the Windows XP start menu by selecting HAL:

(HULLMOS Application Launcher)

All the data acquisition modules and analysis modules are started asbackground processes. The user interface needs user identification (Seenext chapter).

1.3.2. LOGGING IN

Picture 5 – Logging in

After successful starting of the application, a dialog box asking usernameand password appears to the screen. Type your username and passwordand press OK.


12

1.4. MAIN MENU

Picture 6 – Hullmos main menu

After succesful logon, Hullmos main menu appears on the screen. Withthis menu the administrator can access all the options available in theHullmos system. System user can start the modules and manage alarms.


13

1.5. STARTING MODULES

Picture 7 – Starting modules

Modules can be started from the Hullmos main menu.


14

1.6. ALARMS

Picture 8 – Alarm list: All alarms

Picture 9 – Alarm List: Active alarms

Each alarm has three conditions: Red condition, yellow condition andgreen condition.

Red condition indicates that alarm is active. Yellow condition indicates that alarm is active, but it

is accepted by the user. Green condition indicates that the alarm is inactive.

On the main menu (Picture ) is the overall state of the alarms shown asgreen, yellow or blinking red icon. The overall state of the alarms is red


15

if there is at least one alarm in red condition, yellow if no alarms are inred condition and at least one alarm is in yellow condition and green ifno alarms are in red or yellow condition.

1.6.1. ACCEPTING ALARMIf an alarm is in red condition, it is possible to accept the alarm. Afteralarm has been accepted, its state is yellow until the errorcondition thatcaused the alarm is resolved and its state is changed to green.

1.6.2. DISABLING / ENABLING ALARMUser is able to disable one certain alarm. List of disabled alarms is storedin alarms log part of the periodic report file. Disabled alarms have noeffect on the overall alarm state.


16

2. CONFIGURATION OF HULLMOS

Picture 10 – Configuration menu

Only user with administrator rights is allowed to make changes to theconfiguration. System users are allowed to view the configuration.


17

2.1. HULL MONITORING CONFIGURATION

Hull monitoring configuration has three dialogs: Reporting, sensorconfiguration, and sensor locations configuration.

2.1.1. FILES

Picture 11

On the reporting configuration (Picture ) it is possible to edit the logging,reporting and backup settings. It is possible to change the file names,intervals and enable and disable logging and reporting. It is also possibleto do the logging, reporting or backup manually.


18

2.1.2. STRAIN SENSOR CONFIGURATION

Picture 12 – Strain sensor configuration

The display contains the list of all strain sensors and accelerometers.Only administrators are allowed to make changes to the configuration.Following values are shown on the screen:

General, general settings. Sensor name, name of the sensor. Sensor function, more detailed description of

the sensor function. Notes, free text. Sensor type, available types for Hull Monitoring

are “LBSG, “SBSG” and “ACC”. Sensor software version, version number of

the embedded software on the sensor. Identification, sensor identification numbers.

Sensor tag, running number. ID, unique identification number of the sensor. Arcnet ID, unique network identification number

(=ID MOD 255), shown for reference only.


19

Calibration, sensor calibration settings. Initial value, offset in base unit. Also shown as

binary units for reference. Calibration coefficient, calibration coefficient

provided by the supplier. The resulting value aftermultiplication must fit to 16 bits; thus valid rangeis from –31.0 to 31.0. Has no effect for virtualchannels.

Base unit, name for the base unit (for example,µStrain or cm/s²). Special characters (µ, ², º,etc.) can be entered by pressing the ALT-key andinputting the characters ASCII code (µ = 230,²=253, º=167).

Secondary unit conversion factor, conversionfactor to convert from base unit (for example,from µStrain to kN or from cm/s² to g).Secondary units are only shown on the userinterface displays.

Secondary unit, name for the base unit (forexample, kN or MPa). Special characters (µ, ², º,etc.) can be entered by pressing the ALT-key andinputting the characters ASCII code (µ = 230,²=253, º=167).

Limits 100% criteria, the value of base units that

corresponds to 100%. Classification criterias, different criterias

defined by the class. Frequency, sensor sampling frequencies. Only for

sensor software versions 1.02 and above. Values per packet, number of values per

packet (1-200), the larger the number the largerthe delay between packets.

Filter cutoff-frequency, cut-off frequency forthe analog filter in the sensor.

Internal sampling frequency, internalsampling frequency.

Skip n samples for logging, the number ofsamples to skip before uploading.

External logging frequency, the actual loggingfrequency seen on the log files and on the timehistories. Shown for reference only.

Time between packets, for reference only. Sensor configuration, enable/disable software

modules on the sensor. Disable all sensor modules toindicate virtual channel.

Update interval, update interval for processedsensor data in seconds.


20

2.1.3. SENSOR LOCATIONS

Picture 13 – Sensor location configuration

On the sensor locations display administrator may change the locationsof the sensors for the user interface displays. Changing the sensorlocation is done by selecting the sensor and double clicking with cursorat the selected place.


21

2.2. VESSEL CONFIGURATION

Vessel configuration has two dialogs: Vessel settings and profile settings.

2.2.1. VESSEL SETTINGS

Picture 14 – Vessel configuration – Vessel settings

In the vessel settings is the general information about the vessel and thecurrent voyage to reports and logfiles is input to the system.

Ship data is the ship name, owner and type. Voyage data has fourcomponents: Port of loading, port of discharge, departure date andarrival date.

2.2.2. PROFILE SETTINGS

Picture 15 –Vessel configuration - Profile settings


22

On the profile dialog it is possible to change the ships profile that is usedas background image in the modules (See example on Picture ) Picturescan be changed by browsing button and then selecting a new picturefrom the windows file system. Pictures should follow the generalguidelines of the user interfaces (Resolution of 903*561*24). Using oftoo complex pictures should be avoided.


23

2.3. USER CONFIGURATION

Picture 16 – User configuration

On this display user can change his password. Administrator may alsoadd users, delete users and change user levels.

User may user the basic functionality of Hullmos,but can not change the system configuration and cannot access the advanced and possibly confusingfeatures of Hullmos.

Manager may change system configuration andperform basic maintenance operations.

Analyst may access the more advanced features ofHullmos, but has no full access to the systemconfiguration.

System Supplier has full access to everything. Thisuser level should not be used after initial setup.


24

2.4. SYSTEM SETUP AND MAINTENANCE

2.4.1. INITIAL SETUPThe supplier performs initial system setup. Quick reference is includedhere for troubleshooting purposes. Supplier or suppliers representativeshould be consulted before these changes.

1. Clear all configuration files.2. Start Hullmos and log in as Administrator. User base must

always exist.3. Go to Configuration/Vessel. Enter vessel specific data and

click OK.4. Go to Configuration/Hull Monitoring. Add sensors one by one

and enter all sensor specific data, but as a minimum:Sensor ID (See system drawings), Calibration coefficient(Provided by the supplier), Sensor configuration (Enableall modules), set Update interval (See class rules), setFrequencies (See class rules) and set sensor Enabled.Click Ok.

5. Go to Configuration/Ice Load Monitoring. Add sensors oneby one and enter all sensor specific data, but as aminimum: Sensor ID (See system drawings), Calibrationcoefficient (Provided by the supplier), Sensorconfiguration (Enable all modules), set Frequencies (Seeclass rules for bandwidth and sampling rate) and set sensorEnabled. Add virtual channels the same way, but disableall modules on Sensor configuration. Define the virtualchannel calculations (see also Raport D-78). Click Ok.

2.4.2. MAINTENANCEREPLACING SENSORS OR SENSOR AMPLIFIERS

Supplier or suppliers representative should be consulted before thesechanges.

1. Go Configuration/Hull monitoring or Configuration/Ice Loadmonitoring depending on the faulty sensor type.

2. Disable sensor. Click Ok.3. Replace sensor (See installation manual).4. Enter new Sensor ID and new Calibration coefficient

(Provided by the supplier). Enter new initial value(instructions provided by the supplier).

5. Enable sensor.


25

SENSOR ZERO ADJUSTMENT WIZARD

Picture 17 - Zero adjustment wizard

1. Select Zero Adjustment Wizard from the Maintenance Menu fromHullmos Main Menu.

2. Wizard shows the mean value for each channel and proposes anew offset to set the reading to zero.

3. If the proposed offset is ok and the sensor is in such conditionthat the reading should be zero, accept the new offset by pressingAdjust Zero button. If the proposed offset is not ok or the sensoris in such condition that it should not be adjusted, press Move tonext without adjusting.

4. Go thought the sensors.

The proposal is made based on the sensor mean value. Do notuse the wizard again until new mean value is calculated.


26

3. HULL MONITORING MODULE


27

3.1. HULLMONITORING DISPLAY

3.1.1. SENSOR OVERVIEW DISPLAY

Picture 18 – Hull monitoring main display

The overview of strain sensors shows the maximum, minimum, andmean of total measured strain and minimum and maximum of wave-induced strain. The type of strain (longitudinal hull bending, vertical hullbending, etc.) is shown on the scale.

For accelerometer(s) is shown maximum, minimum and meanacceleration and slam count. The type of acceleration (verticalacceleration, longitudinal acceleration etc.) is shown on the scale.

On the bottom of the screen is the sensor locations.

The height of the bar indicates the amount strain. The actual value isshow under the bar as numerical value.

As a reference, on the display is shown the following values ashorizontal color lines:

Alarm limit (Red line)


28

User adjustable warning criteria (Yellow line) Load calculator reference value (white line)

These values are updated based on the update interval defined in theconfiguration. This is normally between 5-30 minutes depending on theclass rules.


29

3.2. SIGNAL HISTORY DISPLAY

Picture 19 – Signal History Display

Signal history (Picture ) shows the previous values of the strain sensorsand accelerometers.

With the dropdown list on the right side of the sheet is possible to selectthe strain sensor or accelerometer to view.

Picture 20 – The options for selecting the data to be viewed.

By checking one of the options (Picture ) it is possible to select whichdata to view on the graph. Minimum and maximum values are shown asbars from minimum value to the maximum value and all the other valuesare shown as bars from zero to the value.


30

As a reference, on the display is shown the following values ashorizontal color lines (only for Minimum and Maximum reading, Meanand Raw signal):

Alarm limits (Red line) User adjustable warning criteria (Yellow line) Load calculator reference value (white line)

On the left side of the graph is the scale.


31

3.3. SENSOR DISPLAY

Picture 21 – Sensor display / Top view

On the sensor locations display (Picture ), the locations of the sensorsare shown. With the radiobuttons below the picture user can selectbetween top view (Picture ) and side view of the ship.

By double clicking sensor icon user can view the current readings of thesensor


32

3.4. GENERAL

3.4.1. SCALES AND UNITS

Picture 22 – The Pop-up menu for scales and units

Scales and units can be changed by clicking the right mouse button onthe scale. Scales and units are channel depended, e.g. changing thescale of one channel on one display changes the scale of that channelon all the displays. Scale settings are local (The client machines andserver machines have own scale settings) and are saved on exit. Ifmeaningful 100% limit exists for the sensor user may also use colorscale (with 100% being red, 0% green and –100% red).

Picture 23 – Changing the scale


33

3.5. LOG FILES

Log files are in ascii format and values are comma separated and can beeasily imported to a spreadsheet program for further analysis. Unit usedfor logging is always the base unit of the channel. Each channel has itsown log files. Log directory structure is as follows:

C:\Logging\C:\Logging\Processed\C:\Logging\Rainflow

3.5.1. RAW SIGNAL LOG FILERaw signal log file contains the raw signal sampled at selected rate(20Hz). First value is the measured value, second value is the wave-induced component, third value is the sensor diagnostis bit, and fourthvalue is the time stamp. Time stamp and sensor diagnostics bit areavailable once per packet.

7,79,99,9,0,23:59:32.7369,97,79,98,87,79,97,78,8

Each day of the month has its own log file for each sensor. Files areoverwritten after one month.

3.5.2. PROCESSED SIGNAL LOG FILEProcessed signal log file contains the processed values. User selects theupdate interval. The values in the log are: Sensor ID, sensor diagnosticsbyte, date, time, mean, standard deviation, peak pos., peak neg., peakto peak, zero crossing value.

72 0 2004/10/04 - 13:15:21.536 -77 1 -71 -82 11 072 0 2004/10/04 - 13:18:21.510 -77 1 -72 -81 9 072 0 2004/10/04 - 13:21:21.485 -76 1 -72 -81 8 072 0 2004/10/04 - 13:40:05.091 -77 1 0 -82 81 072 0 2004/10/04 - 13:50:04.999 -77 1 -71 -84 12 0

Each sensor has its own log file. Files are not overwritten.

3.5.3. RAINFLOW LOG FILE000002


34

000015000001000000000000

Each sensor has its own log file. Files contain cumulative rainflow cyclecount and the current count is updated to the file. No time history isstored of the rainflow count.


35

4. GENERAL CONSEPTS


36

4.1. TIME FORMAT

Time format used in log files and file names is according to ISOstandard: YYYY-MM-DD-HH:MM:SS.MS.


37

4.2. LOGGING

Log file names contain part of the time stamp to separate log files fromdifferent days. For example, log file that contains one hour of data andis kept in the disk for one month before overwriting has DD-HH in its filename. After one month the same file name is used and the old log file isoverwritten.


38

4.3. ARCHIVING

If archiving is selected the log files are archived daily at 00:15. Thearchived files are removed after stored in archive file. The name of thearchive file is Logging-YYYY-MM-DD.Zip.

In archiving there is a five day delay, eg. on 2005-08-08 at 00:15archive file named Logging-2005-08-03 .Zip is created and log files olderthan five days are archived. If archiving fails for some reason, eg.maintenance break, one archive file may contain more than one day ofdata.


39

5. OTHER MODULES

The modules described in this chapter are not in the interest of basicuser of the Hullmos system. They are briefly described here fortroubleshooting / maintenance purposes only.


40

5.1. HULLMOS GENERAL SERVICES MODULE

Picture 24 – HGS Maintenance Screen

Loads the configuration from the disk and saves itback to the disk when changed.

Manages the connections between server andclient(s).

Checks if the modules are updating, and if not, signalthe other modules that the particular module is notresponding and therefore the data produced by thatmodule is not reliable.

Maintenance screen shows the state of the othermodules and the state of the connections.

Launches archiving process once a day Related configuration file: HGS.INI


41

5.2. ARCLAN

Picture 25 – ARC_LAN Maintenance Screen

Handles the arcnet traffic. Receives the data from sensor and puts it into

memory for other modules to use. Maintenance screen shows the last arcnet

message(s) received from each sensor. RS422 receiving. RS422 sending for VDR and other systems. Related configuration file: LAN_RS422.INI


42

5.3. STRAINA

Picture 26 – StrainA Maintenance screen

StrainA is the analysis part of the Strain Analysismodule and it is running all the time, unlike the userinterface part, which can be shut down.

Analysis methods Logging Reporting System backup Checking the error limits of strain sensors This is the module that handles the information from

strain sensors and accelerometers before shown touser by Strain Analysis user interface module.

Most of the strain analysis data is, however, availablewithout this module as it is processed by the sensoritself.


43

5.4. HAM Hullmos alarm module Collecting the alarm states from other modules Alarm log System log (calibration factors and zero factors for

each channel)


44

6. ALARM LIST AND ERROR CODES


45

6.1. HGS ALARMSName Error code DescriptionXxx Died 0 No update for module xxx has been

detected. For server this indicates thatthe xxx module has encountered aninternal error, for client this indicatesthat the xxx module has encounteredan internal error OR the update hasnot been detected because of aethernet error or server shutdown.Xxx is either HAM, LAN or SAM


46

6.2. SAM ALARMSName Error code DescriptionXXX limit exceeded on sensorYYY

0 XXX limit has been exceeded onsensor number YYY. XXX standsfor different types of limits, such asUser Selectable or ClassificationLimit.


47

6.3. LAN ALARMSName Error code DescriptionDriver error See 6.3.1 Error detected in the driver / cardNet error See 6.3.1 Error detected in the arcnet networkCard error See 6.3.1 Error detected with the arcnet

network interface.LAN ERROR DUE TOSENSOR x

Sensor has been defined in theconfiguration, but no messages arereceived from the sensor or messagescan not be processed correctly(message corrupt or file error) and /or no messages can be sent to thesensor.

6.3.1. ARCNET DRIVER ERRORCODESArcnect driver error codes are returned as part of ‘Net Error’,‘Card error’and ‘Driver Error’. The information is provided here for troubleshootingpurposes only. Source: Sohard Arcnet documentation.

Table 6-1 Arcnet runtime errors

Name (declared inFARC.H) Errorcode Cause

E_FARC_DRIVER_NOT_STARTED 2 Driver currently not started

E_FARC_ABORT 995 Request cancelled due to Init/Deinit orreconfiguration of network

E_FARC_INCOMPLETE 996 Request pending (this is not an error)E_FARC_PENDING 997 Request pending (this is not an error)E_FARC_DRIVER_OPTION 3758425001 IoDeviceControl -Code not supported

E_FARC_NO_TOKEN 3758425008No token seen. (ARCNET Controller doesnot detect a valid token. May occur, ifbusrate does not match)

E_FARC_NOT_INITED 3758425018 No IOCTL_FARC_INIT yet performedE_FARC_EXCESSIVE_RECON 3758425021 Controller reconfigures network (No other

nodes are on the net)E_FARC_BUFFER_TOO_SMALL 3758425022 output buffer size too small in call to

DeviceIoControlE_FARC_NO_PARAMETERS 3758425023 dcb-struct invalid

E_FARC_BAD_PACKET_SIZE 3758425024 WriteFile: wrong packetsize, ReadFile:

wrong buffersize

E_FARC_NO_ACTIVITY 3758425029no netactivity deteced (ARCNETController does not detect any activity onthe net)

E_FARC_PERFORMING_ 3758425031 IOCTL_FARC_DISABLE not yet


48

DISABLE finished

E_FARC_NO_DISABLE 3758425032no previousIOCTL_FARC_ENABLE_RECEIVEperformed

E_FARC_BAD_SID 3758425037 WriteFile: wrong Source ID (SID)

E_FARC_DUPID 3758425052 Duplicate node-id detected (another nodeis online with the same node id)

E_FARC_NO_RESPONSE 3758425055 Destination node does not respondE_FARC_NO_LONG_PACKETS 3758425056 Destination node does not support long

packets

E_FARC_INIT_FORCED 3758425058 init forced, inspite of no token or nonetactivity

E_FARC_NO_NEXTID 3758425059 no new-next-id received duringinitalization

E_FARC_WRITE_DENIED 3758425061 Currently no transmission page free

E_FARC_NAK_TX 3758425070 Destination node does not acknowledgetransmitted packet

E_FARC_INITIALIZING 3758425071 ReadFile/WriteFile not accepted, becauseinit running

E_FARC_BAD_PARAMETER 3758425087 wrong parameters in dcb detected (e.g.

nodeid = 0)Table 6-2 Errors during startup

Number inWindows NT

Number inWindows 2000(Event ID)

Cause

8 2390C66 adapters only: DPR of adapter is notvisible, setup your BIOS to enable the usedISA memory

57 194 No ARCNET-adapter found in system atgiven I/O-Adress

60 197wrong controllertype (if using a PCI-adapterwith NT 4.0, try „Reset Card-ID“ (see alsoConfiguration)

87 n.a. Resource conflict (I/O-Adress or IRQ)or invalid parameters in registry

317 618 main vendor identification wrong or missing

487 n.a.

Resource conflict (memory-mapped adress,check jumpers on adapter) on ISA-Adapter. Ifusing PCI-Adapter, swap the used slot withthe slot of another PCI-adapter (Bug in PCI-Bios)

1018 380 Some or all registry entries missing (reinstalldriver)

1450 154 not enough ressources, to start the driver

1388 379 PCMCIA adapter is not a SH ARC PCMCIAadapter

50 187 used ARCNET adapter is not compatible toSOHARD ARCNET adapter


49

7. CONFIGURATION FILES

Hullmos configuration files are standard .INI files.


50

7.1. HGS.INI

7.1.1. SECTION GENERALGeneral section defines some general HGS settings.

Archive flag defines if the archiving of log files is onor off.

HGSHeartBeatInterval defines how often inmilliseconds the main loop of HGS should beexecuted. For server or standalone Hullmos stationsthis should be 5000. For client stations this dependson the network speed, for 1GBps networks 10000 isrecommended, for 100MBps networks 50000 isrecommended. If more than one client is connectedto the server, the “main” client (eg. bridgecomputer) should have interval of 10000 and theother clients (eg. researchers laptops or additionalstation in the cargo control room) should havesignificantly higher intervals (50000 or more).

Sbsgs, Lbsgs, Acc and Ice define the number ofsuch sensors installed in the system, including virtualchannels.

[General]Archive = 1HGSHeartBeatInterval=5000Sbsgs=6Lbsgs=0Acc=1Ice=6


51

7.2. SAM.INI

7.2.1. SECTION GENERAL GlobalMAX defines the maximum of the scale for

the main display for strain sensors. GlobalMIN defines the minimum of the scale for

the main display for strain sensors. GlobalSIZE defines the size of the scale for the

main display for strain sensors. GlobalUNIT defines the unit to be shown on the

main display for strain sensors. AccGlobalMAX defines the maximum of the scale

for the main display for accelerometer(s). AccGlobalMIN defines the minimum of the scale

for the main display for accelerometer(s). AccGlobalSIZE defines the size of the scale for the

main display for accelerometer(s). AccGlobalUNIT defines the unit to be shown on the

main display for accelerometer(s). Location1Tag defines the channel number to be

shown at the leftmost position. –1 means no value isshown at that position. (Location2Tag is the samefor the next position etc).

AccLocation1Tag defines the channel number tobe shown at the leftmost position. –1 means novalue is shown at that position. (Location2Tag is thesame for the next position etc).

[General]GlobalMAX=1997GlobalMIN=-1997GlobalSIZE=205GlobalUNIT=1AccGlobalMAX=1500AccGlobalMIN=500AccGlobalSIZE=250AccGlobalUNIT=1Location1Tag=0Location2Tag=7AccLocation1Tag=10Location3Tag=8Location4Tag=9Location5Tag=-1Location6Tag=-1

7.2.2. SECTION SCALESection scale is defined for each sensor in the system (Scale 1, Scale 2etc.). Section defines the individual scale for each sensor and each type


52

of value. These scales are used when one sensor is selected for closerexamination. On the main display the global scale is used.

[Scale 7]MinMaxMIN=-1004MinMaxMAX=1004MinMaxSIZE=102MinMaxUNIT=1RawMIN=-2000RawMAX=2000RawSIZE=250RawUNIT=1STDMIN=0STDMAX=200STDSIZE=10STDUNIT=1ZeroMIN=0ZeroMAX=60ZeroSize=10ZeroUNIT=3PeakToPeakMIN=0PeakToPeakMAX=500PeakToPeakSIZE=50PeakToPeakUNIT=1


53

7.3. LAN_RS422.INI

7.3.1. SECTION NMEA_INSection NMEA_In defines if NMEA data should be received, and fromwhich ports it is received.

Enabled defines if the NMEA receive should beenabled

NumberOfChannels defines how many incomingNMEA channels exists.

Port1 defines the COM port number for channelnumber 1 (Port2 for channel number 2 etc.).

Port1Baud defines the baud rate (default 4800) forchannel number 1 (Port2Baud for channel number 2etc.).

Port1Databit defines the number of databits(default 8) for channel number 1 (Port2Databit forchannel number 2 etc.).

Port1Parity defines the parity setting (defaultNONE) for channel number 1 (Port2Parity for channelnumber 2 etc.).

Port1Stopbit defines the number of stopbits(default 1) for channel number 1 (Port2Stopbit forchannel number 2 etc.).

Default values are according to the NMEA standard.Default values are used if nothing else is spesified.

[NMEA_In]enabled = 1numberOfChannels = 3

;Example:;;Port1 = port number;Port1Baud = 4800/9600;Port1Databit = 7/8;Port1Parity = 0/1/2 = None, Odd, Even;Port1Stopbit= 1/2

Port1 = 11Port1Baud = 9600Port1Databit = 7Port1Parity = 0Port1Stopbit = 1

port2 = 12

port3 = 7


54

7.3.2. SECTION NMEA_OUTSection NMEA_Out defines if NMEA should be sent, and to which COMport.

Enabled defines if data should be sent Port defines the port number.

[NMEA_Out]enabled = 1port = 10


55

8. ACCOUNTS AND PASSWORDS


56

8.1. HULLMOS PASSWORDS

Account Password

Administrator

User


57

8.2. WINDOWS XP PASSWORDS

Account Password

Administrator

instructions for the operation of hullmos

Documents