Member Since: January 27, 2009

Country: United States

  • Still have this horrible thing: I made a 4K static memory board for my ZX-81 with it. It worked for a year or then started glitching out. Typical of the technology.

  • Has anyone tested these with older Pis with a 26 pin header? From the pinout ( it looks like the SDA and SCL pins are duplicated on 27 and 28 (Or does it need a second !2C? But it doesn't show those pins used on the zero) and you would only lose the on board button pins. You'd probably need to mod the driver if it threw errors looking for pins 27 - 40.

  • Does it still have a 26 pin connector, so it will work with older pi's?

  • Does this unit have enough bandwidth to transmit the 202 AFSK clearly? I used to have a Byonics Microtrak that used an earlier version of the HX-1 and the 2200 hz tone was down about 12db compared to the 1200 hz tone. This limited the range to only a few hundred meters, much more than the low output power would suggest. An audio spectrum screen shot of the transmitted audio would be helpful.

  • Does the v2 camera work with old pi’s? I have some really old original B versions (cpuinfo 0x000e.) a list would be helpful in the product description.

  • - $145 is a lot for a nixie tube - but check out the size: 50mm digits in a 125mm package. That's a big tube! Looks like he has a 6 month order backlog.....

  • To get measurable results with this ting, you'd have to take a long transoceanic airplane flight. and you'd need a stationary atomic clock to compare to.

    There used to be an app called "Einstein's Pedometer" that would calculate this. For a normal subway ride the effect was good for a few ten thousandths of a nanosecond.

  • To compare with a typical application, a single uncompressed NMEA sentence is going to be about 50 chars or 1 "credit" (or 1/2 kilobyte) so that's $0.15 and up for 1 position report.

  • [SOLVED] I also found that my older RC-171 module would not associate. After trying innumerable variations of RN-171 settings, I found that the Linksys had a non-default setting for "Basic Rate"; it was set to "Auto". When I set the Basic Rate to "Default" both RN-171's would join. With the Linksys set to Basic Rate = "Auto" the RN-171 would only join with the Linksys get to "B-only" Mode. So this problem is obviously specific to the WRT54G2 but may apply to older Wifi routers as well.

    There is still the issue that the "set wlan join" parameters don't match the documentation but it looks like the RN-171 will connect to a b/g WPA2 network just fine in either WPA2 or "Mixed" setting.

  • Is firmware 4.00.1 FUBAR? I have two of the RN-171's, one running 4.00.1 and one running 2.32. The 2.32 one will associate without any problems with my venerable WRT54G2 but the 4.00.1 cannot.

    One thing I notice is that the SET WLAN AUTH settings in 4.00.1 are not as documented:

    <4.00> set wlan auth 4
    <4.00> get wlan
    … Auth=MIXED     <- supposed to be WPA-PSK2
    4.00> set wlan auth 3
    <4.00> get wlan
    ...Auth=WPA1       <- Supposed to be "Mixed WPA1 and WPA2-PSK"
    <4.00> set wlan auth 2
    <4.00> get wlan
    … Auth=WPA2       <-- supposed to be WPA1

    No matter what I set wlan auth to, it tries MIXED mode:

    Auto-Assoc CHUM BUCKET chan=4 mode=MIXED SCAN OK
    Joining CHUM BUCKET now..
    Disconn from CHUM BUCKET,AUTH-ERR

    Anybody gotten the new firmware to work with older WPA2 APs? By MIXED, do they mean TKIP+AES auth? I have tried setting the Linksys AP to "AES" vs "TKIP+AES" and no change in behavior.

    The older version RN171 has not trouble associating, I use "set wlan auth 4" on it and it correctly shows WPA2 in get wlan output.