Windows 7 : device is visible but connection failed

I am trying to connect to a freshly received puck.js with standalone IDE. I replaced the driver by Zadig, and in connection window I see the puck. Then it fails to connect. In the console I have this:

We have chrome.serial - not using 'serialport' module
'winnus' module not found, no Windows Bluetooth Low Energy Error: The specified module could not be found. \\?\C:\Users\AMOLCH~1\AppData\Local\Temp\nw2072_17556\node_modules\winnus\build\Release\winnus.node
serial_audio: Audio Sample rate : 48000
serial_audio: Audio Serial Baud 9600 Bit time 5
Web Bluetooth available, but Windows Web Bluetooth is broken in <=56 - not using it
GET chrome.storage.sync = {"AUTO_SAVE_CODE":true,"BAUD_RATE":9600,"BLOCKLY_EXTENSIONS":"|bluetooth|robot|","BLOCKLY_LANGUAGE":"en","BLOCKLY_TO_JS":false,"BLUETOOTH_LOW_ENERGY":true,"BOARD_JSON_URL":"http://www.espruino.com/json","COMPILATION":true,"COMPILATION_URL":"http://www.espruino.com:32766","ENABLE_Testing":false,"ENV_ON_CONNECT":true,"FONT_SIZE":12,"MINIFICATION_DeadCode":true,"MINIFICATION_LEVEL":"","MINIFICATION_Literal":true,"MINIFICATION_Mangle":true,"MINIFICATION_Unreachable":true,"MINIFICATION_Unused":true,"MODULE_AS_FUNCTION":false,"MODULE_EXTENSIONS":".min.js|.js","MODULE_MINIFICATION_LEVEL":"ESPRIMA","MODULE_URL":"http://www.espruino.com/modules","NPM_MODULES":false,"RESET_BEFORE_SEND":true,"SAVE_ON_SEND":0,"SERIAL_AUDIO":"0","SERIAL_TCPIP":"","SERIAL_THROTTLE_SEND":false,"SET_TIME_ON_WRITE":false,"SHOW_CODE_LINK_ICON":false,"SHOW_WEBCAM_ICON":0,"STORE_LINE_NUMBERS":true,"Sound_Error":"","Sound_Info":"","Sound_Success":"","Sound_Warning":"","Speak_Error":false,"Speak_Info":false,"Speak_Success":false,"Speak_Warning":false,"UI_MODE":"Normal"}
Initialising SettingsConsole
Initialising Utils
Initialising Config
Initialising Notifications
Initialising Status
Initialising App
Initialising File
Initialising Code
Initialising Serial
  - Initialising Serial Chrome Serial
  - Initialising Serial Chrome Socket
  - Initialising Serial Noble
  - Initialising Serial Audio
Initialising Terminal
Initialising CodeWriter
Initialising Modules
Initialising Env
Initialising Flasher
Initialising EditorBlockly
Initialising EditorJavaScript
Initialising Send
Initialising MenuPortSelector
Initialising MenuSettings
Initialising MenuFlasher
Initialising SettingsAbout
Initialising SettingsFlasher
Initialising BoardJSON
Initialising VersionChecker
Initialising Compiler
Initialising Assembler
Initialising GetGitHub
Initialising NPMModules
Initialising ExamplePlugin
Initialising Unicode
Initialising SaveOnSend
Initialising Minify
Initialising Tutorial
Initialising Webcam
Initialising FontSize
Initialising UiMode
Initialising URLHandler
Initialising CodeLink
Initialising Project
Initialising Testing
Initialising Notification_Sound
Initialising Tern
Initialising Debugger
Initialising Tour
Initialising SettingsProfile
Initialising HelpLinks
No code in storage.
noble starting scan
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
Found UART device: Puck.js c064 c9:2e:0c:37:c0:64
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
Found UART device: Puck.js c064 c9:2e:0c:37:c0:64
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
>>> Connecting...
Set Slow Write = true
BT> Connecting
BT> ERROR Connecting
ERROR: Unable to open device (connectionInfo=undefined)
ERROR: [notify_error] Connection Failed.
>>> Connection Failed.
Found UART device: Puck.js c064 c9:2e:0c:37:c0:64
Found device: [TV] UE65JU6400 bc:14:85:f2:4d:29
noble stopping scan

From the log, that all looks quite promising.

Do you have a phone that you can use to update the Puck.js firmware with? The new firmware could be a lot better.

Unfortunately out of the box the firmware advertises quite slowly which can make creating a connection unreliable on some devices. If you keep trying then it may actually work for you as-is after a few attempts - but the new firmware would almost certainly fix that.

Yes, I have an android phone with bluetooth. How to update firmware with it?

@Artiom https://www.espruino.com/Puck.js#via-nrf-connect-app-android-
https://www.youtube.com/watch?v=N3CJbl29vy0

I installed nRF Connect on my phone, started puck in red light mode. I see it in the application, I can connect (light turns to green on puck) but no DFU symbol is shown. I just see some properties.

I can connect (light turns to green on puck)

Really Green? Or do you mean blue?

Is it an Android Phone, or iPhone? The iPhone version of nRF connect doesn't have the DFU icon and you need nRF Toolbox (there are instructions at the link above for iPhones)

Yes, to blue. And this is Android. The application I found is this one
https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp
Should I install toolbox instead?

That's strange - it's the right app. Please could you post a screenshot of it when it's connected? It could be a bug in the nordic app I guess.

You could try nRF Toolbox, yes - but nRF connect should really work...

Screenshot

1 Attachment

