I'm guessing Davide is already doing this, as of course it is always a good idea for analog inputs! (digital inputs too actually) "floating" is not great.
In my tests I'm using two sensors and grounding all the other inputs.
.b.
Martin Peach wrote:
B. Bogart wrote:
Hi David,
I'll try and test this today, would it work if I connected the same sensor to all the analog ins? I don't have enough space on my board for 8 voltage dividers!
You could ground all the inputs except the one you want to test. Not sure about the arduino but often floating analog inputs will read the same as adjacent connected inputs because the charge is just sitting on the pins with nowhere to go.
Martin
.b.
Davide Morelli wrote:
Which version are you using? There was some bugs in the past, for sure. I think I got the analogs in, digital outs, and digital ins all working now. The latest version broke the hardware PWM control, but we are also adding software PWM support. Try the latest versions in CVS: externals/hardware/arduino.
I did "cvs update" on 28th August, right before compiling.
Have you tried the firmware with more than 3 analog inputs?
if yes then I'll try your firmware again, maybe i messed something up...
As for adding the pin number, I think its redundant, you can just use a header byte (255) then byte order to determine pin #, and that will save you 5 bytes per cycle (12 bytes versus 7 bytes). Part of the goal of the Pduino firmware is to make is communicate as fast as possible so that people can make usable instruments with it, and make snappy interactions. There are a number of strange things in the firmware the arise because of this.
yes, you're right, the pin number is redundant, I used it just to debug. I didn't meant that you should use it in Pduino, it was just an example of working firmware..
ciao, davide.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list