FEZ Cream Socket change

Archive
1

Hi guys,
Just a simple question: can I edit the FEZ Cream driver to map a different socket type (e.g. socket K instead of a socket Y)?
I need to enable rpi2 to send SMS so I’d like to connect CellularRadio Module but it uses Socket K and FEZ Cream has not a Socket K.

Thanks in advance
Big

2

Thanks for reply. I’m trying it and I’m having some trouble.

Is this the right way to instantiate a class of SerialDevice?

GHIElectronics.UWP.GadgeteerCore.SocketInterfaces.SerialDevice serial;

this.serial = await parentSocket.CreateSerialDeviceAsync();
this.serial.BaudRate = 19200;
this.serial.Parity = Windows.Devices.SerialCommunication.SerialParity.None;
this.serial.DataBits = 8;
this.serial.StopBits = Windows.Devices.SerialCommunication.SerialStopBitCount.One;
this.serial.Handshake = Windows.Devices.SerialCommunication.SerialHandshake.None;

The code above is a snippet of:

protected async override Task Initialize(ISocket parentSocket) {
   ...
}

I get a ‘System.ArgumentOutOfRangeException’ in mscorlib.ni.dll

The exception is thrown here, in the “NativeInterfaces.cs” of UWP Gadgeteer Core:

public static async Task<WD.SerialCommunication.SerialDevice> CreateInterfaceAsync(string deviceId) {
     var infos = await WD.Enumeration.DeviceInformation.FindAllAsync(WD.SerialCommunication.SerialDevice.GetDeviceSelector(deviceId));

     return await WD.SerialCommunication.SerialDevice.FromIdAsync(infos[0].Id);
}

Exception is thrown because the var “infos” returned from method FindAllAsync is empty.
Can you help me to understand why?

Thanks
Big

3

@ BigFoot - we are still working on adding serial support. I would start with the native UWP serial: https://developer.microsoft.com/en-us/windows/iot/win10/samples/serialsample