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.

TCAN332 - DeviceNet

Other Parts Discussed in Thread: TCAN332, SN65HVD253, SN65HVD252, SN65HVD235

Hi all

Would you mind if we ask TCAN332?
Is this device avilable to used for DeviceNet?

SN65HVD252 and SN65HVD253 are optimized specially for DeviceNet as we confirmed following post. 
(https://e2e.ti.com/support/interface/industrial_interface/f/142/t/503702)
Our customer needs the device which is 3.3V version and optimized specially for DeviceNet(SN65HVD252's and SN65HVD253's 3.3V version).

We need your help.

Kind regards,

Hirotaka Matsumoto

  • Hi Hirotaka-san,

    The TCAN33x devices are superior devices to the SN65HVD252 device and meet all of the extra physical layer requirements of DeviceNet that are not described in the ISO 11898 spec. You can confirm this by looking in the datasheet at the electrical characteristic table for the TCAN332 device.

    There is a functional difference though on pin 5 of the TCAN33x devices compared to the SN65HVD55x devices. Please review these differences in the datasheet and let me know if you have any questions? Is your customer using the Vref output or the AB loopback function that are par tof the SN65HVD252 and SN65HVD253 in their system?
  • Hi Hiroyaka-san,

    After looking at the DeviceNet spec a second time I realized that the bus fault protection on the TCAN33x devices does not meet the DeviceNet spec. The TCAN33x devices suyport +/-14V while the SN65HVD252/3 devices support -36V to 40V. Is this a hard requirement for your customer or are they flexible with this particular spec? If this is a hard requirement please consider the alternative SN65HVD235 (SN65HVD23x) series of 3p3V CAN devices.