I tried to recreate your test by placing the Spider into a regular cardboard box and placing the modules in the same sockets that you had listed and I cannot get the same results that you are reporting. With the Lid closed, none of the sensors fired unless I disturbed the box a great deal. Upon opening the box, a few of them fired when they detected the lid opening. After the lid was opened, none of the sensors fired unless I waved my hand in front of them. I reclosed the lid and still none of them fired unless the box was disturbed. I attempted this test with both external power and power only from the USB port on the PC itself.
All of the tests were negative for the behavior that you are reporting.
All that can be done now, if you can, would be to send us your modules and we can test them here.
The first few was when the box was open. The large gap was when the lid was closed. I reopened the lid and until I moved in front of them, nothing was detected.
“trigger” message is displayed each 6 second without I pass my hand front of the sensor !
And serCam.isNewImageReady is never equal to true so Debug.Print(dataimage.ToString()); is never displayed.
I think that there is a hardware issue.
1- I connected PIR (socket 4) and camera (socket 8 ) to SPIDER.
2- In prgram.gadgeteer interface I added only PIR module so SW don’t recognize any camera.
=> I receive every 6 seconds the message "trigger !!
Using extender module I did two buttons. One on Pin 5 and second on Pin 8 of socket 9.
So aim of this test is to confirm that the seen problem is dealing with PIR module or spider.
=> Result: I have the same behaviour. I mean when I press button on Pin 5, event is triggered for Pin 5 and Pin 8 !!! same thing when pressing button on Pin 8 !!
@ Mo7a On the Spider, you wired a button to pins 5 and 8 on socket 9. When you pressed the pin 5 button, you got an interrupt on both pins and when you pressed the pin 8 button you still got an interrupt on both pins?
Hello @ John. Yes you have well summarized what I observe.
But I think found the source of this problem. In fact I didn’t add a capacitance to delete noises when button is pressed. As I haven’t one, I add some wait in source code to be sure that signal read is still equal to 1:
I thought that it’s the case for PIR module so I added this “SW filter” on Pin3 BUT THE SIGNAL IS STILL HIGH AND I RECEIVE DEBUG MESSAGE EVERY 6 SECONDS :wall:
I will make some hardware test in PIR module and come back to you if I find something…
We were able to reproduce the issue with the SerCam being connected, but we do not have a solution for it at this time. We will let you know when we do.