Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

Does anyone know if the GetADC() functions always run code to re-configure the input pins to A/D type, regardless of whether they were already set that way? I would have thought that there was a processor overhead associated with that method and that a coding scheme such as: Call ConfigADC(pinnumber) 'configure the pin as A/D Do iV = GetADC(pinnumber) 'faster as pin is already configured Loop would be better. I doubt many applications switch pins from one mode to another as the input circuitry would not support this very easily. Ian

______________________________
TI's C2000™ microcontrollers controlSUITE™ Desktop gives you instant access to all supporting software libraries, training, collateral, and more!


(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )