Button cannot be connected on socket14 (FEZ Spider firmware 4.1.8.0)

Archive
1

Hi,

I installed firmware 4.1.8.0 and like the last firmware version, button cannot be connected on socket 14. Is there a reason?

Dick

2

What do you mean? See attached image please.

Welcome to the community.

3

Compilation pass, but error when running the code. If the button is place on another socket, it works.

I hope you can reproduce the issue.

Dick

4

What about socket 12?

5

Actually socket 12 isn’t working…

6

I installed new. Works here on 14.
Fry anything?

7

Those are the LCD dockets and there was a bug which was fixed.

Did you start a new project?

Can you try LCD, then remove LCD then try button?

8

When connecting a button on socket 14, it seems to act as a screen.

Here is the error message I got after connecting an Oled display on socket 6 and a button on socket 14 :

Using mainboard GHIElectronics-FEZSpider version 1.0
Program Started
ERROR: You can only use WPF on one display (and if an LCD is present, only on the LCD)

9

Will get back to you Monday when we are at work and try this.

10

Hi,

After a reinstall of the Visual Studio templates, I could connect a button on socket 14. But if I connect an Oled display I still have the error message sent saterday.

Dick

11

So the oled is causing the problem for button on socket 14?

12

I’ve tested this on the latest firmware and latest SDK, and it worked. The fix for this issue was not in the firmware, instead, it was in the device drivers. I have attached the code and a picture of the designer that I used to test. If installing the new SDK doesn’t fix this, let us know and we will look further into the issue.

using System;
using System.Collections;
using System.Threading;
using Microsoft.SPOT;
using Microsoft.SPOT.Presentation;
using Microsoft.SPOT.Presentation.Controls;
using Microsoft.SPOT.Presentation.Media;
using Microsoft.SPOT.Touch;

using Gadgeteer.Networking;
using GT = Gadgeteer;
using GTM = Gadgeteer.Modules;
using Gadgeteer.Modules.GHIElectronics;
using Gadgeteer.Modules.Seeed;

namespace button_on_14
{
    public partial class Program
    {
        // This method is run when the mainboard is powered up or reset.   
        void ProgramStarted()
        {
            /*******************************************************************************************
            Modules added in the Program.gadgeteer designer view are used by typing 
            their name followed by a period, e.g.  button.  or  camera.
            
            Many modules generate useful events. Type +=<tab><tab> to add a handler to an event, e.g.:
                button.ButtonPressed +=<tab><tab>
            
            If you want to do something periodically, use a GT.Timer and handle its Tick event, e.g.:
                GT.Timer timer = new GT.Timer(1000); // every second (1000ms)
                timer.Tick +=<tab><tab>
                timer.Start();
            *******************************************************************************************/
            button.ButtonPressed += new Button.ButtonEventHandler(button_ButtonPressed);
            button.ButtonReleased += new Button.ButtonEventHandler(button_ButtonReleased);

            // Use Debug.Print to show messages in Visual Studio's "Output" window during debugging.
            Debug.Print("Program Started");
        }

        void button_ButtonReleased(Button sender, Button.ButtonState state)
        {
            Debug.Print("UP");
            oledDisplay.SimpleGraphics.Clear();
            oledDisplay.SimpleGraphics.DisplayText("UP", Resources.GetFont(Resources.FontResources.NinaB), GT.Color.Red, 10, 10);
        }

        void button_ButtonPressed(Button sender, Button.ButtonState state)
        {
            Debug.Print("DOWN");
            oledDisplay.SimpleGraphics.Clear();
            oledDisplay.SimpleGraphics.DisplayText("DOWN", Resources.GetFont(Resources.FontResources.NinaB), GT.Color.Red, 10, 10);
        }
    }
}
13

Still not working on my laptop and also in a virtual machine on a Mac.

14
  1. How about showing your code?
  2. If you are using a Hydra there is an open issue with VMs on Macs.
15

the code is pretty simple, there is no code… just put a Oled display on socket 6 or 9 and a button socket 14 or 12 in design mode. Compilation passed… but error on running the application.

I a using a Spider with these configuration :

DeviceInfo:
HAL build info: 4.1.2821.0, Microsoft Copyright (C) Microsoft Corporation. All rig
OEM Product codes (vendor, model, SKU): 255, 0, 65535
Serial Numbers (module, system):
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Solution Build Info: 4.1.8.0, GHI Electronics, LLC
AppDomains:
default, id=1
Assemblies:
mscorlib,4.1.2821.0
Microsoft.SPOT.Native,4.1.2821.0
Microsoft.SPOT.IO,4.1.2821.0
Gadgeteer,2.41.0.0
Gadgeteer.WebClient,2.41.0.0
Microsoft.SPOT.Graphics,4.1.2821.0
Microsoft.SPOT.Hardware,4.1.2821.0
System.Http,4.1.2821.0
System,4.1.2821.0
GTM.Seeed.OledDisplay,1.4.1.0
Gadgeteer.WebServer,2.41.0.0
GadgeteerApp35,1.0.0.0
Microsoft.SPOT.Touch,4.1.2821.0
Microsoft.SPOT.Net.Security,4.1.2821.0
GTM.GHIElectronics.Button,4.1.1.0
Microsoft.SPOT.TinyCore,4.1.2821.0
GHIElectronics.NETMF.IO,4.1.8.0
Microsoft.SPOT.Net,4.1.2821.0
System.IO,4.1.2821.0
GHIElectronics.NETMF.Hardware,4.1.8.0
System.Net.Security,4.1.2821.0
Microsoft.SPOT.Hardware.SerialPort,4.1.2821.0
GHIElectronics.NETMF.System,4.1.8.0
GHIElectronics.Gadgeteer.FEZSpider,4.1.2.0

16

I think your browser is cashing the old SDK. Open the release note in the GHI gadgeteer folder and check the version.