Using Interrupts on Digital Inputs

Is there any example code on using interrupts on digital inputs via Windriver?

Also, are there any restrictions on which digital inputs can be used via interrupts?

Any digital input pin is as good as any other. So far as I know, however, none of them will be able to generate interrupts that your code can respond to.

Why do you want an interrupt? The WPI library has support via the FPGA for pretty much anything you might otherwise need interrupts to implement.

We were thinking about having an ISR service high priority tasks outside of the main loop if necessary.

Sure, but what specifically do you want to do? I can’t think of any events you’d need a “high priority” routine for.

We have some tasks based on limit switches which have high priority. Can’t tell you much more than that since its proprietary… :yikes:

If you look at the source for the DigitalInput class you will see virtual methods for using interrupt handlers. You can use a tInterruptHandler object to catch the interrupts.

We have implemented interrupt handling for our limit switches, reset operations, autonomous goodies using GPIO and the DigitialInput class. Points to note to save you from our madness, the DIO sig pins are pulled high, therefore you switch them low to get response (then high again to get toggle). You will get switch bounce as the contacts come together and separate. You need to program against that. You also need to set the leading or trailing edge of the pulse correctly (the default is the wrong way round by my estimation in the DigitalInput interrupt handler), since the initial setup is to transition to 0v, you should only interrupt on the trailing pulse edge. If not, you will get an interrupt for the press and another for the release of the switch - unless you are interested in that granularity of course.

Good luck. I’ll paste some code here to help.

1711 Raptors

#include "WPILib.h"
#include "Reset.h"

// Victor crab drive definitions
Victor *vicCrabFront;
Victor *vicCrabRear;

#define CRABRESETTIMEOUT 20		// reset timeout in seconds for crab drive

bool frontLimit;
bool rearLimit;

// front crab limit switch interrupt handler (handles both left and right switches)
static void hdlrCrabFrontLimit(tNIRIO_u32 interruptAssertedMask, void *param)  {
	// only process if not already set (eliminates switch bounce)
		// hit limit switch, turn the other way 
		if(vicCrabFront->Get()>0) {
			cout<<"Front right limit fired"<<endl;
		} else {
			cout<<"Front left limit fired"<<endl;
	} else 

Reset::Reset () {
	DigitalInput swCrabFrontRightLimit(4);
	DigitalInput swCrabFrontLeftLimit(5);
	Timer timer; 

	// create the crab Victor objects
	vicCrabFront=new Victor(7);
	vicCrabRear=new Victor(8);

	// adjust interrupts to fire on trailing edge (5>0v) transitions.

	// enable limit switch interrupts (1 routine handles left and right limits)

	// ensure all limit switches are off to start

	// zero front crab drive if not already in position
	cout<<"Waiting "<<CRABRESETTIMEOUT<<" seconds for front reset"<<endl;
	if(swCrabFrontZero.Get()==false) {

		// move crab front drive to right looking for 0 point
		// hold for CRABRESETTIMEOUT seconds waiting for the crab to find zero 
		while(timer.Get()<CRABRESETTIMEOUT&&swCrabFrontZero.Get()==false) ;
		// display error if we cannot zero the crab (timed out)
		if(swCrabFrontZero.Get()==false) {
			cout<<"Cannot zero front crab drive"<<endl;