LMAO, Cheers Nak

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.

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.

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

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

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!

i already have them too

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.

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?

sorry stefan. can you delete this thread please

 

I managed to get to work by setting the hardware to the emulator then the plus 1

the project is not working on the plus 2 so im trying to deploy the project back to plus 1 and i cant why is it? does this mean its not backward compatible. Also how do i support legacy systems?

I'm trying to do the above. it was working ages ago but now all of a sudden my app just hangs!

            byte[] assemblyData = GotSDCard ? File.ReadAllBytes(filename) : ServerHelper.DownloadFile(filename);
            if (assemblyData == null)
                throw new Exception("Assembly was empty");
            try
            {
                Assembly assm = Assembly.Load(assemblyData);
                Debug.Print("loaded Assembly: " + filename);

it hangs on the Assembly.Load call.

In the output window i get

The debugging target runtime is loading the application assemblies and starting execution.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\le\SecretLabs.NETMF.Hardware.NetduinoPlus.dll', Symbols loaded.

How can i fix this or see whats going on?

thanks but that was the basis of my code

its the same size and im using the little endian file. it wont even load it from the sd card if i manually copied the pe file.

we could have 100 of these suckers attached to a webserver and it would be nice if the webserver pushed the firmware update.

would love to but it's a commerical project. I'm scrapping this now as I've spent too much time on it. Just wish this device could do OTA updates. Now got to work on a RS422 interface

Thats what I've used but like i said it hangs on the assembly.load and does not return my app just hangs

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

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.

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

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.