ADC Input block - solved
Posted: Tue Aug 26, 2008 10:04 am
M. Kerhuel,
there is still a problem with the ADC Input block.
For dsPIC33FJ256GP710, it gives the permitted
analogue input pins as 0-21 and 24-33, instead of
0-31 (which is certainly correct)
It is as though 22 and 23 were entered as 32 and 33, and the list was
then sorted into order. Typing 22 produces a dialogue
box:
RTW for PIC 16 MCU error
Subscript indices must either be real positive indices or logicals.
Checking the nearest convenient data-sheet,
Microchip's 70286A (covering dsPIC33FJXXXGPX06/X08/X10)
whenever AN21 is present AN22 and AN23 are also present:
that is, on
dsPIC33FJ{64,128}GP708
dsPIC33FJ{64,128}GP310
dsPIC33FJ256GP510
dsPIC33FJ{64,128,256}GP710
all but the GP708 versions continue with
pins AN24 - AN31: the GP708 stops with AN23.
On the other hand, I don't actually get any input on AN22, even
when I modify AD1CSSH to set the bit I want. I don't yet
understand this, and it might be relevant if I did. It is possible
that this is a problem with the hardware (or my understanding
of it), but I thought I should mention it.
Bernard Leak
there is still a problem with the ADC Input block.
For dsPIC33FJ256GP710, it gives the permitted
analogue input pins as 0-21 and 24-33, instead of
0-31 (which is certainly correct)
It is as though 22 and 23 were entered as 32 and 33, and the list was
then sorted into order. Typing 22 produces a dialogue
box:
RTW for PIC 16 MCU error
Subscript indices must either be real positive indices or logicals.
Checking the nearest convenient data-sheet,
Microchip's 70286A (covering dsPIC33FJXXXGPX06/X08/X10)
whenever AN21 is present AN22 and AN23 are also present:
that is, on
dsPIC33FJ{64,128}GP708
dsPIC33FJ{64,128}GP310
dsPIC33FJ256GP510
dsPIC33FJ{64,128,256}GP710
all but the GP708 versions continue with
pins AN24 - AN31: the GP708 stops with AN23.
On the other hand, I don't actually get any input on AN22, even
when I modify AD1CSSH to set the bit I want. I don't yet
understand this, and it might be relevant if I did. It is possible
that this is a problem with the hardware (or my understanding
of it), but I thought I should mention it.
Bernard Leak