Error ([Errno 111] Connection refused) in veins (sumo-launchd.py)

[عبدالمؤمن كاظم‎]

Hello every one :)

When i run sumo-launchd.py (after opening OMNet++ and start simulation) in the terminal, i get the following issue, which i believe is Python related.

bluemix@blueMix:~/SUMO/veins-2.1/examples/veins$ python /home/bluemix/SUMO/veins-2.1/sumo-launchd.py -vv -c /home/bluemix/SUMO/sumo-0.19.0/bin/sumo
Logging to /tmp/sumo-launchd.log
Listening on port 9999
Connection from 127.0.0.1 on port 45234
Handling connection from 127.0.0.1 on port 45234
Got TraCI message of length 2
Got TraCI command of length 1
Got TraCI command 0x0
Got CMD_GETVERSION
Got TraCI message of length 314
Got TraCI command of length 309
Got TraCI command 0x75
Got CMD_FILE_SEND for "sumo-launchd.launch.xml"
Got CMD_FILE_SEND with data "<launch>
  <copy file="erlangen.net.xml"/>
  <copy file="erlangen.rou.xml"/>
  <copy file="erlangen.poly.xml"/>
  <copy file="erlangen.sumo.cfg" type="config"/>
  <basedir path="/home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/examples/veins/"/>
  <seed value="0"/>
</launch>
"
Creating temporary directory...
Temporary dir is /tmp/sumo-launchd-tmp-2JQTRd
Base dir is /home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/examples/veins/
Seed is 0
Finding free port number...
Claiming lock on port
...found port 41320
Starting SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320, seed 0
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 1)
Error ([Errno 111] Connection refused)
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 2)
Error ([Errno 111] Connection refused)
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 3)
Error ([Errno 111] Connection refused)
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 4)
Error ([Errno 111] Connection refused)
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 5)
Error ([Errno 111] Connection refused)
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 6)
Error ([Errno 111] Connection refused)
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 7)
Error ([Errno 111] Connection refused)
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 8)
Error ([Errno 111] Connection refused)
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 9)
Error ([Errno 111] Connection refused)
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 41320 (try 10)
Error ([Errno 111] Connection refused)
Releasing lock on port
Cleaning up
Result: "<?xml version="1.0"?>
<status>
    <exit-code>-1</exit-code>
    <start>1390404178</start>
    <end>1390404189</end>
    <status>Could not connect to SUMO ([Errno 111] Connection refused). Might be protected by a personal firewall or crashed before a connection could be established.</status>
    <stdout><![CDATA[Loading configuration... done.
]]></stdout>
    <stderr><![CDATA[Error: Empty edges in roundabout.
Quitting (on error).
]]></stderr>
</status>
"

and the information from OMNeT++ console:

<!> Error in module (TraCIScenarioManagerLaunchd) scenario.manager (id=6) at event #1, t=0: Model error: Connection to TraCI server lost. Check your server's log. Error message: 104: Connection reset by peer.

TRAPPING on the exception above, due to a debug-on-errors=true configuration option. Is your debugger ready?

Simulation terminated with exit code: 2

Am using SUMO 0.19.0, veins 2.1, and OMNet++ 4.3.1, Linux UbuntuGnome 13.04 x64-bit.

Thanks in advance :)

 

[Christoph Sommer]

On 2014-01-24 10:45, عبدالمؤمن كاظم wrote:
> bluemix@blueMix:~/SUMO/veins-2.1/examples/veins$ python
> /home/bluemix/SUMO/veins-2.1/sumo-launchd.py -vv -c
> /home/bluemix/SUMO/sumo-0.19.0/bin/sumo

[...]

> <stderr><![CDATA[Error: Empty edges in roundabout.
> Quitting (on error).
> ]]></stderr>

[...]

> Am using SUMO 0.19.0, veins 2.1, and OMNet++ 4.3.1

Unfortunately, Veins 2.1 is not (yet) compatible with SUMO 0.19.

