expected START_HEADER0 0xfe, got nothing

Post any 3rd party software here.
Post Reply
seanwg
Posts: 9
Joined: Fri Jul 04, 2014 4:02 pm

expected START_HEADER0 0xfe, got nothing

Post by seanwg » Fri Jul 04, 2014 11:40 pm

Hi

So I took the plunge, and bought a GEM WIFI. I've been tinkering with it a bit.

I'm trying to get btmon.py working. The GEM is in I guess "monitor" mode ---

btmon.py connects but gets this. Any idea:

^Csean@X~/p % ./btmon.py --ip-mode=client --ip --ip-host=X--print -p-port=80 --device-type=gem
2014/07/04 22:35:46 btmon: 3.0.7
2014/07/04 22:35:46 python: 2.7.2+ (default, Jul 20 2012, 22:12:53)
[GCC 4.6.1]
2014/07/04 22:35:46 platform: linux2
2014/07/04 22:35:46 device type: gem
2014/07/04 22:35:46 device list: ['']
2014/07/04 22:35:46 packet format: gem48ptbin
2014/07/04 22:35:46 schema: counters
2014/07/04 22:35:46 SOCKET: timeout: 60
2014/07/04 22:35:46 SOCKET: server host: X
2014/07/04 22:35:46 SOCKET: server port: 80
2014/07/04 22:35:57 expected START_HEADER0 0xfe, got nothing
2014/07/04 22:37:02 expected START_HEADER0 0xfe, got nothing
2014/07/04 22:38:12 expected START_HEADER0 0xfe, got nothing
2014/07/04 22:39:17 expected START_HEADER0 0xfe, got nothing

And thats it. Any ideas?

Sean
sandeen
Posts: 41
Joined: Fri Jan 10, 2014 3:33 pm

Re: expected START_HEADER0 0xfe, got nothing

Post by sandeen » Mon Jul 07, 2014 8:36 am

seanwg wrote:sean@X~/p % ./btmon.py --ip-mode=client --ip --ip-host=X--print -p-port=80 --device-type=gem
Did you really do "-p-port=80" or is that a typo? Should be --ip-port (with 2 leading dashes)

Is the gem in "real-time" mode or not? I think you need it to be if you want btmon to act as the client.

As for the port, I can't tell from the docs how to set the port that it broadcasts on in realtime mode, and I don't have a gem, sorry. but http://lancet.mit.edu/mwall/projects/po ... config-gem shows an example of --ip-port=5000 - so I guess that's settable somewhere in the gem config. I'm guessing 80 isn't correct, but I'm just guessing, sorry.
ben
Site Admin
Posts: 4262
Joined: Fri Jun 04, 2010 9:39 am

Re: expected START_HEADER0 0xfe, got nothing

Post by ben » Mon Jul 07, 2014 10:26 am

seanwg wrote:Hi

So I took the plunge, and bought a GEM WIFI. I've been tinkering with it a bit.

I'm trying to get btmon.py working. The GEM is in I guess "monitor" mode ---

btmon.py connects but gets this. Any idea:

^Csean@X~/p % ./btmon.py --ip-mode=client --ip --ip-host=X--print -p-port=80 --device-type=gem
2014/07/04 22:35:46 btmon: 3.0.7
2014/07/04 22:35:46 python: 2.7.2+ (default, Jul 20 2012, 22:12:53)
[GCC 4.6.1]
2014/07/04 22:35:46 platform: linux2
2014/07/04 22:35:46 device type: gem
2014/07/04 22:35:46 device list: ['']
2014/07/04 22:35:46 packet format: gem48ptbin
2014/07/04 22:35:46 schema: counters
2014/07/04 22:35:46 SOCKET: timeout: 60
2014/07/04 22:35:46 SOCKET: server host: X
2014/07/04 22:35:46 SOCKET: server port: 80
2014/07/04 22:35:57 expected START_HEADER0 0xfe, got nothing
2014/07/04 22:37:02 expected START_HEADER0 0xfe, got nothing
2014/07/04 22:38:12 expected START_HEADER0 0xfe, got nothing
2014/07/04 22:39:17 expected START_HEADER0 0xfe, got nothing

And thats it. Any ideas?

Sean
Did you happen to enter Setup Mode on the GEM and not exit after? It can take up to 5 minutes for it to start sending packets again if you don't click the "Exit Setup Mode" button.

Using the GEM Network Utility, can you attach a screenshot of your WiFi setup?

Ben
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Post Reply