1 / 5

Particles and Fields Early Payload Test Post Test Review April 6, 2011

Particles and Fields Early Payload Test Post Test Review April 6, 2011. Test Overview. April 5, 2011 PF Bench Checkout: 8:45 am Test Start Time: 9:00 am Reviewed test procedure, performed AESOP huddle PF and SCE Safe-to-Mate Procedure redlines but all test results expected

isaura
Download Presentation

Particles and Fields Early Payload Test Post Test Review April 6, 2011

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. Particles and Fields Early Payload TestPost Test ReviewApril 6, 2011

  2. Test Overview April 5, 2011 PF Bench Checkout: 8:45 am Test Start Time: 9:00 am Reviewed test procedure, performed AESOP huddle PF and SCE Safe-to-Mate Procedure redlines but all test results expected In-rush Testing First time testing with SCE Worked through overcurrent settings, took several scope plots of both current and voltage Broke for lunch: 11:25 am – 12:30 pm Resumed Functional Test: 12:30 pm All tests passed as expected Included testing of inactive side, confirmed no action in response to commands sent to inactive interface Test End Time: 1:45 pm

  3. DTCI Test Analysis • One minor script typo on discrete line • Once fixed, all tests completed successfully ACTION: None.

  4. PF Test Analysis • All commands sent to inactive interface were ignored as desired • All commands sent to active interface were properly accepted and desired response provided • After testing with commands and responses, PF team loaded different software that would force some boundary case testing on checksums • Analysis of messages after the test showed the following: • First IP header sent after power-up shows incorrect checksum • Testing of expected overflow in calculating 16-bit added values showed disconnect between PF and LM methods for calculating IP checksums • All UDP checksums passed • Healthy discussion ensued on methods for calculating checksums. Lingering questions on how to calculate checksums were resolved. ACTION:Resolve first IP checksum miscalculation.

  5. Final Analysis • Safe to Mate portion of test showed expected results • In-rush portion of test showed expected results • Functional portion of test achieved intended objectives • Reset discrete caused reset of PF • Asynchronous RS-422 interface is compatible • Commands sent to inactive interface are properly ignored • Side Select discrete was properly interpreted by PF • Tested with new Side Select definition (A side low) • Boundary cases for checksum calculations showed disagreement between LM and PF as expected based on multiple email transactions prior to test • Created specific transactions to discuss to allow both sides to come to agreement on the correct method to calculate values

More Related