Quote:
Originally Posted by philso
Why do you feel that directly interfacing with the PWM signals is necessary? It is much, much easier (and safer) to manipulate the PWM signals in software as Greg suggests. Much more can be done in software than can be done in hardware. Some teams use co-processors, as Micheal indicates. It would be difficult to find a co-processor with enough horsepower and speed to put in the path of the PWM signals that would not compromise the PWM signals in some way. There are other ways you can apply your creativity without endangering yourself and others.
By directly manipulating the PWM signals, you will be adding complexity to a safety critical system. That complexity can lead to an unsafe condition if not tested very, very thoroughly. This is likely why FIRST wants to see a company as a vendor. It is also likely that they will want to review the company's policies regarding making and documenting design changes. Otherwise a system that was deemed to be safe can become unsafe.
|
This is all theoretical -- I have no intention of actually doing so. It would just be nice to get an idea of how this could work and what potential it could unlock. The MXP is often referred to as a custom electronics board, and I wanted to see just how custom you could get. I'm aware it's a safety concern, but I'm trying to find out what is theoretically possible, and on that line, what is considered dangerous and unsafe.