X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from [65.54.250.76] (HELO hotmail.com) by logan.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 1073685 for flyrotary@lancaironline.net; Wed, 19 Apr 2006 19:38:07 -0400 Received-SPF: pass receiver=logan.com; client-ip=65.54.250.76; envelope-from=lors01@msn.com Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 19 Apr 2006 16:37:22 -0700 Message-ID: Received: from 4.171.174.58 by BAY115-DAV4.phx.gbl with DAV; Wed, 19 Apr 2006 23:37:18 +0000 X-Originating-IP: [4.171.174.58] X-Originating-Email: [lors01@msn.com] X-Sender: lors01@msn.com From: "Tracy Crook" To: "Rotary motors in aircraft" References: Subject: Re: [FlyRotary] Re: Possible data-logging solution? Date: Wed, 19 Apr 2006 19:36:19 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A5_01C663E8.88462A20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: MSN 9 X-MimeOLE: Produced By MSN MimeOLE V9.20.0026.0800 Seal-Send-Time: Wed, 19 Apr 2006 19:36:19 -0400 X-OriginalArrivalTime: 19 Apr 2006 23:37:22.0632 (UTC) FILETIME=[34E21480:01C6640A] This is a multi-part message in MIME format. ------=_NextPart_000_00A5_01C663E8.88462A20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MessageThanks Tim, =20 Joe Hull is a pretty good programmer and said he would take a look at it = but don't have any commitments at this point. Any and all help would be = appreciated on either part of this project. I'm simply out of time to = do it all myself. Any contributor will get full credit for their = efforts and if this stuff ever makes any profit, I'll count you in for = royalties! (hint, it won't be like winning the Power Ball Lotto : ) For anyone interested, Boring technical details of the task follow = below: All others may delete message now. =20 Data logger protocol This protocol is still being worked out so if you have any suggestions = to make it easier of more reliable, fire away. =20 The first part needed is a PC Program to input a stream of data words on = a serial port from the data logger and store them as a disk file. The = words will represent multiple blocks of 28 14 bit values. Each 14 bit = word in the block is one of the 28 data channels in the EM2 engine = monitor. There is one 28 word block for each 2 second sample period. = Definition and order of data words still being developed. The serial data file stream is preceded by a file start marker byte of = $F9. The data words are then sent as two bytes having the msb (bit 7) = cleared and the lower 7 bits holding the data. The least significant 7 = bits of the 14 bit word are sent first. At the end of each 28 word data = block there will be an end of block marker of $FA.=20 The end of the data file will be signified by an end of file marker byte = of $FF. =20 The async serial data will come from the data logger at a baud-rate of = 19,200. Currently there are no flow control lines (CTS / RTS) on this = serial interface but these could be added if necessary. =20 The second half will be an EXCEL spreadsheet that displays the data file = as 28 channels in chart form with time being the X axis (2 seconds per = data block) and the value of each channel plotted on the Y axis. Don't = know if it is practical to display all 28 channels on one chart (would = be nice, in order to see unexpected correlations) or to have separate = charts for various groups. Each channel will be associated with a different formula to convert the = raw sensor data word to human readable units (degrees F, PSI, etc.) = These formulas are already developed. I have only a little EXCEL experience so I don't know if I'm expecting = too much from it or not. Your input welcome here. Tracy Tracy, If you don't have any volunteers by now, get me the details and I'll = take a look at it. =20 -Tim ----- Original Message -----=20 From: Tracy Crook=20 To: Rotary motors in aircraft=20 Sent: Monday, April 17, 2006 10:14 AM Subject: [FlyRotary] Re: Possible data-logging solution? I'll check this out but in the mean time I added a simple data = logger to the fly-by-wire board since it only required the addition of 1 = inexpensive part. Data logging time is limited to 74 minutes at a = sample rate of once every 2 seconds. This should be plenty for = analyzing cooling & performance issues. It ain't over yet since this only stores the raw sensor data. As = Rusty points out, I (or a volunteer with some programming/EXCEL chops?) = need to write the program to download the data and an EXCEL spreadsheet = to display it in a nice chart. BTW, Congrats Buly! Now, give us more details on that needed = cooling tune-up : ) Tracy (did I mention I was looking for volunteer programmers?) Subject: [FlyRotary] Re: Possible data-logging solution? Tracy: Could this module be added to the EM2 or EC2 to add = datalogging in a simple manner? = http://www.labjack.com/labjack_u3.html=20 Interesting Phil. I just bought a serial data logger for my Dynon = DS180 (EFIS and EMS). I just received the Dynon, and data logger, so I = haven't had time to try anything with them, but this setup has promise = for Tracy's stuff as well. =20 = http://www.zen30649.zen.co.uk/product_antilog.html At the moment, the unit only logs one of the two serial channels, = but in the next version of software, it will log both channels. It uses = SD or MMC memory cards, so you can take them home to read them. The OEM = version has this card slot available on the bottom of the board, where = the boxed version is enclosed. I'm told you can use any branded memory, = so you don't have to buy theirs. I got the 128 mb version, since they = seem to screw you on the memory cost, and I can buy larger cards much = cheaper from other vendors. =20 They don't use the FAT file system, so you need their "reader" = program to read the memory card on a PC, or you can use a laptop and = download the data via X-modem. Once I get the data, the next problem = will be figuring out what to do with it. I guess I'll be learning more = about Excel than I cared to know. =20 Cheers, Rusty (one week until my "sentence" in Cleveland starts) ------=_NextPart_000_00A5_01C663E8.88462A20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
Thanks Tim, 
Joe Hull is a pretty good programmer and said he would take a look = at it=20 but don't have any commitments at this point.  Any and all help = would be=20 appreciated on either part of this project.  I'm simply out of time = to do=20 it all myself.  Any contributor will get full credit for their = efforts and=20 if this stuff ever makes any profit, I'll count you in for = royalties! =20 (hint, it won't be like winning the Power Ball Lotto : )
 
