Can't see Element in Kinoma Code device list

edited May 2016 in Kinoma Element

Hi Kinoma,

I'm trying to get my Kinoma Element working, but having a difficult time.

First I connected to the Element's WiFi network, loaded up Kinoma Code and waited to see the Element appear in the devices panel. Here is the log from the Element's Serial Console:

starting... FW version: 2.0.0 (Tue May 10 2016 04:06:29 GMT ())
mc_env_load: mc_fopen /k1/wifi failed. 2
mc_env: initializing /k1/wifi
connecting: UAP...
connected: 192.168.0.1 [0050430395b7]
inetd: starting... mode = 2
inetd: starting udp:6969
inetd: starting tcp:2323
inetd: starting tcp:10000
inetd: starting tcp:8081
inetd: running
[Kinoma Element-0050430395b7]$ wifi: notification: 5
StudioHTTPServer: onRequest: /description
from: 192.168.0.2:52197
StudioHttpService: calling description
inetd: closing instance for 10000

Kinoma Code shows nothing in the devices panel. The element did show up at 192.168.0.1 in the net scanner panel, but I wasn't really able to do anything from there.

Then I tried to connect the Element to my home network, and connect my laptop to the home network and see if it appears in the Kinoma Code Devices panel. Here's the serial console log:

starting... FW version: 2.0.0 (Tue May 10 2016 04:06:29 GMT ())
connecting: <My Home Network SSID>...
connected: 192.168.1.33 [0050430395b7]

Again, I can't see anything in the devices tab (only the Kinoma Create Simulator). I see the Element in the net scanner panel at 192.168.1.33. When I head to 192.168.1.33:10000/description in my browser I get:

{"firmware":"2.0.0","version":"7.1.41","name":"Kinoma Element-0050430395b7","debugShell":"true","id":"com.marvell.kinoma.launcher.element","studio":{"version":"1.3.49","locked":false,"compile":"always","install":"always","profile":false},"xsedit":true}

The log from Kinoma Code when I run it while connected to a network which the Element is connected to:

$ /Applications/Kinoma\ Code.app/Contents/MacOS/Kinoma\ Code 
2016-05-25 23:21:06.859 Kinoma Code[14440:507] CoreText performance note: Client called CTFontCreateWithName() using name "Menlo" and got font with PostScript name "Menlo-Regular". For best performance, only use PostScript names when calling this API.
2016-05-25 23:21:06.859 Kinoma Code[14440:507] CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
2016-05-25 23:21:06.861 Kinoma Code[14440:507] CoreText performance note: Client called CTFontCreateWithName() using name "Open Sans" and got font with PostScript name "OpenSans". For best performance, only use PostScript names when calling this API.
2016-05-25 23:21:06.863 Kinoma Code[14440:507] CoreText performance note: Client called CTFontCreateWithName() using name "Open Sans Semibold" and got font with PostScript name "OpenSans-Semibold". For best performance, only use PostScript names when calling this API.
onSerialRegistered: {"vendor":4742,"product":32896,"name":"Kinoma Element","path":"/dev/cu.usbmodem1a121"}
onZeroconfServiceUp {"name":"Kinoma Element-0050430395b7","type":"_kinoma_setup._tcp.","host":"Kinoma\\032Element-0050430395b7.local.","ip":"192.168.1.33","port":8081,"interfaceIndex":4,"txt":{"uuid":"00023A42-3A42-1002-9802-0050430395b7"}} en0
schema not mapped: _kinoma_setup._tcp.
onSSDPServerUp {"type":"urn:schemas-kinoma-com:device:shell:1","uuid":"00023A42-3A42-1002-9802-0050430395b7","url":"http://192.168.1.33:10000/","interface":"192.168.1.12","interfaceName":"en0","services":[]}
onDeviceUp Kinoma Element-0050430395b7 en0
addInterface: 00023A42-3A42-1002-9802-0050430395b7 en0 -> 1
### doOpenURL netscanner://_kinoma_setup._tcp./Kinoma%20Element-0050430395b7
### doOpenURL netscanner://00023A42-3A42-1002-9802-0050430395b7/192.168.1.12

