Thread: Reading Interrupt Ports
View Single Post
  #2   Spotlight this post!  
Unread 19-05-2008, 20:33
gblake's Avatar
gblake gblake is offline
6th Gear Developer; Mentor
AKA: Blake Ross
no team (6th Gear)
Team Role: Mentor
  
Join Date: May 2006
Rookie Year: 2006
Location: Virginia
Posts: 1,934
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
Re: Reading Interrupt Ports
Quote:
Originally Posted by ManicMechanic View Post
I tried posting this in the Programming thread a while ago but didn't get any takers, and the question has come back to haunt me. I use EasyCv2 for Vex and would like to know how to read the values of the 6 interrupt ports (similar to the way that you use GetDigitalInput(I) to read one of the digital input ports). Basically, I want to create something similar to the FVC/FTC competition template, where I can select between autonomous and R/C, but not be limited by the 20 second/2 minute demarcations of the template the way it currently exists. Does anyone know how to do this?
I think that any instructions able to do this will either have to be imbedded in a slug of User Code blocks, or be a chunk of ordinary C code that a User Code block or a User-defined routine refers to.

So... If you are asking if EasyC 2.X exposes a built-in interrupt reader to users, I think you are out of luck. If you are willing to dive into using ordinary C to write an interrupt detector, that is a different kettle of fish.

Invoking a home-brew detector from within an EasyC 2.X routine might be possible. If it is, I'll leave up to someone else to describe how to do that
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
Reply With Quote