we know. it says so in the specs

well, went on site yesterday to test and it was terrible. triggered once or a few time then nothing!!!

oh and even used the onboard switch too and that was flaky

Ended up having to write my interrruptPort class in the end and it was stable.

no i added it to see if it would fix it but alias not.

Thanks for your help but im getting no where

just attached an NP v1 and works with no false triggering.

My input stage is simple : a connector (input from outside world, open collector source) ->  pull-up resisitor -> connector (micro switch but for testing, the connectors are shorted) -> Schmitt inverter input -> Netduino input! (D0).

I added the trigger inverter yesterday.

like i said if i connect the ground from either by meter or scope it triggers!

i already have them too

with the switch not connected to the input stage it should not trigger but it does.

I can even trigger this when i put the neg lead of my meter on the gnd of my board!

So i dont belive its a floating pin issue.

I've got the internal pull up resistor enabled so it should only go low when the switch is activated otherwise there's 3v3 on the inputs.

I've noticed when i attach the gnd of my scope on to the circuit it triggers it also but i know that my scope is not isolated.

another thing I've noticed is when i attach the gnd to my meter, it triggers it also. Now thats really weird!

here's a really long one!

ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 123 ODD ball trigger: 28 - 124 ODD ball trigger: 28 - 124 ODD ball trigger: 28 - 124 ODD ball trigger: 28 - 124 ODD ball trigger: 28 - 124 ODD ball trigger: 28 - 190 ODD ball trigger: 28 - 191 ODD ball trigger: 28 - 191 ODD ball trigger: 28 - 191 ODD ball trigger: 28 - 191 ODD ball trigger: 28 - 192 ODD ball trigger: 28 - 237 ODD ball trigger: 28 - 237 ODD ball trigger: 28 - 237 ODD ball trigger: 28 - 237 ODD ball trigger: 28 - 237 ODD ball trigger: 28 - 249 ODD ball trigger: 28 - 249 ODD ball trigger: 28 - 249 ODD ball trigger: 28 - 249 ODD ball trigger: 28 - 249 ODD ball trigger: 28 - 249 ODD ball trigger: 28 - 249 ODD ball trigger: 28 - 258 ODD ball trigger: 28 - 259 ODD ball trigger: 28 - 259 ODD ball trigger: 28 - 259 ODD ball trigger: 28 - 259 ODD ball trigger: 28 - 259 ODD ball trigger: 28 - 260 ODD ball trigger: 28 - 261 ODD ball trigger: 28 - 261 ODD ball trigger: 28 - 262 ODD ball trigger: 28 - 262 ODD ball trigger: 28 - 262 ODD ball trigger: 28 - 263 ODD ball trigger: 28 - 263 ODD ball trigger: 28 - 263 ODD ball trigger: 28 - 263 ODD ball trigger: 28 - 263 ODD ball trigger: 28 - 264 ODD ball trigger: 28 - 264 ODD ball trigger: 28 - 264 ODD ball trigger: 28 - 264 ODD ball trigger: 28 - 268 ODD ball trigger: 28 - 268 ODD ball trigger: 28 - 268 ODD ball trigger: 28 - 268 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 270 ODD ball trigger: 28 - 271 ODD ball trigger: 28 - 271 ODD ball trigger: 28 - 271 ODD ball trigger: 28 - 272 ODD ball trigger: 28 - 272 ODD ball trigger: 28 - 272 ODD ball trigger: 28 - 320 ODD ball trigger: 28 - 462 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 468 ODD ball trigger: 28 - 469 ODD ball trigger: 28 - 469 ODD ball trigger: 28 - 469 ODD ball trigger: 28 - 469 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470 ODD ball trigger: 28 - 470

with added debounce

        private void BallTrigEven_OnInterrupt(uint data1, uint data2, DateTime time)        {            string st = time.Second.ToString() + " - " + time.Millisecond.ToString();            Debug.Print("EVEN ball trigger: " + st);            if (ballData.Lanes[(int)id.even].LastPushed.AddMilliseconds(cDebounce) > time)                return;            BallTrigEven.DisableInterrupt();            UpdateStatus(id.even);            Cycle(id.even);            ballData.Lanes[(int)id.even].Data = (int)TestScores.Seven;            ballData.Lanes[(int)id.even].LastPushed = time;            BallTrigEven.EnableInterrupt();        }

break point set on the "if" statement. I triggered the input very crudely (needle nose pliers ) and then F9 when the debugger hit the break point.

Below the debuggers output

EVEN ball trigger: 20 - 851 EVEN ball trigger: 20 - 851 EVEN ball trigger: 20 - 911 EVEN ball trigger: 20 - 938 EVEN ball trigger: 20 - 954 EVEN ball trigger: 20 - 955 EVEN ball trigger: 20 - 966 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 105 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106 EVEN ball trigger: 21 - 106

Now, thats very weird

thats what i thought but it keeps triggering way after the button has been pressed. Also im in bedugging mode too. I placed a break point on the interrupt. When it occurs click go until the it clears. If it happens a few times then its a debounce issue but it just keeps going!

i cant understand what is going on here and was wondering if someone could help me.

I've setup 2 two inputs to interrupt on ports D0 & D1

