Community

Frank Neuhaus

Hi Jeremy,

sorry, my connection to this forum seems to be quite slow. I wrote the answer before you wrote that you could use the WiFi.

BR
Frank

Frank Neuhaus

Great work! I'm happy to see that this product isn't forgotten after being shipped, but actively worked on.
Yes, it was a very good idea to back this up. Thumbs up for everybody working on this!

BR
Frank

Frank Neuhaus

Hello Boken,

sure, here it is:

root@Omega-1D30:/# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:312 errors:0 dropped:0 overruns:0 frame:0
          TX packets:312 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:21888 (21.3 KiB)  TX bytes:21888 (21.3 KiB)

wlan0     Link encap:Ethernet  HWaddr 40:A3:6B:C1:1D:31  
          inet addr:192.168.3.193  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::42a3:6bff:fec1:1d31/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1129 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1277 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:142643 (139.2 KiB)  TX bytes:231079 (225.6 KiB)

wlan0-1   Link encap:Ethernet  HWaddr 42:A3:6B:C1:1D:31  
          inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
          inet6 addr: fe80::40a3:6bff:fec1:1d31/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:6276 (6.1 KiB)

I've rebooted in between, that's why the IP changed.

BR
Frank

EDIT: Changed format.

EDIT2: Obviouly the IP is continuously changing, I think every time it tries to re-associate. But that's does not exactly explain the broken rules in the first setup - I'll just play around with that now… [EDIT: Must have been a change during getting the example… routes fit to the IPs.]

EDIT2^n:

I've just done the following:

[21:09:59  5.11.2015] [frank@waffeleisen] [/home/frank]
% sudo iw dev wlan0 scan | grep SSID
        SSID: Schillerstrasse
        SSID: SchnurlosesNetzwerk
        SSID: Funkkiste SGV Blockhaus
        SSID: Funkkiste SGV
        SSID: WLAN-E7B142

No, I did not change the SSID of my Omega. And the Laptop is standing directly next to the Omega.

P.S.: Connecting to another AP I opened using my mobile (OnePlus One) worked just fine…

EDIT 2^n +1: Most likely my last edit for today, which now might help other people as well. Hopefully.
I've just set my router to only support 802.11b/g (so without n!), and it works. Maybe a problem of the router; I'll test that tomorrow when I'm at a place with another 802.11b/g/n network.

Frank Neuhaus

Hi,

F***. I was in a hurry when reading and replying the last time, so I just overlooked mark-titley's answer. This is, of course, my fault, and I'm sorry for that.
And thanks a lot to mark-titley for solving my question!

BR
Frank

Frank Neuhaus

Hi Luciano,
thanks for your answer. I'm aware of this option, but my question is if I'm doing something wrong or if my dock somehow is defective.
BR
Frank

Frank Neuhaus

Update:

The omega seems to start without problems in the battery dock as I can see the access point it creates.

BR
Frank

Edit:
Also works with Mini-Dock. I get more and more the feeling that something is wrong with my battery dock.

Frank Neuhaus

Hi everybody,

not long ago I received my GPS module and my battery dock, and I am very happy about that. Thanks a lot for your great work!

But now I have a problem… when I connect the battery dock to my computer (ThinkPad T520, Debian stable), it won't find anything. The output of 'dmesg' just does not change at all, but the battery charges. I did not check yet if the Omega will connect to my network to see if it is properly running at all. Regarding the LED it seems to be working.

When I'm using the normal dock, it's found immediately and working fine ("cp210x converter now attached to ttyUSB0"). I've also tried to only use the Omega together with the dock but not connecting anything else: Did not change the result.

So what's going wrong here? Where is my mistake? Can anybody help me?

Thanks a lot in advance and have a nice day!

BR
Frank

Frank Neuhaus

Hi Tony,

maybe you ordered the battery dock? That is one item, and if you did not additionally ordered a "normal" dock, than this is correct although it's too bad for you.

In addition I have another short question:
I'm missing the GPS and battery. If the GPS is finished before the GPS (and that's what I expect), will they be shipped separately or together as soon as the battery dock is ready?
Somehow I can understand the following sentence from the linked page differently:

If your order includes any of the items listed below OLED in the table below, we will be splitting your order into 2 shipments so we can send you whatever we have ready ASAP.

And I'm really looking forward to the GPS.
But please don't get me wrong… I don't want to blame anybody or anything else… I'm just curios.

BR
Frank

Frank Neuhaus

Great work! I'm happy to see that this product isn't forgotten after being shipped, but actively worked on.
Yes, it was a very good idea to back this up. Thumbs up for everybody working on this!

BR
Frank

Frank Neuhaus

Hi Doom,

maybe you ordered a battery dock? If I got it right they were not shipped yet…

BR
Frank

Frank Neuhaus

Hello everybody,

I've decided to make a new reply.
Minutes ago I've tested to connect my Omega and my T520 without limitations to the 802.11b/g/n. What shall I say? It just works fine for both devices, so there seems to be some problem with my router at home.
Therefor I'd say that this problem is solved.
Thanks to everybody who helped me!

BR
Frank

Frank Neuhaus

Hi,

I've had a similar situation and I played around with it.
Do you use 802.11n? For me falling back to 802.11b/g instead of 802.11b/g/n solved the problem.
If it's the routers fault I don't know, but I would not wonder in my case. Will report more tomorrow when I can test another router.

BR
Frank

Frank Neuhaus

Hello Boken,

sure, here it is:

root@Omega-1D30:/# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:312 errors:0 dropped:0 overruns:0 frame:0
          TX packets:312 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:21888 (21.3 KiB)  TX bytes:21888 (21.3 KiB)

wlan0     Link encap:Ethernet  HWaddr 40:A3:6B:C1:1D:31  
          inet addr:192.168.3.193  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::42a3:6bff:fec1:1d31/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1129 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1277 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:142643 (139.2 KiB)  TX bytes:231079 (225.6 KiB)

wlan0-1   Link encap:Ethernet  HWaddr 42:A3:6B:C1:1D:31  
          inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
          inet6 addr: fe80::40a3:6bff:fec1:1d31/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:6276 (6.1 KiB)

I've rebooted in between, that's why the IP changed.

BR
Frank

EDIT: Changed format.

EDIT2: Obviouly the IP is continuously changing, I think every time it tries to re-associate. But that's does not exactly explain the broken rules in the first setup - I'll just play around with that now… [EDIT: Must have been a change during getting the example… routes fit to the IPs.]

EDIT2^n:

I've just done the following:

[21:09:59  5.11.2015] [frank@waffeleisen] [/home/frank]
% sudo iw dev wlan0 scan | grep SSID
        SSID: Schillerstrasse
        SSID: SchnurlosesNetzwerk
        SSID: Funkkiste SGV Blockhaus
        SSID: Funkkiste SGV
        SSID: WLAN-E7B142

No, I did not change the SSID of my Omega. And the Laptop is standing directly next to the Omega.

P.S.: Connecting to another AP I opened using my mobile (OnePlus One) worked just fine…

EDIT 2^n +1: Most likely my last edit for today, which now might help other people as well. Hopefully.
I've just set my router to only support 802.11b/g (so without n!), and it works. Maybe a problem of the router; I'll test that tomorrow when I'm at a place with another 802.11b/g/n network.

Frank Neuhaus

@Frank Neuhaus

Best posts made by Frank Neuhaus

Latest posts made by Frank Neuhaus