<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">It sounds like a good idea, but there'd have to be some standardization. Maybe it would gain in popularity to the point where they'd ship precalibrated but I doubt it because of the time involved.<br><br>Of course different dongle types would have different addresses free, so you'd have to make up a table that had a pointer to the ppm data for each dongle type, and stick to it. If Microsoft ever gets into the game they'll insist on redefining everything. You could key the locations to the USB numbers.<br><br>While you're at it it would be nice to use maybe at least a 16 bit value if possible. I had mine all worked out to about 5 or 6 places then found I could only store what might be an 8 bit integer. SDR Sharp would only store mine as 102 instead of about 102.4567. Since the correction
is done in software there shouldn't be a limit on the size (data type) of the number.<br><br> Alan<br><div><span><br></span></div><div>-----<br>Radio Astronomy - the ultimate DX<br><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Benedikt Heinz <zn000h@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> osmocom-sdr@lists.osmocom.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Saturday, March 16, 2013 4:27 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> [rtl-sdr] store frequency correction in eeprom?<br> </font> </div> <br>
Some of you are probably using multiple dongles with alternating<br>applications as well.<br>Regarding the frequency correction, I put a sticker on each dongle and<br>wrote the ppm value on it.<br>However manually setting the value in each application is still annoying.<br>So I used rtl_eeprom to write the value into the product-ID with the<br>following format: "RTL%+dppm" resulting in sth. like this: RTL+87ppm<br>I'm not sure if this is the best way to do it, but this approach works<br>without changing librtlsdr.<br>Another option might be storing the value in a non-used eeprom<br>location and adding get/set functions to librtlsdr.<br>Is it possible to write arbitrary values to unused eeprom locations<br>without fucking up the realtek eeprom handling? Do you think this<br>would be a better way?<br><br>I'd like to hear your comments on this.<br>It would be awesome if we could find a solution that many existing<br>applications could
incorporate.<br><br>(Of course the ppm value still changes with temperature, but having a<br>base value is still closer to the truth than 0ppm I'd say.<br>I measured the offset directly after grabbing samples for 20 minutes<br>at room-temperature and jitter is <1ppm.)<br><br>Best regards,<br><br>Hunz<br><br><br><br> </div> </div> </blockquote></div> </div></body></html>