Based on the last edit ... my first premise was correct, but it did not help. Since it was asked long ago to set up a wiring diagram, the `phidget-fob1-wiring.png` file (attached) is where I am now. The only functional difference is that I have the common wire (fob) also connecting to the -6v power ...

Okay, I have finally mocked something up in C to test the behaviour. Unfortunately, the results are inconclusive. The program (less some repeating stuff): #include <stdlib.h> #include <stdio.h> #include "phidget22.h" int main(int argc, char *argv[]) { PhidgetReturnCode res; const char *err...

I moved the leads. Doorbell is theoretically fine. However the other device (an old key fob) is still sending signals on power delivery (not yet known if it is a momentary on power delivery or if the switches are closed for the duration). I attached a (blurry, unfortunately) photo of the fob, and of...

By the sounds of the reply, I would be better off placing my outputs on the 0/16/16. The devices power themselves (just needed a Phidget to close the switches I had since desoldered and broken out to leads) - one is powered by 5V, that doorbell in question was powered by a tiny 12V battery. So that ...

Hi, A while back I was gifted a couple InterfaceKits - an 8/8/8 and a 0/16/16 - the older models as they connect by standard USB B. I apparently had some weird assumptions about the digital inputs and outputs. I am looking to (input side) check the state of a switch to see if it is open or closed (c...