This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PGA450-Q1: selection of component between PGA450-Q1 or PGA460-Q1

Part Number: PGA450Q1EVM
Other Parts Discussed in Thread: PGA450-Q1, PGA460, PGA460-Q1, TPS4H000-Q1

Hello TI -Team , 

i ma working on Automotive ADAS application project for reverse park assist , we are using 4 ultrasonic sensors , i have gone through the PGA450-Q1 and PGA460 also , we have a master ECU connected to LIN network , we are looking for cost effective solution.

Proposal 1 : with PGA450-Q1 : 

since PGA450-q1 is having 8-bit MCU and LIN interface can we connect directly the IC and start reading the data from all the ICs ? if yes how to differentiate the data coming from which sensor , does each IC has its own NAD or do you have other proposal . 

I can see this IC is bit costlier as well , we do not require the 8- bit MCU again , need to qualify for functional safety standards also . So we are looking for IC with DSP and EEPROM to store data so that can be read via SPI /I2c

Proposal 2 : with PGA 460 - Q1 : 

This IC is suitable for the application since it is not having any MCU , and a discrete Solution with DSP and EEPROM , but problem is how to interface with my LIN Master ECU , since it is not having any LIN compatible . 

Kindly suggest your proposal.

Thanks and Regards 

Shyam Prasad 

  • Part Number: PGA450Q1EVM

    Hi TI - Team , 

    We are working on Reverse Park Assist for project in which we have one master ECU (CAN /LIN communication ) which needs to be connected to 4 ultra sonic sensors placed on the back side of the bumper. while going through the TI Transceivers we found the PGA450-Q1 and PGA460 as suitable ICS for our development of the project , but we need the take one of these two ICS considering Cost Effective .

    my primary question is can we connect PGA460 to LIN Master ECU , if yes can you propose a design how to connect .

    we are not looking for PGA450-Q1 which has inbuilt 8- bit MCU since we do not require it as we need passing solutuin where we can directly read the data from registers of Transceivers for distance of object detected via SPI/I2C or LIN . 

    Kindly propose a better solution for this .

    Thanks and Regards 

    Shyam Prasad 

  • Hi Shyam,

    I will recommend the PGA460-Q1 for this park assist application because the PGA460 offers superior performance, lower cost, smaller size, and easier programming than the PGA450-Q1. 

    The PGA460-Q1 uses an alternative interface to the LIN called One-Wire UART (OWU) on the IO pin. OWU is a simplified version of the LIN interface, and excludes items such as the break field and much of the other LIN padded frames. The PGA460's OWU bus can support up to eight devices, each with its own unique ID. The unique ID of each PGA460 is stored in the 3-bit UART_ADDR field in the EEPROM memory. The OWU UART_ADDR substitutes the traditional LIN's NAD. Because many ECUs use a UART port to enable LIN, the same UART port can be used to enable OWU on the PGA460. The OWU interface uses the same command and packet structure as the PGA460's standard UART.

    Here is more information on the two automotive-centric one-wire interfaces available on the PGA460, both use the IO pin:

    • Time Command Interface (TCI)
    • One-Wire UART (OWU)

    TCI:

    The TCI interface is a low BW interface for reading and writing registers; however, during typical time-of-flight operation, the TCI pin toggles in real-time when an echo is detected, meaning you get the TOF data faster than any other interface. The TCI interface can only be used in a star topology due to the lack of addressing. The TCI interface will also require an intermediate transceiver between the PGA460 and ECU, so each PGA460 device will need a dedicated GPIO pair from the ECU. Of course, you can multiplex the GPIO signals to minimize the number of allocated GPIOs if you do not intend on simultaneously bursting/listening on multiple PGA460s. TCI is mainly suggested for solutions that require real time TOF data. The idea is that you only read/write registers during start-up for device configuration, and in other special cases (i.e. diagnostic checks or device reconfiguration), so the bulk of the device is operating in the real time TOF mode.

    OWU:

    The OWU mode is more flexible, and is available as a simplified alternative to the LIN interface. You can leverage the PGA460’s address to create a bus topology to only use one UART port from the ECU to bus up to eight PGA460s. In your case, I suspect you will have two UART ports: one for the front bumper and one for the rear bumper. Though the PGA460 does not support daisy chain addressing directly, there are external means of enabling daisy chaining (see Appendix-A below). The primary difference is that in the OWU mode, the device must wait the entire duration of the record length cycle before reading back the TOF results. This means the data response is not real-time, so the OWU approach is for less time sensitive applications. For example, if the maximum detectable range requirement is 5m, then the record cycle length is 32ms, so even if an object is detect very close to the sensor, e.g. at 4ms in time, the device has no means of indicating this early detection, and the user must always wait 32ms to read back the ultrasonic measurement results. An additional benefit to using the OWU mode is that the TOF is computed by the PGA460 as a 16-bit result in 1us resolution, while also being able to provide the echo amplitude and width details. The TCI mode can only provide the echoes rising/falling edges, and requires the ECU to compute the TOF based on these edge captured deltas. I typically recommend OWU for most automotive single wire applications because it is more intuitive, and leverages more of the PGA460’s features. It can only support up to 115.2kBaud for fast read/writes. You will also need a LIN transceiver between the PGA460 IO bus and ECU UART pins.

    The UART (2-pins) and USART/SPI (3-pins) low-voltage interfaces are intended to be used for commercial/industrial applications, but can be leveraged for automotive if preferred. These are more standard, and can be directly interfaced to the PGA460 bus from the ECU. The cost of using a one-wire interface versus the increased cable count for the low-voltage interfaces is an exercise you will need to perform. I suspect the transceiver may be a lower cost solution versus a 2 or 3 pin bus being routed to each of the bumpers.

    Appendix-A:

    If you are able to pre-program the UART_ADDR (bus address) of each PGA460 module before installing the module onto the OWU bus, they will be able to differentiate and independently read/write between each module. However, in the case auto-addressing of each module is required, such that multiple fresh PGA460s are installed on the bus (each will have a default UART_ADDR of 0), below are two auto-addressing options:

    Option 1: PGA460-Q1 Auto-Addressing through Power

    To enable auto-addressing, the power to each module can be controlled by using independent high-side load switches for the VPWR pin of each PGA460. For a system of 3-4 PGA460 modules, you could use a part such as TI’s TPS4H000-Q1 40-V/1000-mΩ Quad Channels Smart High-Side Switch, which requires a GPIO to control the on/off state of each channel. The implementation requires the ECU/BCM to open or close each VPWR channel based on whether it should be programmed, isolated, or constantly active.

    Option 2: PGA460-Q1 Auto-Addressing on Bus Interface

    PGA460 Frequently Asked Questions (FAQ) and EVM

    Troubleshooting Guide: http://www.ti.com/lit/an/slaa733/slaa733.pdf

    4.4.11 Is daisy-chain supported by the PGA460? Can the master controller automatically differentiate and program the PGA460 UART address?

    Daisy-chain auto-addressing and automatic slave node position detection (SNPD) are not supported by the PGA460. External hardware or switches must be used in combination with the external master controller to automatically assign address to multiple PGA460 devices connected to the same bus. The example provided is interchangeable for the IO and RX pin. When switching IO, be sure select a bi-direction switch rated for VPWR (up to 30 V). The RX pin is a unidirectional pin rated at either 3.3V (default) or 5.0 V.

    Figure 15. Master-Controlled Auto-Addressing Example