On 24 Nov 2008, at 06:14 , Joep Suijs wrote: >> Or do we know the 16F ADC version? > Not that I know of. > But we do have some clue's in the bit names of registers (in casu: > ADCON1). If we use the bits and not the register as a whole, the > difference of 16f88 and 16f877 was discovered by the compiler. > Only in the case that certain bit-configs are not valid will be > overlooked (which is maybe the case with i2c-hardware on 16f88). > > So, would it be worth a try to set all configurations by setting > each bit?
No way. We could make different versions via conditional compiling, but I propose separate versions first, if need be with a list of supported PICs at the Documentation section of the library. Interface proposal: CHANNELS = 8 V_REF_PLUS = off V_REF_MIN = off procedure set_channel(byte in channel) function get_AD_result() return byte function get_AD_result() return word Where the last two functions set the justification bit each time. --- ir EE van Andel [EMAIL PROTECTED] http://www.fiwihex.nl Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands tel+31-546-491106 fax+31-546-491107 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
