New Renard Diagnostic Firmware - testing help requested

[RavingLunatic]

EDIT: Idea scrapped

[dirknerkle]

I like what you're trying to do, and I think it has solid merit. I'm printing the PDF as I write this, but thought I'd share my immediate concern.

It seems to me that a significant share of DIY problems come from simple (or sometimes not so simple) cabling issues, bad or nonexistent physical connections, erroneous PC configurations, the inability of the user to recompile PIC code and/or flash the PICs properly, or simply poor construction technique. I really like the idea of diagnostic code, but I wonder what sort of support issues will arise from supporting the diagnostic tool itself?

[IdunBenhad]

Hi:
Am I missing something? I'm able to read the PDF ok, but can't get a download of the ASM or HEX files.

Not knowing too much about the PIC code, I'm curious if there might be a way to flash a PIC and control it from the computer and still be able to run these diagnostic tests. Just being able to control the diagnostics from the computer would prove part of the communication testing.

Having to flash a PIC for each of the tests could get a little tedious unless one had a bunch of PICs on hand.

Other than that, I like the idea of the numerous tests. In this case, more is better.

Edit: Forget the ASM/HEX download thing, I found 'em. My iMac hid them on me.

[DIY Guy]

On the other hand, I had a bad oscillator and the diagnostic firmware pinpointed the problem in only a few minutes.

I don't think 'diagnostic firmware' should be equated with resolving all problems, nor with something every user will be able to do.

Just like soldering et al, new users will have to learn how to implement the diagnostic firmware.

I am happy to see any additions, given how invaluable the existing diag firmware has been.

[RavingLunatic]

Not knowing too much about the PIC code, I'm curious if there might be a way to flash a PIC and control it from the computer and still be able to run these diagnostic tests. Just being able to control the diagnostics from the computer would prove part of the communication testing.


I've been mulling this over a lot lately and while it would be possible, I keep coming back to a single fact that makes it relatively pointless.

The fact is: If you have communications to be able to command those tests then you have communications to be able to do all the same functions as the new tests via VIXEN (at least with this diag code that passes on data).

The new tests are designed more for helping someone who isn't convinced that the problem is with the board or with their interconnection or VIXEN setup.

I don't see too many experienced members needing these tests but a newbie who isn't too sure with what they are doing might have a use for them. That is why they won't be defaulted to run all the time. The new ability to turn the extra diagnostics off/on I believe gives users a lot more flexibility in what they want to do. It just means that newbies will have to "suck it up" and buy a PIC programmer (like most of us preach) and not rely on getting them programmed by others.