Flarmview and Powerflarm Core Config File?

I'm helping KS update his Powerflarm - firmware update to core and updated config files using the Config Tool from the Flarm Website. The update to the Powerflarm worked (solid green color), but the communication to the Flarmview stopped working.

I poked around and found the baudrate setting on the Flarmview is 38400 while the default setting on the config tool is 19400. Just for gits and shiggles I went into the manual settings using the config tool, updated the RJ connection to 38400, and it works.

So, before I claim victory, is there anything else that needs to be done to the "default" Flarm Config to make it work with a Flarmview. I did RTFM on the Flarmview, and it is pretty vague on what the communications protocol settings need to be...

P3

"Rainy days at a contest...."

You can look at a current (yesterday?) IGC log from the ship, it will have all the settings from the old config so you can compare to the new one. It was recently discussed here about "how to pull my old config before the update".

On Sunday, May 17, 2015 at 12:22:19 PM UTC-4, Charlie M. (UH & 002 owner/pilot) wrote:
"Rainy days at a contest...."

You can look at a current (yesterday?) IGC log from the ship, it will have all the settings from the old config so you can compare to the new one. It was recently discussed here about "how to pull my old config before the update".

Yeah but... it looks like there is a new option for Communications Protocol that wasn't there before. At least that's what it looks like when you use the online Configuration Tool. I could be wrong.

What I use:

################################################## ######################
# dataport configuration
################################################## ######################

# configure RJ-45 port for FlarmView 57
$PFLAC,S,NMEAOUT1,61
$PFLAC,S,BAUD1,5

################################################## ######################

and set (on flarmview) data rate to 57,600 baud.

It's not really necessary to set the mode -- I asked Uros about this and he says it is non-critical (so flarmview probably issues it's own mode setting command on the dataport). What *is* critical, as you have discovered is that the datarate set in flarmcfg.txt and on flarmview (in settings on flarmview) match.

Have fun at Mifflin.

-T8

Hi,

I don't recommend using the default settings. They are not ideal. I have
some tips for how to set the parameters in my PowerFLARM Tips document he
http://www.cumulus-soaring.com/flarm...FLARM-Tips.pdf

Best Regards,

Paul Remde
Cumulus Soaring, Inc.
___________________________________

"Papa3" wrote in message
...

I'm helping KS update his Powerflarm - firmware update to core and updated
config files using the Config Tool from the Flarm Website. The update to
the Powerflarm worked (solid green color), but the communication to the
Flarmview stopped working.

I poked around and found the baudrate setting on the Flarmview is 38400
while the default setting on the config tool is 19400. Just for gits and
shiggles I went into the manual settings using the config tool, updated the
RJ connection to 38400, and it works.

So, before I claim victory, is there anything else that needs to be done to
the "default" Flarm Config to make it work with a Flarmview. I did RTFM on
the Flarmview, and it is pretty vague on what the communications protocol
settings need to be...

P3