Sonsivri
 
*
Welcome, Guest. Please login or register.
Did you miss your activation email?
March 29, 2024, 09:34:12 09:34


Login with username, password and session length


Pages: [1]
Print
Author Topic: Suggest High-Speed CAN transceiver with Disabled and Stand-by modes.  (Read 3014 times)
0 Members and 1 Guest are viewing this topic.
Signal
Active Member
***
Offline Offline

Posts: 197

Thank You
-Given: 111
-Receive: 81



« on: August 21, 2019, 07:14:47 19:14 »

Hi, I need help.

TJA1051T/E transceiver has three modes of operation: Normal, Silent and Disabled. These modes are selected by two pins: EN and S.
In Silent mode transmitter is disabled but receiver works in fully operational mode. That mode I do not need.
In Disabled mode not only transmitter is disabled but also internal load/terminal resistors are disconnected from bus. That feature is what I found unique and what I need!
Unfortunately, in Disabled mode receiver is also completely disabled and there are no Stand-by mode as normally present in most of high speed CAN bus transceivers. In Stand-by mode transceiver detects activity on bus and interrupts/wakes up CAN controller.

So I am searching for high-speed CAN transceiver with Stand-by and Disabled (in TJA1051T/E sense) modes. Does anybody knows it?

As alternative could you suggest IC or simple circuit that could detect differential signal on bus to wake up a node that do not compromise the bus and with similar level of protection from bus?
Logged

Give a right name to a right game and play it right
bigtoy
Active Member
***
Offline Offline

Posts: 238

Thank You
-Given: 322
-Receive: 297


« Reply #1 on: August 21, 2019, 08:31:43 20:31 »

At my work we build a lot of CAN devices, and build fairly large CAN networks for industrial type applications. What I'm not understanding is WHY you want to have a disable pin on the CAN transceiver. In my experience it's not necessary. The reason I say that is that CAN is a wired-OR multidrop network. Which means the transceivers sit across the bus in a quite high-impedance state, and they don't noticeably affect the bus unless they transmit. Hence, if you want to guarantee the transceiver won't transmit, it's a lot easier to just gate the TX pin on the logic bus side of the transceiver, than it is to attempt to find a special transceiver.

You mention load resistors. They only exist on the ends of the bus. At each end of the bus there needs to be a 120 ohm resistor between CAN-H and CAN-L. You do not have load resistors at each transceiver. No matter how many transceivers you have on the bus, when a given transceiver is driving the bus it sees a load of 60 ohms (the two 120-ohms in parallel). One purpose of these two termination resistors is to bring CAN-H and CAN-L together when nobody is driving the bus. When transmitting, the transceivers drive the CAN-L / CAN-H lines apart, typically around 5V. That's all they do, and the resistors bring them back together. To create the logic zeros and ones on the bus.

Regarding transceiver choices, there are many. We use the Texas Instruments ISO1050 on most of our products. This supports isolation between the logic side and the CAN bus side, which is useful when you have different devices talking to each other which can have different grounds. If you're talking CAN within a single board, or if you have the system grounds well controlled and equal, then isolation is likely not a concern for you. In terms of protection from "bad things" on the bus (surges, ESD, etc), putting a common-mode choke on the CAN-L / CAN-H signals, close to the transceiver, can do a great deal to help slow or block such nastiness.

Waking up a node is either simple or complicated depending upon your needs. To detect bus activity it's simple - just look at the RX pin from any transceiver - it'll tell you if the bus gets driven apart (to 5V). More complicated is to know if there's a packet on the bus being addressed specifically to you - do you want to wake up for everything, or just for data for you? If you want to wake up on data just for you, you need to use the logic built into your CAN peripheral, in whatever microcontroller / CPU / etc you're using. I've worked with a number of them, and all have address filtering, interrupts and status flags, etc, for this purpose.

I hope this helps.
Logged
Signal
Active Member
***
Offline Offline

Posts: 197

Thank You
-Given: 111
-Receive: 81



« Reply #2 on: August 22, 2019, 12:44:18 12:44 »

What I'm not understanding is WHY you want to have a disable pin on the CAN transceiver.
<...>
I hope this helps.
Nope. It does not help at all. But thank you for willing to help!
I'm asking the specific question. Sorry that you do not understand why but I still need it for my specific purpose.

About "load" resistance, maybe it is my fault not to be clear or explicit enough. I wrote "internal resistors" that in data sheets are named as "input resistance". Did you noticed them before? Purpose of them (surprise) also is to be a "load" or "terminal" (for stub) but somehow weaker than main ones. Did you know about it? Even to add external additional resistors if needed is a known measure.

I am quite experienced using CAN bus as a device designer too so please do not explain me the basics. Please consider more seriously that I ask a specific question for a reason.
If this is still difficult for you then you can try to realize that you also do not understand why NXP developed TJA1051T/E with this particular feature. Do you want to convince them that it was not necessary? ;)

Quote
When transmitting, the transceivers drive the CAN-L / CAN-H lines apart, typically around 5V.
Strange part. Hope you mean 2.5 instead of 5.
Logged

Give a right name to a right game and play it right
Pages: [1]
Print
Jump to:  


DISCLAIMER
WE DONT HOST ANY ILLEGAL FILES ON THE SERVER
USE CONTACT US TO REPORT ILLEGAL FILES
ADMINISTRATORS CANNOT BE HELD RESPONSIBLE FOR USERS POSTS AND LINKS

... Copyright © 2003-2999 Sonsivri.to ...
Powered by SMF 1.1.18 | SMF © 2006-2009, Simple Machines LLC | HarzeM Dilber MC