1 / 11

F-MAN OBT comms

F-MAN OBT comms. Status report Challenges, Issues …. Why so late ?. Logosystem only delivered 1 OBT end of February; OBT did NOT have the correct firmware; OBT had to be dispatched to PI early March (firmware upgrade “on site” by TD);

nedaa
Download Presentation

F-MAN OBT comms

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. F-MAN OBT comms Status report Challenges, Issues …

  2. Why so late ? • Logosystem only delivered 1 OBT end of February; • OBT did NOT have the correct firmware; • OBT had to be dispatched to PI early March (firmware upgrade “on site” by TD); • We had to work with incomplete and incorrect technical info (Protocol Specifications, “case study”, input from Logosystem & TD).

  3. Example

  4. OBT installations & HUB (1) • Installations started on March 9th at Miramas (SCIRO + TD) with considerable difficulties: • Lost almost 3 days for firmware modification (bug fixing) and loading sensor “experiments”; • Very first use of HUB on the 3d day (15:00); • HUB bug fixing ! Ready next day at 12:00; • First 100% session with HUB (EDC – SCIRO)

  5. OBT installations & HUB (2) • Start of PI installations on March 17th (Primoz – TD), again with considerable loading sensor issues; • Successfull OBT installations (OBT + LS) by Primoz and EDC on March 19th; • 2 More OBT’s on 27/3, 26/3 and 6/4 for PI, 1 LS O.K., 1 LS non functional !!

  6. OBT installations & HUB (3) • Miramas 15/04: • 1 Successful OBT installation; • 2 Partly initialisation starts; • STOPPED ! • Asked for diagnosis by TD; TD asked permission to get a “memory dump” from the OBT’s.

  7. OBT installations & HUB (4) • Results on April 16th (after 58 hours !): • Comms between HUB & OBT’s fully operational; • Installed OBT’s (9): • PI: CS00198, CS00199, CS00200, CS00251, CS00252; • SNCF: CS00244, CS00245 (*), CS00247, CS00249.

  8. Issues, challenges… • Loading sensors : • TD issued a LS installation amendment document LAST FRIDAY (16/04) ! • TD has to perform; ASAP ! • Corrective interventions take TIME, because of wagon & personnel availability.

  9. April 16th polling results Latitude, Longtude table (msg 0x80)

  10. HUB – DPM comms • XML interface (parsing) has to be tested and Integrated; • Test-specific software to that purpose installed in Februari. NEVER USED ! • First “test drive” with “bogus” position message (EDC – NTUA) showed 2 small problems (already solved). • CP wagons have to be added… • To be continued

  11. Patience please … • IVU, NTUA and EDC are working on it… • Except for the loading sensors, we are working with PROVEN TECHNOLOGY: • TD sold more than 13 000 OBT’s (although with different firmware); • We (finally) have a valuablme contact at TD; • GSM and SMS => massive use in tracking & tracing applications; • The Internet: where would we be without it ? • Webservers, Databases, GUI’s : we are in very capable hands 

More Related