3
1. Canoe:
a. We firstly open the Canoe application.
b. It takes one .cfg file as a parameter that contains configuration settings necessary for defining and executing a testing environment for automotive networks.
c. After opening that configuration file, we start the measurement, including network traffic, signal behavior, and error detection.
2. Control Desk:
a. Control Desk is automatically opened.
b. After that, add the project. For adding that project, it takes two parameters: one .CDP file and one .sdf file.
c. It refreshes the interface connections.
d. It refreshes the platform configuration.
e. Then it instructs the Control Desk to go online.
3. MAport Configuration:
a. It starts creating a test environment for interacting with a vendor-specific test bench (dSPACE GmbH) using the ASAM XIL API, which is used for configuring measurement and calibration ports (MAPort) and for starting the simulation.
b. It takes four parameters, such as MAportConfigSCALEXIO.xml, as a parameter.
4. GUI for Selecting Excel Path:
a. It opens a GUI from which we select the path of the TestLibrary.xlsx file where all the test cases are written. This GUI will only open the supported Excel file; if you try to upload any other file, it gives you an error.
b. It creates a separate folder with the current date and time as the name of the folder, and it creates a new Test Library Excel file with the same value and the current date and time as the file name.
5. Test Case Execution:
a. We take the start time and print it in the Excel sheet.
b. From these newly created Excel spreadsheets, it mostly focuses on the actions mentioned along with the parameters.
c. There are various actions present in the Test Library, along with the other requirements for performing that action (KL30_off, KL30_on, can_write, LED_read, ExtNtc_write, InNtc_write, vol_write). We have defined these as functions in the backend. So, if the action value matches with this function, it starts doing its operation.
d. To perform any actions, we need two things: model path and value.
e. We create the model path by adding the signals with some fixed path, and we have the value present in the Values column of the Test Library.
f. We perform only two operations: read and write.
i. Write Operation: We fetch the value given in the Test Library and then perform the read operation.
ii. Whatever values come after the read function are printed in the Excel sheet.
iii. We verify that the value we are reading is the same as the value present in the Values column. It also prints how much time it takes to complete that action.
iv. If both values match, then in the Condition column, it writes OK, and in the Result column, it writes Passed.
g. It goes through all the actions row-wise and performs all the operations.
h. If any error occurs, it is managed by the try-except blocks.
6. Test Closer:
a. If the action is completed, it closes the Excel sheet and saves it in the desired location with the file name as the result with time and date.
b. It closes the Canoe, Control Desk, and the connections with the dSPACE.
Let me know if there are any specific changes or additions you'd like!