July 27, 2013: Create the Ophir Project. Add the King Probe Adjustment factor (set to 0.5) to Ophir fml.300 table.
July 30, 2012: M300 Software updated o the latest version.
January 12, 2012: Moved active USB port from front to back so that both back USB ports active. Will use the second USB cable to connect to KVM switch keyboard.
January 12, 2012: Removed version 1 SBUS card and installed version 2 SBUS that was being used in the M200. Nothing wrong with old SBUS card. Old SBUS card was installed in M200.
February 8, 2011 Installed the DMT ISACAPS card into the S.E.A. M300. Working w/ Dave on the 15 pin interface cable from card to the plane data box. Its address on the card is 1019.
March 7, 2011 Received 2DC card back from S.E.A. Installed into M300 for testing.
November 7, 2012 Installed 1D#0 0x0700 S/N 1033 in the M300 for the PCASP probe.
If you get a black screen at start up it is likely do to a system file problem on disk
Add chkfsy -vP / after /etc/netstart in /etc/config/sysint
The /home/bypass/timesync.awk need to be run to sync the M300 to the Time Code Generator. This sync the time to UTC. The programs (/bin/rtc, /bin/date, and bin/rtc) were set with file mode +s to enable the timesync.awk script to be run without being root.
The M300 is configured on the aircraft network to use static IP Address of 192.168.0.110. The M300 has a NTP server running where other computers on the network can sync there time to.
#!/bin/bash
/bin/stty baud=19200 stopb=1 bits=8 </dev/ser10
`head -1 /dev/ser10 | awk '
BEGIN { FS = "," }; \
{ $timestr=$1; \
$timeout=substr($timestr,5,2) substr($timestr,7.2) "." substr($timestr,9,2); } \
END { print "date " $timeout };
' | cat
rtc -s hw
1) Make a new directory in the archive directory
* syntax for directory: undlab_yymmdd
2) cd back to undlab directory
3) Copy everything in undlab directory to new directory in archive
*syntax: cp * /yyyy/archive/undlab_yymmdd
1) In the directory (i.e. /2013) above where the project directory is located type
tar -cvf ophir_130725.tar ophir
to create a tar file (ophir_130725.tar) project directory (ophir).
2) Copy tar file to the PCMCIA car or USB drive
cp ophir_130725.tar /dos/c
3) Remove the PCMCIA card or USB drive.
4) Copy the tar file off the PCMCIA car or USB drive.
1) Type: cd ~ 2) Type: df (make sure /dos/c is listed) 3) Copy archived data to /dos/c 4) Type: uking (to unmount the king card)
To read serial data that is automatically being pushed to the m300 from the command line, use serread. For most instrumentation, the syntax follows the pattern:
serread -b # port
where # is the baud rate of the incoming data and port is the port name/address. For example, to read the data coming in from the TDL on serial port #6:
serread -b 9600 /dev/ser6. For more information about the serread command, see the SEA Utilities (SeaUtils.pdf) manual.
/home/ .kshrc Using alias gpst='timesync -b 9600 /dev/ser10' to sync the computer software does not also sync the hardware.
Cause: Permissions issue: to change the hardware clock, must be a superuser.
Temporary Solution: Use su command to become root, type in password. Use rtc hw command to sync hardware clock.
Tried to use the M300 data acquisition software GUI to change from the CAPE2015 project to the OLYMPEx project. After OLYMPEx directory selected, M300 software crashes with no errors in the M300 Logger window and generates the following message on the command line: “Terminating from signal: 0x000B Fault: 000E SIGSEGV: IP 0005:034E4C96 Pos”. Also tried:
All efforts lead to M300 system crashing with the same command line error message.
Cause: Think that M300 software updates introduced a bug into the software when loading a new project.
Temporary Solution: Change Project=/2015/cape to Project=/2015/olympex in the /usr/bypass/.sea/M300a.cfg file and delete the other M300?.cfg files.
All appropriate breakers were on but M300 wouldn't power on.
Cause: Power supply unit failed and needed to be replaced.
Solution: Bought and installed new power supply unit.
Old PSU: Enermax S3FC2 Whisper 430W PSU (model #: EG465P-VE)
New PSU: Thermaltake Smart 650W with Active PFC (model #: SP-650P)
Errors were appearing in the M300 log window and in the computer terminal window such as:
Cause: M300 CPU was not detecting the M300 software key (iButton) to run acquisition and file writing functions in the M300 software.
Solution: Temporary Solution: Move M300 software key (iButton) to different RS-232 serial port (/dev/ser5). Make sure current project is not using the same serial port as an instrument otherwise could break M300 software key.
When above errors were first encountered, the M300 computer was rebooted several times. The M300 computer was then taken out of the flight rack and connectors between M300 software key and serial port were wiggled to test to see if there was an issue of a loose connector. The extension cable between the M300 software key and the serial port was removed to determine if there was a problem in the extension cable.
Augie at SEA Inc. was called for additional assistance. He suggested typing in 'system -check' to determine the status of the M300 software key. The results were:
Augie suggested that the .bolt.3038 and the .key.3038 files were corrupt and emailed a new set of files. The new files were installed, but the CPU still did not recognize the M300 software key. Augie provided the codes to use the SPP/CDP and the CAPS (CIP) in the Security window (type 'Security' in command prompt). Continuity was checked between the serial port pins in the back of the M300 computer frame and the pins leading into the CPU. The cable between these two areas passed the continuity test.
Augie then suggested to move the M300 security key from the RS-232 port in the back of the M300 to another open RS-232 port. The M300 security key was moved to serial port #5 (/dev/ser5) and the 'Port' in the Security window for the M300 security key was changed from /dev/ser1 to /dev/ser5. Tested the change and the changed worked. Further testing will be needed to determine if the serial port is viable or not.
Disk #2 could not be use as a backup of Disk #1.
Cause: Disk #1 was modified so that the Windows XP and QNX OS were configured to work for our aircraft applications. Disk #2 did not contain these modifications and hence was not a valid backup in case Disk #1 failed.
Solution: Use the G4U hard drive imaging program to create an image of DISK #1 in the aitken.atmos.und.edu ftp server. The image was saved in the /home/install directory which was linked to the Terastation network drive so that there was enough space for the image. The image size was ~77 GB. Since the image file was more than 2 GB, the -lfs option needed to be used when samba mounting the Terastation network drive. The removable hard drive, Disk #1, was replace with hard drive, Disk #2 and again the G4U image program was booted from the CD rom. The G4U program was used to place the new image on Disk #2. The G4U program can handle the whole disk, bit-by-bit, so the boot loader was changed, the XP OS partition was changed, and the QNX4 paritions were changed to match Disk #1.
The startup file name to save data in the M300 had the date field off by one day when the M300 software first starts. It is correct if started a second time after powering up the system.
Cause: The date was incorrect in the BIOS (hardware clock).
Solution: Booted into the BOIS configuration and changed the date. Saved changes. Don't understand why our time generator system doesn't update the hardware clock.
It seems that the power supply on the M300 is failing. While working with the M300 on Friday, the M300 system lost power 6 times. Typically, it would power back up after cycling the power switch; however, on the last power failure, it would not come back until I waited several minutes. Also, after one power failure it would take less time for the next power failure to occur. It seems that the power supply is getting to hot and failing. I've seen this problem on other computer systems and replacing the power supply fixed the problem. During these power failures, other equipment on the same aircraft circuit would continue to function. Inside the aircraft was somewhat warm on Friday but not atypical of field conditions.
Cause: Bad power supply in the M300.
Solution: The M300 was sent to SEA. SEA could not reproduce the problem in the lab even after running the M300 at higher temperatures than were presented during the field failure. The power supply was replaced by SEA and the M300 was returned and reinstalled in the aircraft. As of August 31, 2005, the M300 has flown on three flights and several ground test without any further problems.
Can not access the Kingston drive on M300
Cause: No power on the Kingston drive.
Solution: Call SEA. Augie suggested to take the box apart and check the cables on the back of the Kingston drive. Took apart the M300 and the power connect was not connected to the Kingston drive. I believe they forgot to connect the power cable at SEA since I had to remove wire ties to get a cable that would reach the Kingston drive. Plugged the cable in fixed the problem.
M300 received a time out when trying to talk to the A/D Board #2 (ID #2)
Cause: A/D Board damaged in shipping.
Solution: Call SEA. Augie suggest to run the A/D Board test programs. Run the test program can got the same results. Talked to Lyle at SEA on June 24 and we figured out that the problem was a board was not seated correctly inside the A/D box. Removed the cover and reseated the board. The board must of been jared loss due to the bad treatment of the box during shipping.
No power cable for the Serial Box
Cause: Could not find power cable in shipping box.
Solution: Called SEA and they will send a power cable.
M300 tables need work, including displaying new transducer data.