You are reading a single comment by @Robin and its replies.
Click here to read the full conversation.
-
Right. I program, commit, push, deploy, etc on my computer at my desk.
Usually, I'll connect the puck to my workstation, upload new code, disconnect it from my workstation and reconnect it on our "production computer". My workstation is 100% functional and has no issues with the IDE.
The production computer is the one having issues - it's able to connect via BLE, the IDE just doesn't open completely. I need the production computer to be functional, so other non-technical users can simply open the IDE, to troubleshoot and redeploy the code as-needed.
tako
@Robin
and this is a different Win10 PC than that used in forum post F13-F24 HID keys then?
I'm puzzled, you were communicating with a Puck using a Win10 PC there, so presumably was the native IDE for BLE which should be the same as the one installed from the file indicated in #8 above?
Then I would list the PC mfg, processor/board perhaps along with the version of Win10 for Gordon's reference.