Hi Scott, tnx considering it. I tryed with the OT1plus source code to change the telemetry packet myself to an wetaher packet, but I am not so good in C++ and got stuck in the "send_packet" function somewhere when programms calls for the config array. However I would think that the standard OT-firmware (main.c, weather_main.c) provides already most of the necessary functions: read_adc send telemetry send packet We "just" need to build a weather_packet" instead of an "telemetry packet" and probably do some conversion for the values read from the adc's. Sounds easy- I know... but could not do it myself...-hi
vy 73 de Mike oe3mzc ----- Original Message ----- From: Scott Miller To: [email protected] Sent: Wednesday, September 09, 2009 6:55 AM Subject: Re: [tracker2] Re: OT2 telemetry This is another thing I want to try with the weather station eventually. It'd require the ability to load coefficients for the transfer function for each sensor. Again, I'll probably try it first in the WS1 and back-port it to the T2 if it works and if there's room. Scott Mike Zwingl oe3mzc wrote: > > > Scott, > please also consider to include a possibility to use the ADC values of > OT1plus and/or OT2m for transmitting weather data, > in absence of a serial 1-wire weather station. > It would be perfect to be able to assign temperature, pressure, wind > direction, humidity to some ADC inputs > and rain gauge and/or wind speed to the counter input. > > This would also be very helpful for many "balloon" telemetry applications. > tnx considering. > > vy 73 de Mike > > > > > ----- Original Message ----- > *From:* Scott Miller <mailto:[email protected]> > *To:* [email protected] <mailto:[email protected]> > *Sent:* Thursday, September 03, 2009 5:35 AM > *Subject:* Re: [tracker2] Re: OT2 telemetry > > > > Maybe. The OT1+ does that with temperature and voltage. I'll take a > look at that when I figure out how I want to do the custom telemetry > strings. > > I'll probably hold off on that until I get some work done on the WS1 > weather station. I'm doing some flexible sensor setup that might serve > as a good model for the T2 when I get it ironed out. > > Scott > > James Ewen wrote: > > > > > > On Wed, Sep 2, 2009 at 4:53 PM, Scott Miller<[email protected] > <mailto:scott%40opentrac.org> > > <mailto:scott%40opentrac.org>> wrote: > > > > >> I don't believe that there's any way to access the adc values > in the > > >> script engine, but it would be nice to be able to do that. I'd > like to > > > > > > Not yet, it'll take some testing because reading ADC values > introduces a > > > bit of a pause while it waits for the conversion to complete. > > > > Is there room in the RAM to store the ADC values so they don't > have to > > be read by the script engine? The script engine runs 8 times a second > > or so, if I recall... I don't know if you need to sample the ADC > > values that often. For some applications, that might be > necessary, but > > not for mine currently. Once a second would be good for watching the > > GPS altitude so that the OT2 can record max altitude, and report that > > value once descent has been confirmed. > > > > >> Sheesh, that sounds like a lot of cases of Coke and Twinkies! > > > > > > I have a forklift now, so that's OK. I prefer Coke Zero and the > Hostess > > > chocolate cupcakes. > > > > Aha, that's what the forklift was for... I thought it was for > > offloading containers full of parts! > > > > James > > VE6SRV > > > > > >
