Even if pins are input/analog as default, this is required: the lib itself configure the pin as analog + input, we should be functionally-equivalent. More, I don't know if it makes sens, but user could use either as input or output within the same program.
Seb > Just for curiosity: what would be the point of such a definition? > I can imagine that the direction equivalent could be used to force the > pin to input when used in analog mode. But this is the default, so it > is not realy required. > > Joep > > 2009/4/19 Sebastien Lelong <[email protected]>: > > Hi guys, hi Rob, > > > > Is there any chances to be able to access pin as its A/D name. For > instance > > (and according to current adc_hardware), giving PIC 16F877, pin_A0 is > > pin_AN0, pin_E2 is pin_AN7. Could it be feasible to add this to the > device > > files ? I'm not saying this should be done, I'm just thinking about ADC > > channel selection and how to configure appropriate pins. > > > > I've seen there are table in datasheets, representing "pin summary". This > > information could be extracted from this, but hardly parsable... > > > > Cheers, > > Seb > > -- > > Sébastien Lelong > > http://www.sirloon.net > > http://sirbot.org > > > > > > > > > > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
