interrupt handling in AIN or DIN?

[slajar]

Hi all,

actually, I am going to modify my Core Module to do something different (a small frequency counter and trigger box). Therefore I am reading manuals and tech docs about 18f452. That's why I have a small question. How does it come that the DIN and AIN doesn't drive the interrupts on portB? I know it could reduce the number of midi-events. That's why I have another question, what is the everage latency time of this polling? Do I get 100 Hz?

Thank you

Matthias

[TK.]

Hi Matthias,

How does it come that the DIN and AIN doesn't drive the interrupts on portB? I know it could reduce the number of midi-events.

Which PIC feature do you mean exactly?

what is the everage latency time of this polling? Do I get 100 Hz?

The AIN latency is 200 uS * number of analog channels --- with the MIOS_AIN_DynamicPrioSet feature the latency of the "last changed" inputs can be reduced (but this is only useful for MIDI controllers)

You can reduce the latency a lot, when analog channels are not converted timer interrupt driven with low priority (like handled by MIOS), but directly from your main task.

The DIN latency is specified with the MIOS_SRIO_UpdateFrqSet function, by default it's 1 mS -> 1 kHz (I guess this meets your requirements ;-)

Best Regards, Thorsten.