Sumo mobility file being read incorrectly

[Boong Baang]

I generate a SUMO scenario "circle_50U.tcl" and use it in place of the default scenario of "vanet-routing-compare.cc". I have a header in BSM "loc-header.cc" that includes the location of the sender in the packet when transmitting. I also use "ns2-mobility-trace.cc" to write out the actual locations of all the vehicles from file "circle_50U.tcl" and save it as "Loc_Circle_50U". 

When I compare the content of BSM header that has location information, it doesn't match with the location generated with  "ns2-mobility-trace.cc". And it differs by a big value, more than what the queueing and transmission delay would have affected it.

In "bsm-application.cc", I wait until some time to start the broadcast. Am I write in assuming that the vehicles start moving from t=0 in the simulation ?

I am attaching the codes I am using, if anyone could have a look at it and help me find the source of the issue, I will be very grateful. Bulk of my modification is with "bsm-application.cc". Inside "vanet-routing-compare.cc", I hardcode the mobility file. 

The files with the names as above can be found here in google drive.

Due to the way the scenario is set up, run it using the command

./waf --run "vanet-routing-compare --totaltime=232 --nodes=50 m_scenario=2 m_mobility=1 protocol=0 "

Broadcast starts at 175 seconds, I start recording received packets from 225 seconds.