FP Application Manual

Department: PC TOOLS / ADAS SIBIU

Division: Automotive Systems

Project: FP Application

Author:

Matau Alexandru-Rudi

USER’S MANUAL – FP APPLICATION V1.0

Page 1 of 24

FP APPLICATION Version 1.0.71

User's Manual




Author:



Page 2 of 24

CONTENTS

1. Introduction ..................................................................................................................................................................... 3

2. Abbreviations .................................................................................................................................................................. 3

3. Changelog .......................................................................................................................................................................... 3

4. Interface ............................................................................................................................................................................. 6

4.1. Main Tab (Execute) ............................................................................................................................................. 6

4.2. Database ................................................................................................................................................................... 8

4.2.1. Add/edit command .................................................................................................................................... 9

4.2.2. Edit parameters ......................................................................................................................................... 10

4.2.3. Edit output format .................................................................................................................................... 10

4.2.4. Add/edit error ........................................................................................................................................... 11

4.3. Settings ................................................................................................................................................................... 12

4.4. Specific Project Tabs ......................................................................................................................................... 14

4.4.1. Flash ............................................................................................................................................................... 14

4.4.2. Set GPIO ........................................................................................................................................................ 15

4.4.3. Write/Read Memory ............................................................................................................................... 16

4.4.4. Read Voltage over sar ............................................................................................................................. 17

4.4.5. Send MTi message .................................................................................................................................... 18

4.4.6. get sdadc values ........................................................................................................................................ 19

4.4.7. Send spi message ...................................................................................................................................... 20

4.4.8. control dac output .................................................................................................................................... 22

4.4.9. update wgm lut .......................................................................................................................................... 23

4.4.10. Update pwm lfsr ........................................................................................................................................ 24




Author:



Page 3 of 24

1. INTRODUCTION

FP Application is a window-based application that has been developed using Visual C# 2008. The aim of the application is to allow commands to be sent to ECU’s using one of the available protocols. Each command’s response is received and formatted before displaying the result to the user.

2. ABBREVIATIONS

The following abbreviations are used in this document:

Abbreviation Definition ECU Electronic Control Unit FR FlexRay

CAN Controller Area Network

3. CHANGELOG

Version Change(s) 1.0.36 Initial release 1.0.47 Added Ethernet support

Added ability to import everything from an existing set

Added support for multiple commands with same id but different names and parameter values (database structure had to be slightly modified to accommodate this change)

Fixed value conversion to float Improved log output Extended flash support

1.0.48 Updated Ethernet dll If UDP Send or Receive throws an

exception a messagebox is shown with the exception’s message and the full exception is written to the logfile

Increased timeout to 5 minutes for FPGA flashing

Fixed bug that deleted/modified duplicated commands (same id , different name)




Author:



Page 4 of 24

Source IP and Source MAC are automatically filled with local IP (v4) and MAC address

Changed display of MAC addresses to show hex values

1.0.54 Added project selection window (filters available tabs). Projects:ARS400, MFC400, SRLCAM400, SRR300.

- Completely separated function to interpret and display result from function of executing a command

- Added a separate function to execute a command string

- Scrollable parameter and output windows

- Fixed limit check - Updated TPOverCAN and TPOverFR dll

files (added support for VN1610 and VN1630)

- Implemented special panels for Control SDCLK, Control Clock output, Set GPIO, Read voltage over SAR ADC. ! Panels not yet tested – are available for ARS400 and SRR300.

1.0.68 updated ethernet dll (added detection of ethernet hardware)

- corrected the functionality for set GPIO, Read voltage over SAR ADC

- implemented new panels for read/write memory, get SDADC values, send SPI message (ATIC151 only, for now), control DAC output

- slightly improved error handling for can, fr, ethernet

- new installer (installs required dependencies)

1.0.70 added panels for Send MTI message, Update PWM LFSR, Update WGM LUT

- added excel report output alongside the pdf report

- added aditional panels to Send SPI message : BGT24AT2, BGT24AR4, SpiritDig




Author:



Page 5 of 24

- modified GetSDADC values : Channel can also be set to 2

- modified labels to specify value type (hex or dec)

- added buttons to improve handling of commands to and from the cyclic list

