You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then I changed order in the adc.read sequence.
Channel order: 12, 13, 0, 1
Output: [2035, 1962, 930, 1499] (same output ordering as before)
Expected behaviour by me was that read_buffer indexes would match sequence order, since I don't really know the channel order. I.e read_buffer[2] would give channel 0 data in the last example.
The text was updated successfully, but these errors were encountered:
I ran into an issue with ADC data being wrong. It turned out to be due to not understanding how the data is read.
I added a print in the read method to show the sequence channel ordering.
Example code:
Issue summarized:
Channel order: 0, 1, 12, 13
Output: [2035, 1962, 930, 1499]
Then I changed order in the adc.read sequence.
Channel order: 12, 13, 0, 1
Output: [2035, 1962, 930, 1499] (same output ordering as before)
Expected behaviour by me was that read_buffer indexes would match sequence order, since I don't really know the channel order. I.e read_buffer[2] would give channel 0 data in the last example.
The text was updated successfully, but these errors were encountered: