Cannot connect to simulator

Former Member over 10 years ago

Hello, I am a computer science student learning the ropes and thought this might be a fun way to learn something different. Anyways, I downloaded the SDK and followed the necessary steps in the "Getting Started" page. The only problem I seem to be having is that even when I have the Connect IQ Device Simulator running, when I run the program the console displays the following messages after the build finishes.

BUILD: Complete
Attempt 1 to connect to simulator...
Attempt 1 to connect to simulator...
Attempt 2 to connect to simulator...
Attempt 2 to connect to simulator...
It does this until the count reaches 5 and then says
Couldn't connect to simulator.

Sorry if this seems like an easy question, but I couldn't find any other forum posts about it. Any advice would be appreciated.

Kyle.ConnectIQ over 10 years ago

Are you on OS X or Windows? What version of the SDK do you have?

AlexDV over 10 years ago

Hi Kyle,

I'm having this same issue. I'm using Mac OSX 10.6.8. I'm using SDK 1.1.2. I've tried uninstalling and reinstalling eclipse and the SDK.
I've been able to get it to work on Win7 desktop, but need it to work on my macbook.

Any ideas I can try?

Thanks,

Alex.

rconradharris over 10 years ago

Hi Kyle,

I'm having this same issue. I'm using Mac OSX 10.6.8. I'm using SDK 1.1.2. I've tried uninstalling and reinstalling eclipse and the SDK.
I've been able to get it to work on Win7 desktop, but need it to work on my macbook.

Any ideas I can try?

Thanks,

Alex.

I've been seeing the same issue.

The simulator seems to get wedged occasionally. In each case though, I've managed to recover by doing a Force-Quit.

Aside: Seems like the simulator is bit more unstable in the latest SDK release. Each debug attempt takes two runs now, one where it crashes inevitably, and then another where it actually runs. The previous SDK release, for all its other warts, didn't have this problem.

Kyle.ConnectIQ over 10 years ago

Hi Kyle,

I'm having this same issue. I'm using Mac OSX 10.6.8. I'm using SDK 1.1.2. I've tried uninstalling and reinstalling eclipse and the SDK.
I've been able to get it to work on Win7 desktop, but need it to work on my macbook.

Any ideas I can try?

Thanks,

Alex.

10.6 is not an officially supported version of OS X. Are you able to manually launch the simulator and app via Terminal?

Start the simulator
<sdk path>/bin/monkeydo <PRG FILE> -d <DEVICE TYPE>

<DEVICE TYPE> can be fenix3, epix, vivoactive, fr920xt.

Kyle.ConnectIQ over 10 years ago

I've been seeing the same issue.

The simulator seems to get wedged occasionally. In each case though, I've managed to recover by doing a Force-Quit.

Aside: Seems like the simulator is bit more unstable in the latest SDK release. Each debug attempt takes two runs now, one where it crashes inevitably, and then another where it actually runs. The previous SDK release, for all its other warts, didn't have this problem.

Can you further describe what's happening with the simulator? Are you using Eclipse to launch the app? If so, is it taking two runs to get the simulator to connect? If you're getting crash logs, could you post them here or send them to [email][email protected][/email] for us to take a look at?

rconradharris over 10 years ago

Can you further describe what's happening with the simulator? Are you using Eclipse to launch the app? If so, is it taking two runs to get the simulator to connect? If you're getting crash logs, could you post them here or send them to [email][email protected][/email] for us to take a look at?

Yep using Eclipse.

So the scenario is:

1. I run application once using 'Run -> Run'

2. I go back to the editor, tweak a value or whatever

3. I run the application again using 'Run -> Run'

4. Simulator crashes with the debug log below[1]. Key line there: "Socket Error in packet header 0"

5. I re-run it without doing anything different, and it works. Hence 2 runs per 'real run'.

_____
[1]

Found Transport: tcp

Connecting...

Connecting to device...

Device Version 0.32.1Device id 0 name "A garmin device"

Shell Version 166723Copying file.... 1% complete

Copying file.... 2% complete

Copying file.... 4% complete

Copying file.... 5% complete

Copying file.... 7% complete

Copying file.... 8% complete

Copying file.... 9% complete

Copying file.... 11% complete

Copying file.... 12% complete

Copying file.... 14% complete

Copying file.... 15% complete

Copying file.... 17% complete

