Jump to content

interrupt handling in AIN or DIN?


slajar

Recommended Posts

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...