grey

Hi chris, thank you for your quick response.
 
The effect arises only when i "read()" an adjacent pin.
All the other digital pins are not in use. The other (not in use) analog pins are connected to ground (see the picture before).
 
There is no hardware bug from my side. I checked all sensors with an oszilloscope and everthings works as it should.
 
I think these guys has the same problem:
http://forums.netdui...-tied-together/
http://forums.netdui...tage-incorrect/
http://forums.netdui...mpare-to-a1-a2/
 
this is my code

Microsoft.SPOT.Hardware.AnalogInput analogInputTemp = new Microsoft.SPOT.Hardware.AnalogInput(Cpu.AnalogChannel.ANALOG_5);
            Microsoft.SPOT.Hardware.AnalogInput analogInputPoti = new Microsoft.SPOT.Hardware.AnalogInput(Cpu.AnalogChannel.ANALOG_0);

            while (true)
            {
                Debug.Print("A5 " + analogInputTemp.Read().ToString());
                Debug.Print("A0 " + analogInputPoti.Read().ToString());

                Thread.Sleep(1000);
            }

output:

A5 0 A0 0      ->> both potis set to zero
A5 0 A0 0      
A5 1018 A0 0   ->> a5 poti set to max
A5 1016 A0 1   
A5 1019 A0 0
A5 482 A0 0    ->> a5 poti set to ~half
A5 467 A0 0
A5 467 A0 1017 ->> a0 poti set to max
A5 467 A0 1019
A5 467 A0 476  ->> a0 set to ~half
A5 467 A0 476
A5 339 A0 461
A5 0 A0 428    ->> a5 set to zero (the a5 poti falls from 461 to 428 automatically)
A5 1 A0 427
A5 0 A0 429
A5 1018 A0 526 ->> a5 set to max (the a5 poti increase from 428 to 526 automatically)
A5 1018 A0 526
A5 1018 A0 526
A5 446 A0 473  ->> a0 set to ~half (the a5 poti falls from 526 to 473 automatically)
...

in my post before I uploaded a diagram when this effect arise.
 
grey