Copying file.... 18% complete

Copying file.... 19% complete

Copying file.... 21% complete

Copying file.... 22% complete

Copying file.... 24% complete

Copying file.... 25% complete

Copying file.... 27% complete

Copying file.... 28% complete

Copying file.... 29% complete

Copying file.... 31% complete

Copying file.... 32% complete

Copying file.... 34% complete

Copying file.... 35% complete

Copying file.... 37% complete

Copying file.... 38% complete

Copying file.... 39% complete

Copying file.... 41% complete

Copying file.... 42% complete

Copying file.... 44% complete

Copying file.... 45% complete

Copying file.... 46% complete

Copying file.... 48% complete

Copying file.... 49% complete

Copying file.... 51% complete

Copying file.... 52% complete

Copying file.... 54% complete

Copying file.... 55% complete

Copying file.... 56% complete

Copying file.... 58% complete

Copying file.... 59% complete

Copying file.... 61% complete

Copying file.... 62% complete

Copying file.... 64% complete

Copying file.... 65% complete

Copying file.... 66% complete

Copying file.... 68% complete

Copying file.... 69% complete

Copying file.... 71% complete

Copying file.... 72% complete

Copying file.... 74% complete

Copying file.... 75% complete

Copying file.... 76% complete

Copying file.... 78% complete

Copying file.... 79% complete

Copying file.... 81% complete

Copying file.... 82% complete

Copying file.... 83% complete

Copying file.... 85% complete

Copying file.... 86% complete

Copying file.... 88% complete

Copying file.... 89% complete

Copying file.... 91% complete

Copying file.... 92% complete

Copying file.... 93% complete

Copying file.... 95% complete

Copying file.... 96% complete

Copying file.... 98% complete

Copying file.... 99% complete

Copying file.... 100% complete

File pushed successfully

Connection Finished

Closing shell and port 

Found Transport: tcp

Connecting...

Connecting to device...

Device Version 0.32.1Device id 0 name "A garmin device"

Shell Version 161690Socket Error in packet header 0

Connection Finished

Closing shell and port

AlexDV over 10 years ago

10.6 is not an officially supported version of OS X. Are you able to manually launch the simulator and app via Terminal?

Start the simulator
<sdk path>/bin/monkeydo <PRG FILE> -d <DEVICE TYPE>

<DEVICE TYPE> can be fenix3, epix, vivoactive, fr920xt.

Hi Kyle,

I tried manually launching, but got an error saying:
/Applications/eclipse/connectiq-sdk-mac-1.1.2/bin/monkeydo: line 11: 330 Illegal instruction "$MB_HOME"/shell --transport=tcp --transport_args=127.0.0.1:$i push "$PRG_PATH" "0:/GARMIN/APPS/$FILE"
/Applications/eclipse/connectiq-sdk-mac-1.1.2/bin/monkeydo: line 11: 332 Illegal instruction "$MB_HOME"/shell --transport=tcp --transport_args=127.0.0.1:$i tvm "0:/GARMIN/APPS/$FILE" $DEVICE_ID

I did a bit more searching and you had replied to someone earlier with a similar issue on 10.6. So I'm in the process of upgrading to 10.10. Once I have everything installed, I'll let you know how it goes.

Regards,

Alex.

Kyle.ConnectIQ over 10 years ago

Yep using Eclipse.

So the scenario is:

1. I run application once using 'Run -> Run'

2. I go back to the editor, tweak a value or whatever

3. I run the application again using 'Run -> Run'

4. Simulator crashes with the debug log below[1]. Key line there: "Socket Error in packet header 0"

5. I re-run it without doing anything different, and it works. Hence 2 runs per 'real run'.

What happens if you launch it via the terminal using monkeydo? Do you run into the same problem?

AlexDV over 10 years ago

Hi Kyle,

I ended up upgrading to Yosemite (10.10.3), and it works fine now.

Regards,

Alex.

Former Member over 10 years ago

binaries not executable

Hi,

So I had the same problem as above (with OS X Yosemite), after updating to the latest SDK version (1.1.3).
The simulator worked before the update, but afterwards I had the above symptoms.
I noticed that the bin folder contained a lot of binaries that were not executable (missing x marker in the command line).
After doing a "chmod +x" for all the files, including the simulator binary in the Connect IQ.app, everything was working again.

Best regards,
Alin