Regarding my last post - Netduino Plus 2 (and Netduino Plus 1) - Netduino Forums
   
Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

Regarding my last post

AdvancedButtonApp InterruptPort

Best Answer toddpthayer, 15 May 2013 - 05:37 PM

It appears I sent the wrong version of the file... and now, it's working.

I moved it from work to home, and now everything is fine.

I'll have to dig in and see if the driver / framework versions are the same to see if I can in fact reproduce the failure, but for now... I'm going to humbly apologize for bothering you....

 

Todd

Go to the full post


  • Please log in to reply
1 reply to this topic

#1 toddpthayer

toddpthayer

    New Member

  • Members
  • Pip
  • 1 posts

Posted 15 May 2013 - 05:17 PM

Hello,

 

Brand new to Netduino, having tinkered with Arduino and some Visual Basic (I am a broadcasting systems integrator with a broad background in hardware and software systems).

 

I'm working on a project to monitor some hardware and respond to events etc, was successful in building the AdvancedButtonApp, then in moving the LED to a digital pin, but when I try to move the button functionality to an outboard button, it reliably locks up the board.

 

The good news is, the firmware flashing info is clear and concise and the board comes back (over and over again).

 

In researching the InterruptPort at MS, I find this

 

It is possible to configure an InterruptPort object into an invalid state. In such cases, your program may not generate an exception until it actually uses the InterruptPort object. For example, suppose you create an InterruptPort object with its resistor mode set to Port.ResistorMode.PullUp, the interrupt mode set to Port.InterruptMode.InterruptEdgeLevelHigh, and the glitch filter set to true. This configuration does not generate an exception when you instantiate an InterruptPort object. If you then add an interrupt handler, the .NET Micro Framework throws an exception.

 

I might expect an error, but I don't think it should brick out.

 

As I mentioned, just starting out... I'm not sure where to go next...

Code attached...

 

Any help appreciated.

Todd

 

 

Attached Files



#2 toddpthayer

toddpthayer

    New Member

  • Members
  • Pip
  • 1 posts

Posted 15 May 2013 - 05:37 PM   Best Answer

It appears I sent the wrong version of the file... and now, it's working.

I moved it from work to home, and now everything is fine.

I'll have to dig in and see if the driver / framework versions are the same to see if I can in fact reproduce the failure, but for now... I'm going to humbly apologize for bothering you....

 

Todd







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.