|
Jack Purdum
All:
I think Chuck Adams has the right approach to this. His video series on YouTube for building W8DIZ's 1 Watter () has a lot of good stuff about kit building in general. However, his approach addresses the subject line here: How do you diagnose problems with a homebrew or kit project. If you are going to use the ?C as part of the process, it would be much more successful if the diagnoses are done at stages along the way, rather than deferring until the project is done. It's much easier to diagnose a stage as it is built rather than waiting to a point where several stages can interact and be causing issues. This suggests building the PS first, checking the voltages, etc. and pronouncing it "healthy". I would immediately then constuct the ?C section, utilizing the the Serial object to verify it is working (e.g., the simple Blink program). Then (and you EE guys are better at deciding what's next) perhaps build the audio section and have program code that sends a 700Hz tone to the amplifier for replay through the headphones/speaker. If you get to a section where the test from the ?C doesn't pass its test, you have limited the source of the error to the most recent section. It's the same concept as Encapsulation in software engineering. My point is: If you're going to the trouble of building diagnostic software into the rig, utilize it through the entire construction process...don't defer it to the end. Not only does the approach enhance the odds of a working piece of equipment when the project is done, it builds confidence in the builder along the way--a double win! Jack, W8TEE
On Friday, April 27, 2018, 8:35:43 PM EDT, Howard Fidel <sonic1@...> wrote:
Great idea. If the Arduino only had
more inputs we could do a really thorough job with some mods.
On 4/27/2018 8:09 PM, John wrote: I have started developing a diagnostic software for the uBitx.?
|
