So my initial testing of an ESP-12E showed that it couldn’t reliably keep up with two 10K PPR encoders (40K count). I discussed this project a great deal with my fellow astronomers on CloudyNights. After doing a lot more research and testing I’ve determined that the ESP8266 even when running at 160Mhz just can’t keep up with two 10K PPR encoders. Continue reading
So yesterday I was all happy that I got my prototype ESP-DSC working. This ended up being short lived as I realized this morning that while it does technically work, the ESP8266 can’t keep up with two medium resolution (2,500 CPR) encoders.
Ironically, I found out that the code was too slow when I started to optimize the code and I realized that the code I has was very very conservative. My original optimization was to speed it up, but maintain that conservative ethos. I figured while I was editing the code, I might as well also add a test to see if the ESP-12F was dropping interrupts… Continue reading
Spent most of my post-St. Patricks day writing code for the ESP-DSC. The big question was always does the ESP-12E have enough horsepower to handle both the encoders as well as doing all the WiFi/communications. So far, I’ve bench tested a pair of 2.5k CPR encoders which translate into 10K encoders after quadrature decoding. Continue reading
So a few years ago, I announced TeensyDSC, project that brings telescope digital setting circles to the iPad and Android devices using WiFi. I’ve been using my TeensyDSC successfully with my telescope and SkySafari on an iPad for a few years, but one thing always bothered me about it: the “COGS” (cost of goods sold) of the TeensyDSC was really expensive: nearly $100. A lot of that cost was in two parts: the Teensy 3.1 ($20) and RN-XV WiFi module ($35).
So I’ve been using EaglePCB for a number of years. I’ve designed and created some open source projects like my SV650 ECU Decoder and TeensyDSC. While I had a cheap ($79) commercial license for a one off commercial project I did, most of my work was done using the $169 “Maker” version for non-commercial use.
Then mid-2016, Eagle was bought by AutoDesk. I’ve only used one AutoDesk product before: Fusion360 which I really like. Sure, it’s not as good as SolidWorks, but I’ve designed parts for both CNC and 3D printing and they’ve come out great. And to top it off, AutoDesk is very gracious in it’s licensing terms- allowing makers like me to use it for free.
So spent a bunch of the time in the garage this weekend working on reverse engineering the SDS protocol on the SV650. SDS is basically ISO9141 aka K-Line which something you often see in a car’s ODB-II port. Unfortunately, SDS is just different enough that you can’t use any commercial off the shelf ODB-II reader to read the messages. The way I have been going about this was pretty painful and taking a lot of time/effort to iterate over so I came up with a new tool chain.
As racers, we’re always looking for an advantage over the competition- better brakes, exhaust, motor work, titanium bolts to reduce unsprung weight- you name it. With the advent of modern electronics, now data logging and analysis is becoming available for not just pro-racers, but club racers as well.
Most data loggers talk about how awesome their hardware is… see how sleek and sexy it looks? It has all kinds of features like GPS and accelerometers which are sampling at many times a second. Just imagine how much data you’ll collect! So then you install the data logger on your bike and you can’t wait until you can go out on track and try it out. Everything is great! Until…