Team,
I've created a simple demo to illustrate the unexpected behavior I'm seeing.
Using the EMANE tutorial (https://github.com/adjacentlink/emane-tutorial) I've
created a new directory 10/ and modified the Makefile according to my scenario,
using the ieee80211abg model (I can provide the entire scenario tar.gz as
attachment if requested):
----
Node1 (platform1.xml)
NEM1
|
| (subid 1)
|
NEM2
Node2 (platform2.xml - defines 2x NEMs)
NEM3
|
| (subid 2)
|
NEM4
Node3 (platform3.xml)
----
I have a simple EEL script that assigns a GPS lat,long,alt for each of the 4
NEMs (NEM2 and 3 are assigned the *same* lat,long,alt since they are in the
same node) at time 0 and doesn't change:
0.0 nem:1 location gps 40.031290,-74.523095,10.000000
0.0 nem:2 location gps 40.034566,-74.518008,20.000000
0.0 nem:3 location gps 40.034566,-74.518008,20.000000
0.0 nem:4 location gps 40.036018,-74.511500,30.000000
I 'make' and 'sudo ./demo-start' and all comes up as expected - links show in
the olsrlinkview.py application. BUT ...
GPS coordinates don't seem to align correctly. Using emanesh shows the correct
information:
[emanesh (node-2:47000)] ## get table nems phy LocationEventInfoTable
nem 2 phy LocationEventInfoTable
| NEM | Latitude | Longitude | Altitude | Pitch | Roll | Yaw | Azimuth |
Elevation | Magnitude |
| 1 | 40.03129 | -74.523095 | 10.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0
| 0.0 |
| 2 | 40.034566 | -74.518008 | 20.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0
| 0.0 |
| 3 | 40.034566 | -74.518008 | 20.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0
| 0.0 |
| 4 | 40.036018 | -74.5115 | 30.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0
| 0.0 |
nem 3 phy LocationEventInfoTable
| NEM | Latitude | Longitude | Altitude | Pitch | Roll | Yaw | Azimuth |
Elevation | Magnitude |
| 1 | 40.03129 | -74.523095 | 10.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0
| 0.0 |
| 2 | 40.034566 | -74.518008 | 20.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0
| 0.0 |
| 3 | 40.034566 | -74.518008 | 20.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0
| 0.0 |
| 4 | 40.036018 | -74.5115 | 30.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0
| 0.0 |
However, using cgps on node-3, I see the coordinates for NEM-3 (which are also
the same as NEM-2), but not the coordinates for NEM-4 which is the NEM defined
in node-3 platform3.xml file:
> cgps node-3
[...]
│ Latitude: 40.034565 N
| Longitude: 74.518006 W
│ Altitude: 65.6 ft
[...]
(note: 65.6 feet = 20 meters)
Also, the olsrlinkview.py application, while showing the links as per my
stellar ASCII art diagram above, shows the nodes 2 and 3 with the same GPS
locations - (probably because it's reading the GPSd socket at UDP 2947 same as
cgps?) - I believe it should show node-3 at the NEM4 GPS locations from the EEL
file above.
QUESTION:
I understand "EMANE" (probably emaneeventd on the node's LXC) receives the EEL
events and processes them - and then sends the appropriate location event onto
GPSd via the pseudo terminal created.
* Is the NEM number somehow sent as well?
* It seems from my observations that the node number (platform#.xml) is
being mixed up with the actual NEM ID?
* Am I misinterpreting behavior or the documentation?
Cheers,
Michael J. Vincent
Lead Network Systems Engineer | The MITRE Corporation | Network Technology &
Security (T864) | +1 (781) 271-8381
_______________________________________________
emane-users mailing list
[email protected]
https://publists.nrl.navy.mil/mailman/listinfo/emane-users
