For some reason the 47 pF value for the caps is sitting in my mind. Either after 'calibration' the LC meter is so far off that it read both my TI-89's and my V200's caps 51 pf, both ~8% high, or both of them are within their 10% tolerance and reading...
I made a 5V, 5W buck derivative that is smaller than the flybuck design but uses the same input/output filter design for low noise/ripple applications. The inductor core is a Magnetics MPP C055048A2. with 38 turns of 24 AWG. Peak efficiency with...
Requirements Easily found when misplacedBig enough to hold easily but not too big that it's cumbersomeShould have a battery compartment so that unskilled personnel can replace batteries without having to open up the housingRoom enough for the necessary...
I did another test with the rev1 prototype, this time only measuring voltage, and bringing it all the way to the maximum voltage of 60V. Again I am doing calibration and comparison to my Fluke 101 Multimeter. This has a problem as the Fluke 101 does...
Looking at the registers I noticed something. the first 24 bytes look like they have data and the last 6 bytes look like they have data. This looks like what a WII peripheral in encrypted mode would look like. The fixed 8 byte pattern repeating every...
On my TI-89, one of the battery contacts on the PCB was heavily corroded and it took a good deal of time and heat to reflow solder to make a new pad. I did this to the V200 as a preventative measure too, but I guess I heated up the nearby fuse to where...
Improving mocks I have decided to use Rust for mocking libcmfwk and libshmem_manager, as it is the language I am most comfortable with. By creating accurate mocks for these libraries, I aim to resolve the issue where camctld hangs while trying to send...
Wrote a very basic command interface with three commands:W - Write the EEPROMR - Read the EEPROMB - Bounce an LED across the RPP-UIO-16 cardThe result looks like this:Write to the EEPROM Read from the EEPROM 0000 00 01 02 03 04 05 06 07 08 09 0a 0b 0c...
Let's go back to logs 139. Heuristic breakthrough and 140. gPEAC to 1 million. Now that the gPEAC inner loop is optimised, it's time to build the distributed scanner to hack through a mountain of numbers... It should be faster with the optimised...
OK I thought that the amount of data in the future would be too large and I decided to do the sieving in C. Using the available scanning data, I could only go up to 2161 : n1=46 and n2=2114.The first hicup comes at 1511 so there is no point in dealing...
With the new harvest, I estimate that the perfect and maximal orbits under m=1M is around 100K. This starts to make quite a large .h file to include in the sieve generator. Not that it's such a concern but scalability, you know.... And embedding such...
So, the results are different than expected, but that is just fine. I'm running my V200 at 2x the speed it came from TI. For those who are TL:DR with my logs, you need a 1.21 kOhm resistor and an 18 pF capacitor. I never ran the MD5 checksums as I didn't...
[This post brings me up to date with the work I've done so far, and corresponds to the state in commit 0e4b928083ae69bb6ae577197ac016e93a77e80e] I've documented my design for the NEXT routines, which I've committed to Github here. It's a little sketchy,...