BallTrigOdd = new InterruptPort(NPIO.BallTrigOdd, true, Port.ResistorMode.PullUp, Port.InterruptMode.InterruptEdgeLow);BallTrigOdd.OnInterrupt += new NativeEventHandler(BallTrigOdd_OnInterrupt);BallTrigOdd.EnableInterrupt();BallTrigEven = new InterruptPort(NPIO.BallTrigEven, true, Port.ResistorMode.PullUp, Port.InterruptMode.InterruptEdgeLow);BallTrigEven.OnInterrupt += new NativeEventHandler(BallTrigEven_OnInterrupt);BallTrigEven.EnableInterrupt();

        private void BallTrigEven_OnInterrupt(uint data1, uint data2, DateTime time)        {            BallTrigEven.DisableInterrupt();            UpdateStatus(id.odd);            Cycle(id.even);            ballData.Lanes[(int)id.even].Data = (int)TestScores.Seven;            BallTrigEven.EnableInterrupt();        }        private void BallTrigOdd_OnInterrupt(uint data1, uint data2, DateTime time)        {            BallTrigOdd.DisableInterrupt();            UpdateStatus(id.even);            Cycle(id.odd);            ballData.Lanes[(int)id.even].Data = (int)TestScores.Seven;            BallTrigOdd.EnableInterrupt();        }

but for some reason it just keeps triggering and gets stuck in a loop. Is there something I'm doing wrong?

Thanks for the replies

Im aware of the 3700 but its expensive and im having to use components that if it becomes obsolete it can easily be replaced.

I've a circuit diagram which should do what i need

we are interfacing to some equipment so there are several inputs of 28VAC so using transformers and regulators is out of the question. The response needs to be pretty darn quick too. Basically its to detect a presence.

I know PLC's have AC/DC inputs, so i kinda need that input stage fitted to my NP2

I need to monitor a state of some 28VAC lines.

Hows the best way to do this?

I know i need a full bridge, some smoothing and a opto coupler but the bit inbetween the smoothing and opto im stuck on.

will be relaying the data on as the NP2 has no imaging libs so we cant process the image internally (which would of been great).

So its not looking like anyone has played with high speed image capturing then

Has anyone got any experience capturing images at high speed?

The current camera we are using can take an image heavily compressed @ 320 x 240 and transfer the image in about over a second via a TTL serial interface.

I need a camera at a resolution of at least 640 x 320 and the transfer rate of well under a second. Any help would be very much appreciated

netmf-toolbox does not do interrupts.

Changed everything to adapt to your code and still nothing.

Thanks for help but ive implemented a software interrupt routine now.

hi, tried your code and it does not work for me

I can do basic IO on this chip without any issues but can i get the interrupt to work, no. Been at it for a few days and im not making any progress, please help!!!!

Hardware setup:

NP2+, clk & data lines have pull up resistors, 2 leds on the output of the mcp chip. 2 simple switch for the input with pull up resistors which is shorted to ground when switched. INTA on the mcp has a direct connection to the NP2+ to DIO0.

private void SetupPort(Port port){byte IODIA = IODIRA;byte IOCONAddress = IOCON;byte GPINTENAddress = GPINTENA;byte INTCONAddress = INTCONA;byte INTCAPAddress = INTCAPA;byte DEFVALAddress = DEFVALA;if (port == Port.PortB){IODIA = IODIRB;GPINTENAddress = GPINTENB;INTCONAddress = INTCONB;INTCAPAddress = INTCAPB;DEFVALAddress = DEFVALB;}// I/O expander configuration 1010 0000this.device.Write(new byte[] { IOCONAddress, 0xA0 });// Interrupt on change pin 00001111 first 4 are enabled only cus they are inputsthis.device.Write(new byte[] { GPINTENAddress, 0x0F });// default value to compare before the interrupt hitsthis.device.Write(new byte[] { DEFVALAddress, 0x0F });// Interrupt on change control reg, interrupts on default valuethis.device.Write(new byte[] { INTCONAddress, 0x0F });// clear the interupt capture regbyte[] ReadBuffer = new byte[] { INTCAPAddress };this.device.Read(ReadBuffer);// Direction register 11110000 first 4 are outputs and the rest are inputsthis.device.Write(new byte[] { IODIA, 0xF0 });// set outputs to 0//SetIOPort(port, 0);}

basicaly the setup is the first 4 bits to be inputs (interrupt driven) and the next 4 bits as outputs.

ive configured to only go high when it receives a high level from the input.

Its not working at all.

Dave thanks very much option b seems to the best and the most easy to implement

I've a log file which i append to every so often. (Thats the easy bit)

What i want to do is if its gets above a certain size then delete the old 1 st line before add the latest line to the bottom of the file.

Is there a way of doing this? i cant exactly read the whole file as i will run out memory

oh ok.

cool. i checked about last month for a solution.

It might be best to make it a sticky somewhere or part of a FAO.

Sorry if this has been discussed before but ive searched for a solution for this and was unable to come with a answer.

I've got a project in VS and i want to deploy across various target boards but i want to pass this task to another member of the team but i dont wish for him to have the source code.

Is there a way of the deploying the output binaries to the target device i.e. MFDeploy.

I think secret labs should get a camera to try in order to see whats going on