JKos Elite Veteran Location: City of California in the state of Maryland
| Wolfgang,
> Pulse width IS time. You're plotting time against time ?
Yes, that is correct. Each pulse out of the receiver has a certain length (time) and occurs at a certain time (time). Thus, the new plots will show not only the pulse width for each pulse, but exactly when they occur.
> The nature of the system will never allow channels to update
> simultaneously since data is sent sequentially.
That is incorrect. Both Futaba PCM formats (PCM1024 and G3) and Airtronics PCM have simultaneous pulse outputs for various groups of channels. JR PCM rx outputs are sequential, but the data coming into the rx is certainly not sequential in nature.
> The above does not necessarily apply to pcm.
Almost all of these tests are with PCM. Those which are FM are labeled as such. PCM is of the most concern for this issue.
> see some strange pulse coincidences on the three trace plots where
> channels 1 and 2 have coincident pulses and channel 6 is down the
> line somewhere. My question is why are 1 and 2 coincident?
Because that is how the receiver is sending them out.
> The other graphs you show with pulse width versus frames are
> showing exactly what?
They show how the transmitter is updating the pulse widths on a frame-by-frame basis. The corresponding pulses may or may not come out of the receiver at the same time, but they are being sent within the same frame.
> Is that data the outputs from the RX?
Yes, all data presented here are from the receivers' servo channel outputs.
> If so, where are the stick inputs?
This is not a latency test and thus the "stick" input is not shown. The stick input is a fast collective change. The latency tests capture stick-to-receiver output timing.
> which of these test are done using e-CCPM
All of them.
> I would expect the dedicated channel operation has the least
> problems of latency and slew.
Yes, that is correct. These issues are not a problem for non-eCCPM machines since no interaction is created by individual channel behaviors. Latency is still an issue on non-eCCPM machines as it does directly effect the connection between the pilot and the machine.
A collective change was chosen for these tests since that is what seems to cause the most swashplate "dancing" issues.
Captain Chaos,
> I assume this is all done in eCCPM, hence the thread title.
Bingo!
- John |