Oct 8, 2014 at 1:08 AM
Edited Oct 8, 2014 at 1:09 AM
So as you know in .NET Gadgeteer 2.43.800 onwards, there is this new indirection capability, so we have two options here that might be happening.
In the normal case (i.e. input is not
indirected, and you end up with
), you need to correctly specify the resistor mode for the hardware. You can follow the parameter in code: the
passes the parameter to
which directly uses the parameter in .NET Micro Framework's
class. So unless your hardware's firmware is ignoring this parameter,
you need to set it correctly
In the indirected case, it depends on the indirector (i.e.
delegate), what it does with the parameter, it can ignore it, or use it when creating the indirected input class. That's on the manufacturer of the hardware/driver.
The same holds for the bi-directional and interrupt input related classes.
Also note that .NET Gadgeteer mainboards are only required to support
on interruptable GPIOs and are never required to support