10 th Plenary Meeting Panagiotis Lytrivis ( panagiotis.lytrivis@iccs.gr ) ICCS

1. 10th Plenary Meeting Panagiotis Lytrivis (panagiotis.lytrivis@iccs.gr) ICCS SP1

2. Contents of the presentation Deliverable 1.4.2 – “HW & SW specifications of prototype and test bed components” Deliverable 1.5.1 – “Test Plan design” SR algorithms status LDM installation FW version 4 testing (problems and UDP players)

3. Deliverable 1.4.2 (1) “HW and SW specifications of prototype and test bed components” EXECUTIVE SUMMARY 1. Introduction 1.1.Innovation and Contribution to the SAFESPOT Objectives 1.2.Methodology 1.3.Deliverable structure 2. HW specifications: Sensorial Suite 2.1.Laserscanner (IBEO) 2.2.LRR 2.2.1.Fujitsu Ten (CRF) 2.2.2.Other (Renault, VOLVO) 2.3.Vision Systems (CRF, Renault, VOLVO, TUC) 2.4.Tilt Sensor (PIAGGIO) 2.5.GPS Sensor (?)

4. Deliverable 1.4.2 (2) 3. HW specifications: Description of the HW Components 3.1.Main PC specs (PlugIn PC - BOSCH) 3.2.Gateway (each OEM if they use different approaches) 3.3.Ethernet Switch (each OEM if they have different options) 3.4.ESPOSYTOR PC(MMSE) 3.5.VANET Router (DAIMLER) 3.6.Other PCs (from other SPs or reference to another deliverable) 4. SW Specifications 4.1.The platform (the SW modules of the platform described in D1.4.1, a short paragraph and reference to the previous deliverable) 4.2.The positioning SW – SP3 (reference to another SP3 deliverale) 4.3.The synchronization SW (reference to other deliverable docs of other SPs) 4.4.Other related SW running inside each vehicle

5. Deliverable 1.4.2 (3) 5. Test bed specifications: The test vehicles 5.1.The VOLVO vehicle 5.2.The PTW vehicle 5.3.The CRF vehicle 5.4.The Renault vehicle 5.5.Other test beds 6. Conclusions 7. References • Annex/es Discussion

6. Deliverable 1.5.1 (1) “Test Plan Design” EXECUTIVE SUMMARY 1. Introduction 1.1.Innovation and Contribution to the SAFESPOT Objectives 1.2.Methodology 1.3.Deliverable structure 2. Testing in the lab 2.1.HW components tests 2.2.SW components tests 3. Validation of the in-vehicle platform 3.1.Demonstrators and test tracks 3.2.On board functionality test 3.3.Evaluation phase

7. Deliverable 1.5.1 (2) 4. Performance analysis phase 5. Conclusions 6. References 7. Annex/es Open points - discussion

8. SR status • Decision not to work with Eclipse and GNU compiler (no experience) and use the 3rd version of the FW to continue the work -> if needed no problem using Eclipse and MinGW • Working in VS 2003 .NET and update to 2008 was needed for the library files and connection to the LDM • Next step the consideration of map matching idea into the trajectories • Contact with Robin Schubert from TUC to discuss and exchange ideas about the map matching should be arranged • 3 dlls (CML, VDL, SRL) were implemented and tested with the 3rd FW everything was OK (low level functionality e.g. matrices, vectors, motion models etc, are included in these dlls)

9. Installation of Dortmund DB • Problems installing the DB from Dortmund test site • A lot of effort from Tele Atlas (designing the map) and it was difficult to find a common date for phone call • Signing of evaluation agreement and sending to TA was time consuming • Unexpected problems with the script for importing the shapes to the database (using “Cygwin”) → problem solved with the help of Christine Bartels • Previous week Dortmund test site tested with Tester.cpp provided by BOSCH • Minor problems occurred using the API queries (probably the lib file was not the latest one) e.g. the intersection function was empty but from openJump this was not the case. • Further checking is needed from ICCS

10. FW experiments & open issues FW experimentation • The laser scanner UDP player successfully tested (4th FW) • CRF UDP player - Only “DAQ” provided a log file - “All threads” selection (sometimes) resulted in error Open points • Positioning and VANET group -> Current status, UDP players? • Internal report concerning the algorithmic details?