Any ideas?

Cheers, Harry

Answers

  • Hello,

    I just tried with a different Element device, different laptop, different WiFi network - still no luck.

    Here's the report from port 10000 /description:

    {"firmware":"2.0.2","version":"7.1.41","name":"k5-00504303912c","debugShell":"true","id":"com.marvell.kinoma.launcher.element","studio":{"version":"1.3.49","locked":false,"compile":"always","install":"always","profile":false},"xsedit":true}
    

    Cheers, Harry

  • First thing to do is make sure you're using the latest version of Code. It should be 1.0b5 (build 7.1.74). Since you have seen this on multiple laptops, I recognize that it's probably up to date. But ya gotta make sure, especially since Code does not yet have auto-update.

    In the Preferences you can now enable or disable whether various classes of devices are discovered. Can you open Kinoma Code Preferences and twirl down DEVICES and Discovery and make sure "Kinoma Element" is switched on in there?

    Also, can you download Kinoma Studio (http://kinoma.com/develop/studio/) and check whether Studio can see it in the same way? (You'll need Java SE Development Kit 1.7 or later.) Create a new Application; the Application editor has the device list.

  • Hi KinomaMJ,

    Thanks for your response!

    Checked the version of Kinoma Code. It was 1.0b5 (build 7.1.74).

    Checked the preferences menu. Kinoma Element was enabled.

    Tried Kinoma Studio. Created an application. Waited for the Element to appear in the list of devices. Pressed refresh several times. No luck.

    Manually added the device with its IP address. After about 20 seconds it showed the Kinoma Element icon, FW version and the serial number of the device.

    I'm unable to run an example application on it however... Nothing really happens when I click "Run".

    If I click "Run" on the simulator, the program starts running and the view switches to Kinoma Debug.

    Cheers, Harry

  • Hello,

    I'm still waiting on help with this issue. I live in Sunnyvale, CA and would be willing to meet up with someone from Kinoma to debug.

    Cheers, Harry

  • Good afternoon Harry,

    My apologies that your post fell through the cracks last week. I've got several Engineers digging into the thorough information you've provided. I'll keep an eye on this thread to make sure this gets resolved soon.

    Thanks,

    Will

  • Hi Harry,

    We're still looking through the log files you included above (thanks for that) and trying to sort out what's happening here. The usual culprit in things like this is a router configuration that blocks multicast packets -- but that doesn't seem to be the case here based on the logs.

    Is there anything uncommon about the network you're seeing this issue on? I know you mention in your post that you've tried this with multiple laptops and on multiple Wi-Fi networks... are there any commonalities between the networks that stand out? Just trying to think through the possibilities here.

    Thanks!

    — Andy

  • Hi Andy,

    no WiFi network restrictions that I know of. I have used UPnP to set up devices on my network before, so broadcast packets should be able to get through.

    Kinoma Code's logs clearly shows that it found the device at the correct IP address. It just didn't show up in the device list. This suggests it's not a networking issue, right?

    Also, I can't even get Kinoma Code to show the device when I use the Kinoma Element in AP mode and connect to it directly.

    What is the meaning of the log line "schema not mapped: _kinoma_setup._tcp."?

    Still willing and interested in meeting up with someone on the Kinoma team to debug this :)

    Cheers, Harry

  • Hey Harry,

    I'm about out of better ideas. Can you shoot me an email at acarle@kinoma.com — let's setup a time for you to stop by the office or something similar.

    — Andy

  • I am seeing something similar I think. I have 1 Create and 3 Elements. I had them all visible in the Device list in Kinoma Code and Kinoma Studio. Came home today, fired up my laptop and can only see the Create in Kinoma Code's device list. I see all the devices shells in the network scan. Kinoma Studio see's all 4 devices. What is happening?

Sign In or Register to comment.