Here is a black box diagram of the hookup.
Any sources for internal logic diagrams, conventions?
Do I use a decision tree, or some other format?
How do you indicate PWM-adding, multiplexing multiple inputs- as for V-tail, or Elevons?
The Pwm input can be represented as a value on as scale of 1 to 100, I suppose?
question: why does this post show in grey? - is this to do with moderation.
The next stage is to diagrammatically represent the Nano app, I think.
I am familiar with decision trees, but never used them in my work.
Do they have an application here?
I would divide the app into logic blocks and functional blocks.
- PWM converters, current loop setup and monitor, calibration tables, storage.
Then I can go looking for existing code blocks that do the required jobs.
I saw a nice app suite that did quads, helicopters etc, and had a desktop graphical interface.
I am not likely to find something that detailed for this app.
In the meantime, I will watch a few You tube videos on learning the Arduino system.
as well as a Helicopter example.