I'm afraid you need to manually fix the problem (it should be as simple
as removing the offending roundabout and allowing TraCI to use SUMO
0.19.0), downgrade to SUMO 0.18, or wait for a new version of Veins.


Best,

Christoph

--
Dr.-Ing. Christoph Sommer
Institute of Computer Science
University of Innsbruck, Austria
Phone: +43 512 507-53285 / Fax: -53079
http://ccs.uibk.ac.at/~sommer/

[عبدالمؤمن كاظم‎]

Actually, i spent the whole day trying to manually fix the problem by using explicit host and port numbers, i thought the connection was refused because port number didn't match :)

OK, now, i'll use the older version of SUMO (0.18).

Thanks for your answer Sommer :)

By the way, can you told me when the new version of veins would be released?

[عبدالمؤمن كاظم‎]

Now, i installed SUMO 0.18.0, and did make install.

After executing in the terminal, i get the following:

bluemix@blueMix:~/SUMO/veins-2.1/examples/veins$ python /home/bluemix/SUMO/veins-2.1/sumo-launchd.py -vv -c /home/bluemix/SUMO/sumo-0.18.0/bin/sumo

Logging to /tmp/sumo-launchd.log
Listening on port 9999

Connection from 127.0.0.1 on port 56921
Handling connection from 127.0.0.1 on port 56921

Got TraCI message of length 2
Got TraCI command of length 1
Got TraCI command 0x0
Got CMD_GETVERSION
Got TraCI message of length 314
Got TraCI command of length 309
Got TraCI command 0x75
Got CMD_FILE_SEND for "sumo-launchd.launch.xml"
Got CMD_FILE_SEND with data "<launch>
  <copy file="erlangen.net.xml"/>
  <copy file="erlangen.rou.xml"/>
  <copy file="erlangen.poly.xml"/>
  <copy file="erlangen.sumo.cfg" type="config"/>
  <basedir path="/home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/examples/veins/"/>
  <seed value="0"/>
</launch>
"
Creating temporary directory...

Temporary dir is /tmp/sumo-launchd-tmp-ZVdazZ

Base dir is /home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/examples/veins/
Seed is 0
Finding free port number...
Claiming lock on port

...found port 39684
Starting SUMO (/home/bluemix/SUMO/sumo-0.18.0/bin/sumo -c erlangen.sumo.cfg) on port 39684, seed 0
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.18.0/bin/sumo -c erlangen.sumo.cfg) on port 39684 (try 1)

Error ([Errno 111] Connection refused)

Connecting to SUMO (/home/bluemix/SUMO/sumo-0.18.0/bin/sumo -c erlangen.sumo.cfg) on port 39684 (try 2)
Releasing lock on port
Starting proxy mode
Done with proxy mode
Done with proxy mode, killing SUMO
Done running SUMO

