The invention relates to a method for operating a transceiver of a bus participant connected to a data bus, or, expressed differently, a method for the transceiver management of a bus participant. Particularly, the invention relates to a method for configuration, state control and diagnosis of transceivers exclusively via their data bus communication interfaces.
Technical solutions for networks often require configuration, diagnosis and state control of the transceivers of the data bus participants of the network. A transceiver is understood to be the interface between a data bus and a microcontroller of the participant.
In present-day configuration interfaces, use is made either of standardized interfaces such as e.g. SPI, I2C, or other proprietary interfaces. The transceiver pins (TXD/RXD) are normally used exclusively for communication of useful data via the data bus.
The methods that up to now have been normally used for operational control of transceivers will require additional (control) pins on the transceivers, which often have to be provided exclusively for this purpose. Due to the advancing miniaturization, an ever more frequent demand exists for very small housings with only few IC pins while, nonetheless, the wish exists to have all degrees of freedom of configurability, state control and diagnosis of transceivers.
It is an object of the invention to provide a method for operating a transceiver of a bus participant connected to a data bus which makes it possible, even in case of a reduced number of terminals, i.e. IC pins, to control the transceiver with respect to its operation and its operational settings as had been the case before.
To achieve the above object, the invention proposes a method for operating a transceiver of a bus participant connected to a data bus, the bus participant further comprising a control unit (e.g. microcontroller, state machine, hard-wired logic), and the transceiver being connected between the data bus and the control unit and, according to a bus protocol, being supplied with instructions and operating data for its operation and receiving and transmitting useful data via the data bus, wherein, in the method of the invention,
By the invention, it is proposed in a general sense that the operational control (i.e. the management), i.e. particularly the configuration, diagnosis and state control of the transceiver, will be realized by the useful-data communication interface which exists in any case, and will be realized both for locally performed operational control and for operational control via the data bus. Thus, according to the invention, control pins and the like terminals on the side of the transceiver can be omitted. The transceiver will evaluate the communication, which communication can also be performed e.g. in accordance with the communication protocol depending on the type of data bus, and will interpret the contents of specific instructions—these may be provided e.g. also for communication of useful data—as requests for configuration, state control and/or diagnosis—and respectively for the transceiver management in general. Diagnosis information transmitted by the transceiver can be transmitted both locally and on the bus side on the communication interface of the transceiver, both toward the control unit and to the data bus.
For hardware realization of the method of the invention, it is required that the bus participant and respectively the transceiver are provided with a logic unit which is capable to receive the bus communication and the communication from the control unit and to decode it. The transmitted transceiver management data will then be interpreted and used by the transceiver in a product-specific manner.
The invention will be explained in greater detail hereunder by way of several exemplary embodiments thereof and with reference to the drawing. Specifically, the following is illustrated in the drawing:
The transceiver management communication is performed bidirectionally between the communication/control unit and the transceiver, wherein the communication or generally the transceiver management on the bus side, i.e. toward the data bus, is “not visible”, i.e. there is no communication. The communication/control unit does not participate in the external data bus communication. The transceiver will decode the management data coming from the microcontroller and will use them in an application-specific manner.
As a possible application, one can envision e.g. the configuring of the transceiver via the local communication interface (between transceiver and microcontroller) e.g. during initialization of a control device of the respective participant, with said control device not yet participating in the data bus communication. The configuration of the transceiver is exclusively performed locally. For instance, this can be the case always when a bus participant is being prepared for a specific operational state, e.g. with respect to the assignment of the ID and of the data contents in the—e.g. partial—network which is to be responded to, wherein the control device shall not actively participate in the bus communication. After e.g. a transceiver error has been detected, this transceiver and respectively the participant will be decoupled from the rest of the network, and the cause of the error can be locally detected. Further, by way of dedicated messages, the functional state of the transceiver can be locally determined, without the necessity of an active participation in the bus communication.
According to the scenario depicted in
As a possible application, there could be envisioned e.g. a bus-sided diagnosis of the transceiver while the local control device of the participant is in the switched-off state. Nonetheless, the transceiver is ready for reception, notably for management data coming from the data bus, and respectively for transmission of management data and respectively for their acknowledgement on the data bus. The transceiver can e.g. be polled from a remote site with respect to diagnosis information (e.g. state inquiry by the network management). It is possible to configure the transceiver from the bus side. If, for instance, the control device is in a state wherein only the transceiver is ready for reception, the transceiver can be provided with configuration data from a remote site (e.g. changing the configuration in the—e.g. partial—network by the network management). Also a diagnosis of the transceiver is possible from the bus side. While the local control device is in the switched-off state whereas the transceiver is ready for reception, the transceiver can be polled from a remote site for diagnostic purposes (e.g. state inquiry by the network management).
The transceiver management-data communication from the communication/control unit of the microcontroller to the transceiver is possible, wherein the configuration toward the data bus is not “visible” while, however, the ECU of the transceiver remains capable of reception (in analogy to “listen only”). The transceiver will decode these management data and will use them in an application-specific manner. An application can reside, for instance, as described above in connection with
Transceiver management-data communication is possible bidirectionally between the communication/control unit of the microcontroller and the transceiver, wherein the configuration is transparently “visible” on the data bus. The transceiver will decode these management data and will use them in an application-specific manner. As a possible application, there could be envisioned the case of an external control device which transmits network management data that will be decoded and converted by the transceiver of another participant. The local microcontroller of the addressed participant (i.e. the microcontroller within the participant) will receive these data in parallel. Further, the transceiver management can take place locally (i.e. within the participant), wherein these management data are “visible” in the entire network.
Number | Date | Country | Kind |
---|---|---|---|
12176545 | Jul 2012 | EP | regional |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/EP2013/059123 | 5/2/2013 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2014/012688 | 1/23/2014 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
7424553 | Borrelli | Sep 2008 | B1 |
7539888 | Hu | May 2009 | B2 |
8185678 | Azad | May 2012 | B1 |
8321612 | Hartwich | Nov 2012 | B2 |
9262365 | Hartwich | Feb 2016 | B2 |
9330045 | Muth | May 2016 | B2 |
20030058882 | Fleury | Mar 2003 | A1 |
20030167345 | Knight | Sep 2003 | A1 |
20040020698 | Gehrke | Feb 2004 | A1 |
20050097212 | Engel | May 2005 | A1 |
20060045123 | Gopalan | Mar 2006 | A1 |
20060252375 | Wu | Nov 2006 | A1 |
20080291986 | Lida | Nov 2008 | A1 |
20090327506 | Diab | Dec 2009 | A1 |
20100111081 | Diab | May 2010 | A1 |
20100229013 | Diab | Sep 2010 | A1 |
20110007896 | Chen | Jan 2011 | A1 |
20110022766 | Beckmann | Jan 2011 | A1 |
20110249713 | Hammarwall | Oct 2011 | A1 |
20120282875 | Park | Nov 2012 | A1 |
20140046494 | McAlister | Feb 2014 | A1 |
Entry |
---|
International Search Report and Written Opinion for corresponding patent application No. PCT/EP2013/059123 dated Jul. 29, 2013. |
Number | Date | Country | |
---|---|---|---|
20150178240 A1 | Jun 2015 | US |