1.0.71 - added functions to load/save cyclic list and settings(timeout, repeats, selected command set)

- added option for inverted endianness 32 bit, payload only (calculate CRC after inversion)

- fixed crash when device was disconnected after being selected




Author:



Page 6 of 24

4. INTERFACE

4.1. MAIN TAB (EXECUTE)

The main tab of the application. From here the user can:

- Check to see if the connection is active (upper left – status led): If the communication protocol has been successfully initialized the led will be green and the status message will report that the selected protocol has been successfully initialized.




Author:



Page 7 of 24

If the connection has failed the led will be red , the status message will report that no communication protocol has been initialized and the application will switch to the settings tab where the user can adjust the connection’s settings and try again.

- See the ECU Info(Software version, Hardware version and PCB Index) if the connection with the device has been successfully initialized

- Select a command set from the list of available sets – a command set is a list of commands that the user can create and modify to suit a certain project/situation/device. Each set is independent and can consist of different or same commands as other sets but with slight variations like different command outputs or parameters.

- Execute a single command by double clicking on the desired command in the Commands list - Execute a single command with a different set of parameter values by clicking once on the

desired command , changing the values in the input/output box and double clicking on the same command in the Commands list

- Execute multiple commands with a set delay between each command with the possibility of multiple repeats:

o Drag the desired commands from the Commands list over to the Cycle Commands list

o Reorder them as necessary by using drag and drop inside the list o Set the repeat count o Set the time between commands (in milliseconds) o Press the execute button

- Log command’s output by checking Log command(s) before executing any command that needs to be logged (applies to both singular commands and cyclic commands) – not yet implemented – output style needs to be defined

- Clear the input/output box - Export the outputs of the commands that were executed since the last clearing of the

input/output box - Close the connection and return to settings tab - Select if the application should stop the execution of the cyclic commands if one fails by

checking the upper right checkbox (“Stop on failure”); - The application will automatically create a PDF report after a cyclic run has completed

(after all repeats have been executed or if the execution of the commands has been stopped by the failure of a command – “Stop on failure” checked)

- Save and load cyclic command list, repeats, delay between commands and selected command set.




Author:



Page 8 of 24

4.2. DATABASE

The database tab. From here the user can:

- Create/rename/remove command sets using the following buttons: New Set, Rename Set, Remove Set available under the list of commands. If no command set has been selected only the New Set button is enabled.

- Add/Edit/Remove commands (see 3.2.1) - Edit command parameters and output format (see 3.2.2 and 3.2.3) - Generate header file – available if a command set is selected. Will generate a header file

(“FPCommands.h”) for the currently selected set in the application folder. - Add/Edit/Remove errors (consisting of error code and description) (see 3.2.4)




Author:



Page 9 of 24

- Import everything (commands, parameters, outputs, errors) from another set - Import only errors from another set (using the Import Errors button on the Errors tab)

4.2.1. ADD/EDIT COMMAND

Response length: the total expected length of the result (including the first 4 bytes – receive ID, controller ID, command ID, response status). Used to define output format, does not limit the number of response bytes received or displayed.

Length: the total length of the command (request ID, controller ID, command ID, parameter values).




Author:



Page 10 of 24

Parameters: the number of parameters the command has.

ID: the command id specified in hex (with or without the 0x prefix).

4.2.2. EDIT PARAMETERS

Using this window the user can specify a name, the length in bytes and a default value for each parameter. The name is optional. ! Obs: Do not use “:” in parameter name.

! All parameters are to be specified in hex (with or without the 0x prefix) with multiple bytes separated by spaces.

4.2.3. EDIT OUTPUT FORMAT

Using this window the user can specify how the result of a command should be interpreted and displayed. If the user does not save the output format for a command, all values received will be displayed as hex. Name is optional.




Author:



Page 11 of 24

The user can also select for the output value to be checked either to match or to be within certain limits. For this , the user must select the check type and complete the corresponding textboxes for the type of checking selected.

4.2.4. ADD/EDIT ERROR




Author:



Page 12 of 24

4.3. SETTINGS

The settings tab. From here the user can select the desired communication protocol, configure protocol settings and initialize the communication.

The application has autodetect support and will automatically update the list of hardware currently available. Once a device is selected the application checks for available channels for all protocols.