For anyone interested, Boring technical details of the task follow=20 below:  All others may delete message now. 
 
 Data logger protocol
 
This protocol is still being worked out so if you have any = suggestions to=20 make it easier of more reliable, fire away.   
 
The first part needed is a PC Program to input a stream=20 of data words on a serial port from the data = logger and=20 store them as a disk file.  The words will represent multiple = blocks of 28=20 14 bit values.    Each 14 bit word in the block = is one of=20 the 28 data channels in the EM2 engine monitor.  There is one = 28 word=20 block for each 2 second sample period.  Definition and order of = data words=20 still being developed.
 
The serial data file stream is preceded by a = file start=20 marker byte of $F9.  The data words are then sent as two = bytes having=20 the msb (bit 7) cleared and the lower 7 bits holding the data.  The = least=20 significant 7 bits of the 14 bit word are sent first.  At the end = of each=20 28 word data block there will be an end of block marker of = $FA. 
 
The end of the data file will be signified by an end of = file=20 marker byte of $FF. 
 
The async serial data will come from the data logger at a baud-rate = of=20 19,200.   Currently there are no flow control lines (CTS / = RTS) on=20 this serial interface but these could be added if necessary.  =
 
The second half will be an EXCEL spreadsheet that displays the data = file as=20 28 channels in chart form with time being the X axis (2 seconds per data = block)=20 and the value of each channel plotted on the Y axis.   Don't = know if=20 it is practical to display all 28 channels on one chart (would be nice, =  in=20 order to see unexpected correlations) or to have separate charts=20 for various groups.
 
Each channel will be associated with a different formula to convert = the raw=20 sensor data word to human readable units (degrees F, PSI, = etc.)  =20 These formulas are already developed.
 
I have only a little EXCEL experience so I don't know if = I'm expecting=20 too much from it or not.  Your input welcome here.
 
Tracy

Tracy,
 
If you don't have any volunteers by now, get = me the=20 details and I'll take a look at it. 
 
-Tim
 
----- Original Message -----
From:=20 Tracy Crook=20
To: Rotary motors in = aircraft=20
Sent: Monday, April 17, 2006 = 10:14=20 AM
Subject: [FlyRotary] Re: = Possible=20 data-logging solution?

I'll check this out but in the mean time I added a simple = data=20 logger to the fly-by-wire board since it only required the addition = of 1=20 inexpensive part.   Data logging time is limited to 74 = minutes at=20 a sample rate of once every 2 seconds.   This should = be=20 plenty for analyzing cooling & performance issues.
 
It ain't over yet since this only stores the raw sensor = data.  As Rusty points out, I (or a volunteer with some=20 programming/EXCEL chops?) need to write the program to download the = data and=20 an EXCEL spreadsheet to display it in a nice = chart.
 
BTW,  Congrats Buly!  Now, give us more = details on=20 that needed cooling tune-up : )
 
Tracy  (did I mention I was looking for volunteer=20 programmers?)
 
 
Subject: [FlyRotary] Re: Possible data-logging = solution?

Tracy:   Could this = module be=20 added to the EM2 or EC2 to add datalogging in a simple = manner?

http://www.labjack.com/la= bjack_u3.html 
 
Interesting=20 Phil.  I just bought a serial data logger for my Dynon DS180 = (EFIS=20 and EMS).  I just received the Dynon, and data logger, = so I=20 haven't had time to try anything with them, but this setup = has=20 promise for Tracy's stuff as=20 well.  
 
http://www.ze= n30649.zen.co.uk/product_antilog.html
 
At the = moment, the=20 unit only logs one of the two serial channels, but in = the next=20 version of software, it will log both channels.  It uses = SD or=20 MMC memory cards, so you can take them home to read them.  = The OEM=20 version has this card slot available on the bottom of = the board,=20 where the boxed version is enclosed.  I'm told you can use = any=20 branded memory, so you don't have to buy theirs.  I got the = 128 mb=20 version, since they seem to screw you on the = memory cost, and I=20 can buy larger cards much cheaper from other=20 vendors.  
 
They = don't use the FAT=20 file system, so you need their "reader" program to read the memory = card on=20 a PC, or you can use a laptop and download the data via=20 X-modem.  Once I get the data, the next problem will be = figuring out=20 what to do with it.  I guess I'll be learning more about = Excel than I=20 cared to know. 
 
Cheers,
Rusty = (one week until=20 my "sentence" in Cleveland starts)
 
  
------=_NextPart_000_00A5_01C663E8.88462A20--