we know. it says so in the specs

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

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!

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.

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

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

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.

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?

i already have them too

I dont think its the com port as i did a loop back test and it seemed ok but 100% sure.

            byte[] outbuff = new byte[] { 0x56, 0x00, 0x32, 0x0C, 0x00, 0x0A, 0x00, 0x00, bPos1, bPos2, 0x00, 0x00, bLen1, bLen2, bdelay1, bdelay2 };            int numPackets = imagelength / 496;            if (imagelength > (numPackets * 496)) numPackets += 1;            byte[] imageData = new byte[imagelength];            for (int i = 0; i < numPackets; i++)            {                int pos = i*496;                // Ask for the next packet                outbuff[8] = (byte)(pos >> 8);                outbuff[9] = (byte)(pos & 0xFF);                serialPort.Write(outbuff, 0, outbuff.Length);                int bytesToRead = 506;

 

as soon as you step over the last line, thats it! no more debugging and the program has crashed!

cant test on another com port as its a sheild. Works fine the plus 1 and there are a few deployed at our customers

 

One the plus 2 it seems the debugging is terrible. you step over while bugging and nothing happens!!! its hard to explain

 

I wish i never brought the plus 2 now but no where stocked the plus 1. im a tight dead line and these kind of hassles is not what i need right now!

compared to plus 1 the com port 2 is not behaving correctly. we got a serial camera attached and it does not get any data when we asked for it  or when we write a buffer it just hangs!!!  (Baud rate 115200)

 serialPort = new SerialPort("COM2", 38400, Parity.None, 8, StopBits.One);

hi, sorry. its noting special

Adafruit was the place we got the plus 2's from because no where in the UK had enough stock and no stock of the plus 1's. We went for the Plus 2 thinking it would be a direct drop in replacement.

 

The funny thing is ive put my shield back on the plus 1 and its working as well as can be expected. Stick on the plus 2 the com2 and debugging is a nightmare.

 

Com 2 is set to 38400 initally until i set up the camera and the camera the baud rate to use is 115200. Then i close the port, change the baud rate and then re-open it. Any other comms after returns 0 bytes to read!

thanks mark but with we need more than 10 and need to get this working on the 2's as it will benefit everyone as there is an issue here. like i said it works fine the np1 and falls over on the np2.

i dont a small project which basically sets up the camera, takes a pic and returns the pic as a byte array and yes the same issue is there.

 

public byte[] GetImageData(int imagelength)        {            byte bdelay1 = 0x00;            byte bdelay2 = 0x0A;            byte bPos1 = 0x00;            byte bPos2 = 0x00;            // datalength of 496. Camera transfer maximum 512 bytes at a time. Each packet has 5 bytes at the start and 5 at the end            // and the datalength must be a multiple of 8. So 496 is the biggest we can have            byte bLen1 = 0x01;            byte bLen2 = 0xF0;            byte[] outbuff = new byte[] { 0x56, 0x00, 0x32, 0x0C, 0x00, 0x0A, 0x00, 0x00, bPos1, bPos2, 0x00, 0x00, bLen1, bLen2, bdelay1, bdelay2 };            int numPackets = imagelength / 496;            if (imagelength > (numPackets * 496)) numPackets += 1;            byte[] imageData = new byte[imagelength];            for (int i = 0; i < numPackets; i++)            {                int pos = i*496;                // Ask for the next packet                outbuff[8] = (byte)(pos >> 8);                outbuff[9] = (byte)(pos & 0xFF);                serialPort.Write(outbuff, 0, outbuff.Length);                int bytesToRead = 506;                if ((imagelength - pos) < 496)                {                    bytesToRead = (imagelength - pos) + 10;                }                WaitForData(bytesToRead, 100, imageData, pos);            }            StopPic();            return imageData;        }

as i step over the code the debug line dissapear when i do a serial.write and it looks like the system has crashed as there is nothing else i can do!

changing the baud rate

 public bool ChangeBaudRate(Baud baudRate)        {            byte b1= 0x2A,b2= 0xF2;            switch (baudRate)            {                case Baud.B57600:                    b1 = 0x1C;                    b2 = 0x4C;                    break;                case Baud.B115200:                    b1 = 0x0D;                    b2 = 0xA6;                    break;            }            byte[] outbuff = new byte[] { 0x56, 0x00, 0x24, 0x03, 0x01, b1, b2 };            serialPort.Write(outbuff, 0, 7);            byte[] inbuff = WaitForResponse(5, 50);            if ((inbuff[0] == 0x76) && (inbuff[2] == 0x24))            {                serialPort.Close();                serialPort.BaudRate = 115200;                serialPort.Open();                return true;            }            return false;        }

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

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

thanks but that was the basis of my code

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?