Cleaning up
Result: "<?xml version="1.0"?>
<status>

    <exit-code>1</exit-code>
    <start>1390590790</start>
    <end>1390590791</end>
    <status>Exited with error code 1</status>

    <stdout><![CDATA[Loading configuration... done.

Step #0.00]]></stdout>
    <stderr><![CDATA[Error: tcpip::Socket::recvAndCheck @ recv: peer shutdown

Quitting (on error).
]]></stderr>
</status>
"

Closing connection from 127.0.0.1 on port 56921
^CKeyboard interrupt.
Shutting down.

and in OMNeT++ console:

RUNTIME ERROR. A cRuntimeError exception is about to be thrown, and you
requested (by setting debug-on-errors=true in the ini file) that errors
abort execution and break into the debugger.

You should now probably be running the simulation under gdb or another
debugger. The simulation kernel will now raise a SIGABRT signal which will
get you into the debugger. If you are not running under a debugger, you can
still use the core dump for post-mortem debugging. Once in the debugger,
view the call stack (in gdb: "bt" command) to see the context of the
runtime error.

<!> Error in module (TraCIScenarioManagerLaunchd) scenario.manager (id=6) at event #1, t=0: Model error: TraCI server "SUMO 0.18.0" reports API version 6. This server is unsupported..

TRAPPING on the exception above, due to a debug-on-errors=true configuration option. Is your debugger ready?

Simulation terminated with exit code: 2

Working directory: /home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/examples/veins
Command line: veins -r 0 -n ..:../../src:../../tests -l ../../tests/power/utils/powerTestUtils -l ../../tests/testUtils/miximtestUtils -l ../../src/base/miximbase -l ../../src/modules/miximmodules omnetpp.ini

Environment variables:
PATH=/home/bluemix/OMNeTpp/omnetpp-4.3.1/bin::/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/bluemix/OMNeTpp/omnetpp-4.3.1/bin
LD_LIBRARY_PATH=/home/bluemix/OMNeTpp/omnetpp-4.3.1/lib::/home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/tests/power/utils:/home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/tests/testUtils:/home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/src/base:/home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/src/modules:/usr/lib32
OMNETPP_IMAGE_PATH=/home/bluemix/OMNeTpp/omnetpp-4.3.1/images
 

Is the problem that i didn't completely remove SUMO 0.19.0 from the system, even though i did make install to 0.18.0 (i.e., OMNetT++ is calling TraCI of SUMO 0.19.0), can that be happened?

Thanks in advance Sommer :).

[Christoph Sommer]

عبدالمؤمن كاظم wrote:
> Now, i installed SUMO 0.18.0, and did make install.

[..]

> Model error: TraCI server "SUMO 0.18.0" reports API version 6. This server is unsupported..

Sorry about that. I forgot that even SUMO 0.18 is not yet supported by
Veins. I have now uploaded a newer version to

https://github.com/sommer/mixim-sommer/archive/b47beb0c.zip

This one should work for all current versions of SUMO. Note that it has
not received extensive testing yet, so please let me know any problems.

Best,

Christoph

--
Dr.-Ing. Christoph Sommer
Institute of Computer Science
University of Innsbruck, Austria

Phone: +43 512 507-96835 / Fax: -9888
http://ccs.uibk.ac.at/~sommer/

[عبدالمؤمن كاظم‎]

Hello,
i've downloaded the file and execute it. I get the following:

bluemix@blueMix:~/SUMO/veins-2.1-beta/mixim-sommer/examples/veins$ python /home/bluemix/SUMO/veins-2.1-beta/mixim-sommer/sumo-launchd.py -vv -c /home/bluemix/SUMO/sumo-0.19.0/bin/sumo

Logging to /tmp/sumo-launchd.log
Listening on port 9999

Connection from 127.0.0.1 on port 39948
Handling connection from 127.0.0.1 on port 39948

Got TraCI message of length 2
Got TraCI command of length 1
Got TraCI command 0x0
Got CMD_GETVERSION
Got TraCI message of length 314
Got TraCI command of length 309
Got TraCI command 0x75
Got CMD_FILE_SEND for "sumo-launchd.launch.xml"
Got CMD_FILE_SEND with data "<launch>
  <copy file="erlangen.net.xml"/>
  <copy file="erlangen.rou.xml"/>
  <copy file="erlangen.poly.xml"/>
  <copy file="erlangen.sumo.cfg" type="config"/>
  <basedir path="/home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/examples/veins/"/>
  <seed value="0"/>
</launch>
"
Creating temporary directory...

Temporary dir is /tmp/sumo-launchd-tmp-ecvP3E

Base dir is /home/bluemix/OMNeTpp/omnetpp-4.3.1/samples/mixim/examples/veins/
Seed is 0
Finding free port number...
Claiming lock on port

...found port 40503
Starting SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 40503, seed 0
Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 40503 (try 1)

Error ([Errno 111] Connection refused)

Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 40503 (try 2)

Error ([Errno 111] Connection refused)

Connecting to SUMO (/home/bluemix/SUMO/sumo-0.19.0/bin/sumo -c erlangen.sumo.cfg) on port 40503 (try 3)

Releasing lock on port
Starting proxy mode
Done with proxy mode
Done with proxy mode, killing SUMO
Done running SUMO
Cleaning up
Result: "<?xml version="1.0"?>
<status>
    <exit-code>1</exit-code>

    <start>1390663457</start>
    <end>1390663621</end>

    <status>Exited with error code 1</status>
    <stdout><![CDATA[Loading configuration... done.

Step #87.80]]></stdout>?UPS, vehicles TOT 30 ACT 30)                          

    <stderr><![CDATA[Error: tcpip::Socket::recvAndCheck @ recv: peer shutdown
Quitting (on error).
]]></stderr>
</status>
"

Closing connection from 127.0.0.1 on port 39948

What am wandering about is this information:

<stderr><![CDATA[Error: tcpip::Socket::recvAndCheck @ recv: peer shutdown
Quitting (on error).

If anything wrong happens during the simulation, i'll report it to you.

Thanks Mr. Sommer.

[Christoph Sommer]

عبدالمؤمن كاظم wrote:
> What am wandering about is this information:
>

> Error: tcpip::Socket::recvAndCheck @ recv: peer shutdown

This is just SUMO complaining that its peer (that is, OMNeT++) has
closed the connection.

This happens independent of whether the OMNeT++ stops because an error
happened, or because it completed successfully.


Cheers,

[عبدالمؤمن كاظم‎]

Ah, OK, not a problem.

Thanks a lot for your answer and your time Mr. Sommer :)
Wish you the best :)

[loon yun]

Hi, do u know how to execute sumo + veins with a different network map? I tried the example and it works for me but whenever I load my network map the program just stop responding. Pls help

[عبدالمؤمن كاظم‎]

Please see the answer of this link:
http://stackoverflow.com/questions/21287273/error-errno-111-connection-refused-in-veins-sumo-launchd-py

--
You received this message because you are subscribed to a topic in the Google Groups "omnetpp" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/omnetpp/7QL2k6QfQqw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to omnetpp+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Yasser Mawad]

Hello every one,
I'm new for OMNeT++, so i have a question.

I have spent about two weeks to install OMNeT++, SUMO, VEINS because i would like to make a scenario for VANET.

I used
- Linux Mint 
- OMNeT Version: 4.6
- SUMO-0.22.0
- Veins-2.1

For each time i have the same problems when try to run veins on OMNeT++ using the command
mawad@linux ~ $  ~/software/veins-2.1/sumo-launchd.py -vv -c ~/software/sumo-0.22.0/bin/sumo-gui

Simulation terminated with exit code: 133

Does you know the problem?
or Does the above versions compatible?

Thanks

[AbdElmomen عبدالمؤمن‎]

Hello,

I guess when you use the latest version of SUMO you have to use the latest version of Veins too.

I think, if you want things to work, try to use Veins 3.0 and SUMO 0.22.0.

try those versions, and tell me if you have the same errors.

[Abdul Latif]

Dear AbdElmomen ,

I used Veins 3.0, sumo 0.22.0 and omnet 4.6. But, I got the following errors 

Simulation terminated with exit code: 255

I am quite new in omnet enviroment. I imported veins but I do not know how can I link sumo 0.22.0 with veins. Could you please explain the procedure. I also spend more than 16 days only installing and running veins with sumo. Please help. 

[AbdElmomen عبدالمؤمن‎]

Hello Abdul Latf,

"Simulation terminated with exit code: 255"

just this information is provided?

are there any text with it?

can you provide me a snapshot of your screen and copy the full error text here?

[Abdul Latif]

Dear AbdElmomen Thanks for your response. The following is the detail of the error. I appreciate your help and guidance in order to run the first example of veins.

Starting...

$ cd C:/Users/IT/Desktop/OMNET++/veins-3/veins-veins-3.0/examples/veins

$ ../../../../../../../../omnetpp-4.6/bin/opp_run.exe -r 0 -n .;../../src --tkenv-image-path=../../images -l ../../src/veins omnetpp.ini

OMNeT++ Discrete Event Simulation  (C) 1992-2014 Andras Varga, OpenSim Ltd.

Version: 4.6, build: 141202-f785492, edition: Academic Public License -- NOT FOR COMMERCIAL USE

See the license for distribution terms and warranty disclaimer

Setting up Tkenv...

Loading NED files from .: 1

Loading NED files from ../../src: 29

Loading NED files from C:\Users\IT\Desktop\OMNET++\veins-3\veins-veins-3.0\examples\veins: 1

Loading images from C:\Users\IT\Desktop\OMNET++\veins-3\veins-veins-3.0\images: *: 0  status/*: 6  

Loading images from C:\omnetpp-4.6\images: *: 0  abstract/*: 90  background/*: 4  block/*: 320  device/*: 195  logo/*: 1  maps/*: 9  misc/*: 70  msg/*: 55  old/*: 111  status/*: 28  

Plugin path: ./plugins

RUNTIME ERROR. A cRuntimeError exception is about to be thrown, and you

requested (by setting debug-on-errors=true in the ini file) that errors

abort execution and break into the debugger.

You should now probably be running the simulation under gdb or another

debugger. The simulation kernel will now raise a SIGABRT signal which will

get you into the debugger. If you are not running under a debugger, you can

still use the core dump for post-mortem debugging. Once in the debugger,

view the call stack (in gdb: "bt" command) to see the context of the

runtime error.

<!> Error in module (Veins::TraCIScenarioManagerLaunchd) RSUExampleScenario.manager (id=6) at event #1, t=0: Model error: Could not connect to TraCI server. Make sure it is running and not behind a firewall. Error message: 10061: Unknown error.

TRAPPING on the exception above, due to a debug-on-errors=true configuration option. Is your debugger ready?

Simulation terminated with exit code: 255

Working directory: C:/Users/IT/Desktop/OMNET++/veins-3/veins-veins-3.0/examples/veins

Command line: ../../../../../../../../omnetpp-4.6/bin/opp_run.exe -r 0 -n .;../../src --tkenv-image-path=../../images -l ../../src/veins omnetpp.ini

Environment variables:

PATH=;C:/Users/IT/Desktop/OMNET++/veins-3/veins-veins-3.0/src;C:\omnetpp-4.6\bin;C:\omnetpp-4.6\tools\win32\usr\bin;C:\omnetpp-4.6\tools\win32\mingw32\bin;C:/omnetpp-4.6/ide/jre/bin/client;C:/omnetpp-4.6/ide/jre/bin;C:/omnetpp-4.6/ide/jre/lib/i386;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\MiKTeX 2.9\miktex\bin\;C:\Program Files\MATLAB\R2008a\bin;C:\Program Files\MATLAB\R2008a\bin\win32;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;C:\Program Files\Windows Kits\8.0\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\omnetpp-4.6\bin;;C:\omnetpp-4.6\ide;

OMNETPP_IMAGE_PATH=C:\omnetpp-4.6\images

[AbdElmomen عبدالمؤمن‎]

Hello,
First of all, I don't use Windows. I am really sorry if I don't understand your problem.
Did you run sumo-launchd.py?

[Abdul Latif]

Dear AbdElmomen,

I did not launched  sumo-launchd.py. But, I run the example of sumo.exe standalone. How can I run sumo-launchd.py in command prompt or in mingwe of omnetpp? Please if you can give me a procedure I am spending too much time on veins. 

[AbdElmomen عبدالمؤمن‎]

Hello,

I really don't know how to do thin under Windows.

But, I THINK, you have to install Python, and then type python sumo-launchd.py in the terminal.

If you don't know Python all, then search on YouTube on how to install Python on Windows.

[Rens van der Heijden]

to run as daemon:
python sumo-launchd.py -dc "$SUMOPATH"
for debugging:
python sumo-launchd.py -vc "$SUMOPATH"

(assuming your SUMOPATH contains the location of your sumo executable)
see also:
python sumo-launchd.py --help

Make sure your machine runs python 2.*, not 3.*, and make sure the port (9999, if I recall correctly) is accessible from 127.0.0.1 (or whichever IP you're trying to access your sumo-launchd from).

[AbdElmomen عبدالمؤمن‎]

did you execute this code?

[Rens van der Heijden]

Better yet, I've included it in the notes on VEINS usage that I'm gathering:
https://github.com/namnatulco/veins/blob/master/usagenotes.md#basics

[Abdul Latif]

Dears ,

I installed python 2.7 in my windows 8.0. in the command prompt I have written the above codes but I got the following error: 

python is not recognized as internal or external command. 

Should I key in the aforementioned commands in command prompt of windows or bash of omnet++ or where?  

[Abdul Latif]

I could run examples in Inet, inetmanet, mixim. But unfortunately I stacked with veins. But, I will try my best to go through this problem with your help. 

[Abdul Latif]

Please any help??

[AbdElmomen عبدالمؤمن‎]

you have to install Python on your system.

see YouTube on how to install it.

[Abdul Latif]

I already installed python in my system and it is straightforward. Then, I added the path of python to my environment variable. 

[Abdul Latif]

Dears

Based on the veins tutorial, I tried to run sumo-launchd.py. However, it is not working and would not also provide error? Is there any solution? 

[Rens van der Heijden]

Use the -v switch to get debug output. Without it, the script minimizes its output.

[Abdul Latif]

Dears, 

I used -v but I got the following:

Listening on port 9999

and no any action. Even I disabled my AVG anti-virus. I know I am in the track but I am not sure what is the problem?

[Rens van der Heijden]

Here's some more things you can check:

Did you configure your omnetpp.ini to connect to 9999?
Can you connect to port 9999 at all (try netcat/telnet or whatever the windows equivalent is?)
Is OMNeT++ still saying it can't connect to SUMO?
Try setting SUMPATH to the sumo-gui exectuable instead. Then you should see the sumo gui every time that the sumo launch daemon starts sumo, and you can see what exactly is going wrong.

If none of these produces useful output, I'm not sure what to do. It'd probably be best to report a bug to the veins developers at that point.

[Abdul Latif]

Thanks a lot Dear Rens,

I will do your suggestions and let you know the results. 

[Maged Hasan]

Hi Dr 

i have used sumo 0.22.0 for my simulation but ut shows me this error 

<!> Error in module (TraCIScenarioManagerLaunchd) uiascenario.manager (id=5) at event #1, t=0: Model error: TraCI server "SUMO 0.22.0" reports API version 8. This server is unsupported..

what can i do know ?
best regards 




On Saturday, January 25, 2014 at 2:42:55 PM UTC+3, Christoph Sommer wrote:

عبدالمؤمن كاظم wrote:
> Now, i installed SUMO 0.18.0, and did make install.
[..]
> Model error: TraCI server "SUMO 0.18.0" reports API version 6. This server is unsupported..

Sorry about that. I forgot that even SUMO 0.18 is not yet supported by
Veins. I have now uploaded a newer version to

https://github.com/sommer/mixim-sommer/archive/b47beb0c.zip

This one should work for all current versions of SUMO. Note that it has
not received extensive testing yet, so please let me know any problems.


Best,

[AbdElmomen عبدالمؤمن‎]

I guess you tried to execute it from the Veins example of OMNeT++?

--
You received this message because you are subscribed to a topic in the Google Groups "OMNeT++ Users" group.

[Maged Hasan]

the veins example runs smoothly with veins ? but my project doesn't .

[AbdElmomen عبدالمؤمن‎]

have you seen the above solutions?

[Maged Hasan]

No , nothing until now .. 

[Maged Hasan]

Thanks to Mrs Tian Bin , he have solved the problem ..According to his justification ,  the thing is that SUMO 0.22.0 is too high to run Inermanet , so we we can use the old version SUMO-0.15 and my simulation could be run smoothly ..