thank you for your answers. I tried to start the ITS Cooperative Demo Application (iCS -c itetris-config-file.xml) and get an error. The app is not able to connect the NS3 on port 1982.
The error causes probably by a previous error on step 2 - setup phase.

WELCOME TO iTETRIS
==================
STEP 1 - SETUP PHASE
iCS --> SUMO launched.
iCS --> ns-3 launched.

STEP 2 - SETUP PHASE
main-inci5: error while loading shared libraries: libns3.so: cannot open shared object file: No such file or directory
sh: demoapp: not found
Loading configuration... done.

STEP 3 - SETUP PHASE
iCS --> Trying 0 to connect SUMO on port 5500...
iCS --> Connected to SUMO
O

iCS --> Trying 0 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Trying 1 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Trying 2 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Trying 3 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Trying 4 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Trying 5 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Trying 6 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Trying 7 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Trying 8 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Trying 9 to connect ns-3 on port 1982 and Host localhost...
iCS --> No connection to ns-3; waiting...
iCS --> Could not connect to Ns-3

I tried to start the NS3 before the ITS Cooperative Demo Application with the main-inci5 app in the NS3 scratch folder and get an error during the start of the app (./waf --run scratch/main-inci5):

No port or log file for ns-3 server introduced.
Format is: main-inci3 [port-number] [fileGeneralParameters] [fileConfTechnologies] OPTIONAL [log-path]
Exiting...

Is it nessessary to start the NS3 before Demo Application or start the Demo Application the NS3 automaticly (like the SUMO)?

I found the "communicationsim" tag in the itetris-config-file.xml and I noticed the "communication-general-params-file" tag.

"communicationsim"
"communication-executable value="main-inci5"/"
"communication-host value="localhost"/"
"communication-port value="1982"/"
"communication-general-params-file value="./ns-3_files/configGeneral.xml"/"
"communication-config-technologies-file value="./ns-3_files/configTechnologies-ics.xml"/"
"/communicationsim"

I replaced the brackets of the tags with " because of your forum-editor hide all xml-tags :-)

I have no configGeneral.xml in my ns-3_files folder!

Regards

Michael

I would test my installation with the ITS Cooperative Demo Application but I can't find it in the iTETRIS_Platform_0.1.0.zip. Where can I download this Application?

Regards
Michael

Comments: 3

I downloaded the new source and get a new Error during the make-command: make -f Makefile.cvs

autoreconf -i
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT'
configure.ac:10: installing `./missing'
src/Makefile.am: installing `./depcomp'
Makefile.am: installing `./INSTALL'
Makefile.am: required file `./NEWS' not found
Makefile.am: required file `./README' not found
Makefile.am: required file `./AUTHORS' not found
Makefile.am: required file `./ChangeLog' not found
Makefile.am: installing `./COPYING' using GNU General Public License v3 file
Makefile.am: Consider adding the COPYING file to the version control system
Makefile.am: for your code, to avoid questions about which license your project uses.
autoreconf: automake failed with exit status: 1
make: *** [all] Error 1

And the configure-command failed too:
./configure --enable-sumo --enable-ns3 --enable-applications -with-geographic=/usr/local –enable-log

configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: –enable-log
checking build system type... Invalid configuration `–enable-log': machine `–enable' not recognized
configure: error: /bin/bash ./config.sub –enable-log failed

It works fine if I apply the patch in the ns-allinone-3.7/ns-3.7 folder.

Thanks

I used the command from the iTetris_Guidelines0.1.0.pdf:

./configure --enable-sumo --enable-ns3 --enable-applications -with-geographic=/usr/local –enable-log

The patch failed with this output:

Hunk #1 FAILED at 49.
Hunk #2 FAILED at 176.
Hunk #3 FAILED at 216.
Hunk #4 FAILED at 1000.
Hunk #5 FAILED at 1033.
Hunk #6 FAILED at 1047.
Hunk #7 FAILED at 1130.
Hunk #8 FAILED at 1161.
8 out of 8 hunks FAILED -- saving rejects to file bindings/python/apidefs/gcc-ILP32/ns3_module_common.py.rej
patching file bindings/python/apidefs/gcc-ILP32/ns3_module_core.py
Hunk #1 FAILED at 93.
Hunk #2 FAILED at 351.
Hunk #3 FAILED at 1575.
3 out of 3 hunks FAILED -- saving rejects to file bindings/python/apidefs/gcc-ILP32/ns3_module_core.py.rej

...

The next patch would delete the file scratch/simple.cc,
which does not exist! Assume -R? [n]

Comments: 4

"make -f Makefile.cvs" returns the same output and the configure command returns:

...
config.status: creating src/ics/facilities/mapFacilities/Makefile
config.status: creating src/ics/facilities/mapFacilities/road/Makefile
config.status: creating src/ics/facilities/stationFacilities/Makefile
config.status: creating src/ics/facilities/messageFacilities/Makefile
config.status: error: cannot find input file: `Makefile.in

Is a solution or a workaround avaliable?

Thanks
Micha

Comments: 4

Comments: 0

Comments: 0