A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Soaring
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

USA PF Brick question



 
 
Thread Tools Display Modes
  #1  
Old August 12th 12, 04:00 PM posted to rec.aviation.soaring
Richard[_9_]
external usenet poster
 
Posts: 551
Default USA PF Brick question

On Sunday, August 12, 2012 7:11:09 AM UTC-7, Jim wrote:
On Saturday, August 11, 2012 9:46:39 PM UTC-4, Andy wrote: On Saturday, August 11, 2012 6:10:06 PM UTC-7, Richard wrote: Make sure the file is named FLARMcfg.txt caps/small. If the file name is case sensitive it will either be found and read, or not found and not read. My file was found and read, and at least one command was executed, so it seems all lower case is acceptable. I included this (from a FLARM example file): ################################################## ###################### # Writes a diagnostic dump (PFSSSSS.DMP) to the USB stick. Existing files with the same file name will be overwritten ################################################## ###################### $file,dump However, I can find no definition of that command in the user port specification. Does that command influence the LED behavior? GY Andy, you are correct, the case of the filename is irrelevant. In my PF the $file,dump command creates a rather lengthy text file for diagnostic information only. It's full of unintelligible stuff and you don't really need it. It may be continually accumulating data and appending it to the open file. I don't recall the final color of the LED but you could just delete the $file,dump line and see what happens to the LED. If you want to see more informative info you could use the $debug_out,fat,all,all which dumps a smaller easier to read file on your disk. One word of caution if you will be using 2 external displays: You need to enable the second serial port in the Brick with: $pflac,s,nmeaout2,61 and set the BAUD rate with: $PFLAC,S,BAUD2,5 -Jim


Jim,

I would suggest to all to be very carefull what you are changing in the cfg file. If someone takes the above advice they are setting the baud rate at 57.6 kBaud. If they do this and then because of confusion remove that sentence the baud rate will be at 57.6 until changed with another sentence. You can imagine the many calls that I can connect to my software.

I recommend that all use the config on the PowerFlarm USA web site and contact their dealer advice on changes or additions.

I realize the PowerFlarm documentation is not complete at this time and is still in development.

Richard
www.craggyaero.com
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Powerflarm Brick feedback Ramy Soaring 7 August 10th 12 01:02 AM
Measured current draw, PowerFlarm Brick Evan Ludeman[_4_] Soaring 4 July 16th 12 12:03 AM
PowerFlarm Brick - Can it send GPS sentences to SN10B? WaltWX[_2_] Soaring 11 June 17th 12 05:33 PM
PowerFLARM 'brick' progress? Frank Paynter[_2_] Soaring 5 November 13th 11 07:28 PM
Display for PowerFLARM brick Andy[_1_] Soaring 4 May 10th 11 02:32 PM


All times are GMT +1. The time now is 03:30 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 AviationBanter.
The comments are property of their posters.