I am trying to send AT commands to a XDot device (Eu1-A00) using a UWP application (.Net Core). My app is working only after I connect with Putty to the XDot and send a simple “AT” command.
Here are the steps:
1. I plug the xDot in a usb port on my PC
2. I run my app that sends “AT” to the device but I get no answer back. At the second click I get the error “WinRT information: The operation identifier is not valid.” (this I think it is because the operation at the first click did not finish… but not entirely sure)
3. I connect with putty to the device, send AT, get the OK, close Putty
4. Open my application again, send the command, get the answer. After this all the other commands work as well.
It seems like the Putty on my PC is “waking up” the XDot(?).
Any idea why this behavior?
On my Raspberry Pi (with Windows 10 IoT Core 15063) I get the same behavior as in step 2 above.
I cannot connect with Putty to my Raspberry Pi so I cannot say if it will “wake up” the XDot there also..