I've ran into another issue. I have no real idea, where this goes wrong and I am not sure if it is me again or a bug.
Let me first show my small scenario: the car starts at a little left from sta1 and moves over to the right in a straight line.
This works when I use the mobility thread like:
The net.plotGraph(max_x=300, max_y=200) shows me the movement of car1, but as my logs point out, car1 is just moving in the GUI, but the net-traffic remains at the same place. It seems like car1-wlan0 is still stuck at 10.0,10.0,0.0, while the car in the GUI is moving. Only sta1 and sta2 see messages from the car.
The telemetry approach also shows the movement. Hence I do something telemetry incompatible in my software, telemetry stops as soon as I start my program inside staX (I can open a Issue for that too).
Hi,
I've ran into another issue. I have no real idea, where this goes wrong and I am not sure if it is me again or a bug.
Let me first show my small scenario: the car starts at a little left from sta1 and moves over to the right in a straight line. This works when I use the mobility thread like:
All my staX logs (from the software there running) show that they've received messages from car1, if it passed them by.
But when I use the socket option or modify the car1.params directly like:
The net.plotGraph(max_x=300, max_y=200) shows me the movement of car1, but as my logs point out, car1 is just moving in the GUI, but the net-traffic remains at the same place. It seems like car1-wlan0 is still stuck at 10.0,10.0,0.0, while the car in the GUI is moving. Only sta1 and sta2 see messages from the car. The telemetry approach also shows the movement. Hence I do something telemetry incompatible in my software, telemetry stops as soon as I start my program inside staX (I can open a Issue for that too).
I also tried to start a emtpy mobility thread:
which makes no difference.
edit: In the meantime, I will play around with replay mobility. I have a feeling that this could help me in fixed scenarios really well :-)