Hello,
I ordered my spider two days ago, it arrived today, and it appears to be having problem after problem.
The install appeared fine on both my laptop and main pc. No error messages during that. I then upgraded the bios, and that appeared 100%. I put the dip switches back after.
In Visual Studio, I can set up a diagram, add a button event, and the button works fine.
With the lights, with AddBlue I get green, with Add green I get blue.
With the camera. The picture capture event has fired once between a slew of it never working. The camera fires the camera connected event. I have set the resolution to low, and every call to take picture goes by, but no event.
The screen when connected appears permanently dead. I have followed guides, and no colours at all, not even a flicker.
All this on two computers.
Before I send this back, am I missing anything basic?
Yes some LEDs are reversed. The fix is by calling LED.swap___ I do not remember the exact name. We will add this to the getting started guide to make this simpler fro new users.
Feel free to send back but I do not think you need to. You just got the kit so give it some time to see the benefits. Have you used gadgeteer before? If not then there is a little learning curve. It is very short curve but not few hours
Thank you for the reply. I spotted the swap after posting the last message.
The camera is a problem. Taking the kit into work tomorrow, and will rig it up to a different version of visual studio, and a different version of windows. Do not think they are the problem, but willing to try.
Followed the sticky earlier, and the wiki, all to no avail.
The monitor just appears dead. It is linked up in the diagram, commands are being sent over, but it has never shown any sign of life at any time. The connectors appear good, no pins are missing or bent. I was expecting to see some life on the monitor when flashing.
All the work with the kit has been done on my workbench, so no chance of static zapping it. All connecting an disconnecting when the device is not connected to power. Have dabbled a bit over the years.
Looking forward to having some working kit to play with. Been a developer for 17 years, used to specialise in AI, Internet communications, and computer vision. Hoping to bring something productive to the community, and fun to my evenings.
My two test machines here were both windows 7 64 bit on VS2010.
Two other machines to test it here on, but installing VS is a pain this early in th emorning.
I tried at lower resolutions, but still no joy.
I will try VS 2008, and 32 bit machines at work tomorrow.
Tried direct usb connection, and through a powered USB hub.
If I notice any differences with the camera will let you know.
Overall impressed by the kit. If the display is dead, then it is dead, it happens.
don’t bother trying with VS2008, the .netMF 4.1 SDK is only compatible with VS2010.
The wiki that talks about the debug steps for the camera, what are your results? That might help the GHI team to identify what if anything is different in your results.
In work now, installed on a slower 32 bit machine.
Also redownloaded, and reflashed the device.
Program is from the wiki, same version I was testing with last night.
Have run the program 10 times.
Very strangly when running at home I have only seen it capture once. when running here. It still has times when not capturing at all, but has had a few times when it has captured two or three times before failing to capture for the rest of the test.
If only some people are having the problem, then could the others be using an older flash, or driver which may work us now? Or has the software on the camera itself changed?
The display is still totally dead to the world.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\mscorlib.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Native.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Hardware.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.IO.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\GHI Electronics\GHI NETMF v4.1 SDK\Assemblies\le\GHIElectronics.NETMF.System.dll’
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Graphics.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\GHI Electronics\GHI NETMF v4.1 SDK\Assemblies\le\GHIElectronics.NETMF.USBHost.dll’
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Net.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.TinyCore.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\System.IO.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Hardware.SerialPort.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Gadgeteer\Core\Assemblies.NET Micro Framework 4.1\le\Gadgeteer.dll’
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\System.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Net.Security.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\System.Net.Security.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\System.Http.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Gadgeteer\Core\Assemblies.NET Micro Framework 4.1\le\Gadgeteer.WebClient.dll’
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\GHI Electronics\GHI .NET Gadgeteer SDK\Modules\Camera\NETMF 4.1\le\GTM.GHIElectronics.Camera.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Gadgeteer\Core\Assemblies.NET Micro Framework 4.1\le\Gadgeteer.WebServer.dll’
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Touch.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\GHI Electronics\GHI .NET Gadgeteer SDK\Modules\Display_T35\NETMF 4.1\le\GTM.GHIElectronics.Display_T35.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\GHI Electronics\GHI NETMF v4.1 SDK\Assemblies\le\GHIElectronics.NETMF.Hardware.dll’
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files\GHI Electronics\GHI .NET Gadgeteer SDK\Mainboards\FEZSpider\NETMF 4.1\le\GHIElectronics.Gadgeteer.FEZSpider.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘c:\data\visual studio 2010\Projects\GadgeteerApp1\GadgeteerApp1\bin\Debug\le\GadgeteerApp1.exe’, Symbols loaded.
The thread ‘’ (0x2) has exited with code 0 (0x0).
Using mainboard GHIElectronics-FEZSpider version 1.0
Displaying information about the connected display…
Display Resolution: Height: 240 Width: 320
Display Auto Redraw: True
Program Started
Camera was busy taking a picture. Number of times picture capture failed: 1
Camera reports that it is ready to take a picture. Attempting to take a picture
Camera successfully connected!
Displaying information about the connected camera…
Camera Resolution: Height: 240 Width: 320
Camera Ready: False
If you are experiencing blurry or unfocused images, try manually adjusting the camera’s focus, located on the end of the camera lens.
Camera was busy taking a picture. Number of times picture capture failed: 1
Camera was busy taking a picture. Number of times picture capture failed: 2
Camera was busy taking a picture. Number of times picture capture failed: 3
Camera was busy taking a picture. Number of times picture capture failed: 4
Camera was busy taking a picture. Number of times picture capture failed: 5
Picture successfully captured!
Picture encoding: 3
Attempting to print the picture to the display…
Picture sent to the display.
Camera reports that it is ready to take a picture. Attempting to take a picture
Camera was busy taking a picture. Number of times picture capture failed: 1
Camera was busy taking a picture. Number of times picture capture failed: 2
Camera was busy taking a picture. Number of times picture capture failed: 3
same message up to 501
Camera was busy taking a picture. Number of times picture capture failed: 501
The program ‘[11] Micro Framework application: Managed’ has exited with code 0 (0x0).
