I recently bought Sphero 2.0 and playing with it on iPad with no problems.
Now I want try to develop some apps with Mac SDK however I am not able to connect my Sphero with my Mac Mini 2012 nor Macbook Pro 2013 Retina. I open Bluetooth settings, I see Sphero-YRG click to "Pair", it shows for two seconds "Connected" and after that "Not connected".
After this pairing process I can still click on "Not connected" Sphero bluetooth device, after few seconds it turned into "Connected" and again after two seconds its "Not connected". I doubted that it really gets to connected state because Sphero won't start light with that blue-white as it does when it connects to my iPad.
This is output from /var/log/system.log :
Feb 3 21:19:11 Pavel-Mac-mini.local blued[83]: Save link key for device: 68-86-e7-00-25-b8
Feb 3 21:19:12 Pavel-Mac-mini.local BluetoothUIServer[3420]: setAudioDevice:kAudioDeviceUnknown
Feb 3 21:19:12 Pavel-Mac-mini.local BluetoothUIServer[3420]: Failed to set the device Sphero-YRG
Feb 3 21:19:13 Pavel-Mac-mini kernel[0]: [0xffffff8058432e00][free]()
What worked for me is quickly running some code using the Sphero during the short interval while it shows "connected" in the Bluetooth settings.
Connect Sphero. It will automatically disconnect, stupid.
ls /dev | grep Sphero shows the name of the port which was associated with the device. Use the tty one (in my case, /dev/tty.Sphero-BOY-AMP-SPP).
Paste the port name into your code, so you can run it quickly.
Remove Sphero from the Bluetooth settings UI.
Choose to pair with the Sphero again, and immediately run your code using it. Now it stays connected and the connection is usable and stable.
The Mac SDK looks like its last update was about a year ago, which would mean that the SDK has not been updated to be able to see or connect to the Sphero 2.0 ball correctly. That being said, the Mac SDK is actually an unofficial SDK, and therefore is not directly supported by us. I will make sure that this gets forwarded to the correct people, and will get you some more information when I know more.
You could try using artoo open source framework to connect and control your sphero from your computer.
Here you can find a tutorial on how to do it: https://github.com/hybridgroup/artoo/wiki/1.3.2.-Sphero
If you don't want to use ruby, you could use http://cylonjs.com with javascript too.
Related
I have recently started to have a deeper look into Wi-Fi Direct under Windows 10 (desktop version) and had a look into the API descriptions
from Microsoft => https://msdn.microsoft.com/en-us/library/windows/desktop/dn457945(v=vs.85).aspx
One of the described methods there (WFDStartOpenSession) states that a previous pairing through the "Windows Pairing experience" (WPS ?) is required.
So i started to play a little bit with the pairing stuff by using a Windows 10 (Build 1607, Desktop) together with an Android-based smartphone (version 6.0.1) and
made the following observations:
When i initiate the connection from my PC to the phone, it "basically" works i.e. the pairing dialog shows up on the phone's display and i can connect to it.
Although it works, it's not really stable in my opinion - on my side it works 1 out of 3 times.
After ~ 30 seconds, Windows disconnects from the phone (in the "Devices and printers" view) while the phone itself stays connected a little longer (then it also disconnects).
When i initiate the connection from my phone to the Windows PC, nothing happens - no message box, no pop-up window :-(
Has anybody else seen this or similiar behavior ?
I tried it with 2 different USB adapters, one with a RTL8723BU chipset from Realtek and the other one with a RT5572 chipset from Mediatek Ralink - both show
exactly the same behavior.
In addition, i noticed that the "Realtek Wireless Lan Utility" to control and configure the USB adapter is not working anymore in Windows 10 (1607) when switching
from client to Access Point mode. I think it's somehow related to ICS, missing hosted network support ... don't know yet.
However, actually you don't need the tool from Realtek as you can for example use the mobile hotspot feature of Windows 10 to share your internet connection with your devices.
But without the Realtek tool i have not found any possibility to switch WiFi channels - does anybody have the same problem ? is there are solution available for that ?
Thanks
Goodmorning,
I'm working quite hard on my own app. At this point I want to run it on my android (galaxy note 3) phone. Unfortunately Appcelerator studio doesn't detect my android phone; Windows does. I've tried it with the new Galaxy s7 of a friend, but same result.
Off course I searched the web like crazy and found several possible (old) answers, but none did the magic.
When I consult the log, there's no new info to be read!
Does anyone have a clue where to look? Looking forward to your answers…
Kind regards!
One thing you should check is if you have set up your phone for development. You can see the instructions here: http://developer.android.com/tools/device.html (... tap 7 times... - took me a while to discover!)
And the small obvious thing is in Appcecelerator Studio you may need to select "Refresh devices" when you try to run the project.
/John
When you say "Windows" detects it, what exactly do you mean? Does adb detect it?
If you run
adb devices
on the command line, does it report your device ID?
On my Mac, I run this and I can see my connected S4:
List of devices attached
9726ea90 device
I'm assuming that the Windows version of adb would output a similar report.
With all the Samsung phones I've debugged with, I always have to go to the notification bar and choose "connect as media device" (or something similar). The default connection mode does not work for debugging. And unfortunately, you have to do this every time you connect the device.
I enabled debugging over bluetooth on my Moto 360
and enabled Android Wear app on my Nexus4.
Status displays target : disconnected
Forwarding the port from my computer shows the status host will be changed to connected, but the target status remains disconnected.
I toggled debug via the bluetooth switch which had no effect.
My phone is a Nexus 4. Is there a problem with my phone or the Moto 360?
I eventually managed to get it working. The issue seems to be related to having paired your device with an emulator first. Take a look at this post to see how I fixed it: http://melix.github.io/blog/2014/10/android-moto360.html
open the applications settings, search for the Android Wear application, then force stop it
clear its data and cache
Search for Google Play Services
Click on Manage space. Delete all data.
reboot your phone
reset your Moto 360
Pair watch with phone
Following the instructions from android.com https://developer.android.com/training/wearables/apps/bt-debugging.html to setup debugging and it should work now.
Done.
I tried it on a Sony z1.
It succeeded without any problems.
So, maybe it's not supported perfectly in Nexus 4.
If you have the same problem, I suggest using another device.
I fixed without factory reset with these steps
-Force stop android wear application and clear cache
-Disconnect emulator on android wear app
-Forget emulator on android wear app
-Connect your real device via bluetooth
-Open debugging over bluetooth
Make sure that debugging options are also active in android wear device
Run this commands in command window:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
I have an app installed on Android Wear Emulator that I can directly run from Start->MyApp. However when I want to start it with voice command i.e. Start MyApp, it keeps waiting for something but does not complete. What could be reason for this?
There is a limitation of the current emulator that it does not support voice actions via the keyboard, even though the text appears on the display. You will need to start the application by clicking on the display, then the red G, and then going to the start menu and picking the app from there. You can also quickly start the application using something like this from your development machine:
adb shell am start -n com.example.android.test/.TestActivity
The watch needs to be connected to a phone (device or emulator) with an internet connection for the voice commands to work.
Has anyone gotten the Sample BasicDriveApp App working in Windows 8?
https://github.com/orbotix/Sphero-Win-SDK
When I build and run the Project I get a message "No Sphero is connected" and when I try to connect the Sphero via Windows 8 Bluetooth it does not work.
Can anyone offer any tips?
Thanks.
John.
It indeed works, I've had some problems with connectivity myself, however.. process I use to restore if all goes awry:
Refresh Sphero (return to base for sleep mode, wait a few seconds, wake up)
Refresh Bluetooth in Windows (off / on) without connecting to Sphero
Open your app, wait for it to connect. It'll find Sphero and automatically dig in if all goes well.
[Update]
It appears Windows 8.1 doesn't really know what to do with Sphero. It has a hard time reconnecting after the connection is lost, even if you close all instances of the app and toggle through Bluetooth.