The user must first select the desired protocol, then the hardware device, the protocol specific settings like channels, send id, receive id, etc and click the “Apply settings and Initialize” button. If the initialization will succeed the application will automatically switch to the main tab and execute the initial commands required to display ECU Information. If the initialization fails the user has to




Author:



Page 13 of 24

check the settings and try again. The “Load defaults and Initialize” button will set the protocol settings to predefined defaults and try to initialize the connection.

The application will save all the application settings (selected command set, selected hardware, etc) at exit and will load the last used settings at startup and try to initialize the communication. If it fails the settings tab is automatically displayed so that the user may check the connection settings before trying to manually initialize the desired protocol.




Author:



Page 14 of 24

4.4. SPECIFIC PROJECT TABS

4.4.1. FLASH

From this tab the user can either select a folder from which to load the files to be flashed (5 files named as follows: “SBL.tiimage", "SBL_CA8.tiimage", "SBL_DSP.tiimage", "SBL_M3VIDEO.tiimage", "SBL_M3VPSS.tiimage”) or select files individually , select the flash type and issue the flash command. The progress of the flashing will be displayed using the progress bar.

The inverted endianness option (if checked) will invert every 4 bytes of payload data. CRC is calculated after inversion.

Example: original payload : AC DB 35 67 11 22 33 44

Inverted payload : 67 35 DB AC 44 33 22 11




Author:



Page 15 of 24

4.4.2. SET GPIO

This tab gives the user the ability to update GPIO values. Input the number of GPIO to be updated in the GPIO count box and click the Update button after which set the GPIO number, Output and Level for each GPIO. After everything has been set press the Send button to execute the update.




Author:



Page 16 of 24

4.4.3. WRITE/READ MEMORY

On this tab it is possible to read from memory and write to it. Specify the start address for the operation desired and the width of write for writing or number of bytes and bytes per line for reading after which issue the command by pressing the corresponding button.




Author:



Page 17 of 24

4.4.4. READ VOLTAGE OVER SAR

Specify an INI file and read the voltage values. Based on information provided in the INI , transformations and formulas will be applied as specified and all channels mentioned will be displayed with their respective values in the table.




Author:



Page 18 of 24

4.4.5. SEND MTI MESSAGE

Select Lane number, specify length of header and header bytes as well as length of payload and payload bytes and press the Send button.




Author:



Page 19 of 24

4.4.6. GET SDADC VALUES

After selecting all the values for the different settings press the Get values button to open a window containing a graph displaying the values requested.




Author:



Page 20 of 24

4.4.7. SEND SPI MESSAGE

4.4.7.1. ATIC151

4.4.7.2. BGT24AT2




Author:



Page 21 of 24

4.4.7.3. BGT24AR4

4.4.7.4. SPIRITDIG




Author:



Page 22 of 24

4.4.8. CONTROL DAC OUTPUT

Set the values and press the Send button to modify DAC output.




Author:



Page 23 of 24

4.4.9. UPDATE WGM LUT

Specify an ASCII file to load data from or specify the required LUT index, start address and data then press the Send button to update the specified LUT index. The following ASCII file is provided as template: WGM_LUT.txt . Comments are to be specified after //. DO NOT insert comments as new lines before, after or between the lines of index, address and data. Always insert comments at the end of existing lines using // followed by the respective comment. Data can have as many lines of bytes specified and as many bytes on a row as one sees fit. Bytes can be grouped or spaced as needed.

WGM_LUT.txt




Author:



Page 24 of 24

4.4.10. UPDATE PWM LFSR

Specify an ASCII file to load data from or specify the required LUT index and data then press the Send button to update the specified LUT index. The following ASCII file is provided as template: PWM_LFSR.txt . Comments are to be specified after //. DO NOT insert comments as new lines before, after or between the lines of index and data. Always insert comments at the end of existing lines using // followed by the respective comment. Data can have as many lines of bytes specified and as many bytes on a row as one sees fit. Bytes can be grouped or spaced as needed.

PWM_LFSR.txt

Date post:	15-Dec-2015
Category:	Documents
Upload:	asuras
View:	47 times
Download:	10 times

FP Application Manual

Documents