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