No Longer Can Connect "err connect"

[ben]

Looks good besides the bottom portion of the Ethernet settings, you need to uncheck Use DNS and change the Server IP to whatever is hosting btmon.

[jhenline]

I feel like I'm getting closer...but one problem seems to replaced by another. It seems now that the GEM is providing data to btmon. However, btmon doesn't seem to be able to read the data. I'm getting read errors like:

2015/11/05 02:25:41 read failed: expected START_HEADER0 0xfe, got 0x20
2015/11/05 02:25:41 reading 1 of 1 packets
2015/11/05 02:25:41 read failed: expected START_HEADER0 0xfe, got 0x30
2015/11/05 02:25:41 reading 1 of 1 packets

I found similar posts on the web for "expected START..." and have made so many changes at this point that I don't know what to try next. I'm attaching all the settings as screenshots that I have. I probably have more than one configuration crudded up at this point.

BTMON CONFIG FILE:
--
[source]
device_type = gem
ip_read = true
ip_host = 10.0.0.169
ip_port = 8000
ip_mode = client

[openenergymonitor]
oem_url = http://emoncms.org/input/post
oem_out = true
oem_token = jeffs_super_secret_token
oem_node = 1
--

DEVICE INFORMATION:
Raspberry Pi Address: 10.0.0.176
GEM Address: 10.0.0.169

[ben]

Change Primary Packet Format on the GEM to Bin-48-NET-Time, that'll solve that issue.

[jhenline]

That did it, thanks Ben. Phew! Now, time to learn how to work with emoncms.