The font size looks a bit big - do you think it's possible that you have a large font size set in Android, and that has meant that there was no room for the nRF Connect app to add the DFU button?

If you don't want to change that, I'd just use the nRF toolbox instructions - the only reason I suggest nRF connect is that it's a useful app to have when using Puck.js. nRF toolbox is marginally less useful :)

I tried small font and still don't see the button. Toolbox DFU tool didn't work either...

What happened in the case of the Toolbox DFU?

Just error with no explanation. I select the file, the device then upload button and it says dfu file error 2

And you gave it the zip file - not the uncompressed contents of the zip?

Did you get the apps from the Google Play store? all I can think is that for some reason they are out of date.

APPS are taken yesterday from GStore. I don't uncompress the ZIP in DFU file selection there is a choice Multiple Files (ZIP).
nRF Toolbox v1.10.0

By the way: Info on DFU tool says that the content of the zip have to be following:
softdevice.hex bootloader.hex application.hex
And this is not what I see in the zip 1v90: I see .bin .dat and .json

Odd - I see nRF toolbox 2.2.1 reported on the 'About' page, and on the Google Play Store: https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox&hl=en_GB

That could be your problem. Could also be an issue with nRF Connect if you have the older version of that too.

The zip file is fine - you don't need the 3 hex files any more.

Ok, I donwloaded the apk from GIT and it worked! Uploading firmware...

Still the same error: connexion failed:

noble starting scan
Found UART device: Puck.js c064 c9:2e:0c:37:c0:64
Found device:  d4:81:ca:e0:77:90
Found device:  d4:81:ca:e0:77:90
Found device:  d4:81:ca:e0:77:90
Found UART device: Puck.js c064 c9:2e:0c:37:c0:64
Found device:  d4:81:ca:e0:77:90
Found device:  d4:81:ca:e0:77:90
>>> Connecting...
Set Slow Write = true
BT> Connecting
BT> ERROR Connecting
ERROR: Unable to open device (connectionInfo=undefined)
ERROR: [notify_error] Connection Failed.
>>> Connection Failed.
Found device:  d4:81:ca:e0:77:90
Found UART device: Puck.js c064 c9:2e:0c:37:c0:64
Found device:  d4:81:ca:e0:77:90
Found device:  d4:81:ca:e0:77:90
noble stopping scan

I tried it on the linux box from Chromium. Result is slightly different. All the time different. Here is the transcript of several connexions:

No code in storage.
>>> Connecting...
Set Slow Write = true
>>> Connecting to Puck.js c064
BT> Device Name: Puck.js c064
BT> Device ID: t5VB7pAhtyVVCJlk1naOMQ==
BT> ERROR: NetworkError: Connection failed for unknown reason.
ERROR: [notify_error] Connection Failed.
>>> Connection Failed.
>>> Connecting...
Set Slow Write = true
>>> Connecting to Puck.js c064
BT> Device Name: Puck.js c064
BT> Device ID: t5VB7pAhtyVVCJlk1naOMQ==
>>> Connected to BLE
BT> Connected
BT> Disconnected (gattserverdisconnected)
ERROR: [notify_error] Connection Failed.
>>> Connection Failed.
ERROR: [notify_error] Connection Failed.
>>> Connection Failed.
>>> Connecting...
Set Slow Write = true
>>> Connecting to Puck.js c064
BT> Device Name: Puck.js c064
BT> Device ID: t5VB7pAhtyVVCJlk1naOMQ==
>>> Connected to BLE
BT> Connected
BT> Disconnected (gattserverdisconnected)
ERROR: [notify_error] Connection Failed.
>>> Connection Failed.
ERROR: [notify_error] Connection Failed.
>>> Connection Failed.
>>> Connecting...
Set Slow Write = true
>>> Connecting to Puck.js c064
BT> Device Name: Puck.js c064
BT> Device ID: t5VB7pAhtyVVCJlk1naOMQ==
>>> Connected to BLE
BT> Connected
Got ""
No Prompt found, got undefined - issuing Ctrl-C to try and break out
Got ""
No Prompt found, got undefined - issuing Ctrl-C to try and break out
Got ""
No Prompt found, got undefined - issuing Ctrl-C to try and break out
Got ""
No Prompt found, got undefined - issuing Ctrl-C to try and break out
Got ""
No Prompt found, got undefined - issuing Ctrl-C to try and break out

On your Linux box, did you check the BlueZ version and install the correct one? http://www.espruino.com/Web+Bluetooth+On+Linux

No I didn't check the Bluez. I just wanted to compare the behaviour. I need to make it work on my laptop which is unfortunately Window 7, and I can not do much of it. Except if you know a live distribution of linux with the right Bluez version. Live, because I cannot install something on dualboot on this pc.

Ok, on Linux you won't get it working on standard Linux unless you're willing to fiddle with Bluez (although Ubuntu 16.10 might work).

On Windows, do you happen to have two Bluetooth dongles (one internal, one external?). If so, could you try disabling the one you're not using? I'm wondering whether it is interfering somehow.

Also, what is the type of Bluetooth adaptor that you are using? I guess somehow it might be incompatible with Bluetooth LE, but I can't really imagine how

I have only one internal adapter Intel one. I suppose as I can see the puck.js it is BLE compatible.

So I found that the only way of making this works in Windows is to avoid windows ;). I installed Virtualbox with Archlinux (bluez 5.43). And it works out of the box! With all the same hardware.

This internal adaptor is on the USB bus so it can be virtually attached to virtualbox USB hub.