DESIGN OF A CUSTOM ASIC INCORPORATING CAN™ AND 1 ...

DESIGN OF A CUSTOM ASIC INCORPORATING CAN™ AND 1 ... DESIGN OF A CUSTOM ASIC INCORPORATING CAN™ AND 1 ...

acumen.lib.ua.edu
from acumen.lib.ua.edu More from this publisher
15.08.2013 Views

1 – Wire® Devices Type # Table 6.3 FILHITx Bit Definitions. FILHIT2 FILHIT1 FILHIT0 Description 0 0 0 Perform A/D conversion on AN1. 0 0 1 Read Digital Input pins. 0 1 0 Write Value to Digital Output 1. 0 1 1 Write Value to Digital Output 2. 1 0 0 Change Node Address. 1 0 1 Turn off Digital Outputs 1 and 2. 1 1 1 Not Used # of CAN Nodes # of Receiving CAN Nodes Table 6.4 Test Results. CAN Bus Speed (kbps) 203 1 – Wire® Bus Speed (kbps) Hot- Swapped (1 – Wire®) Length of Test (min) Failures DS1996 3 2 1 10 14 Yes 60 No DS1996 3 2 2 10 14 Yes 60 Yes 2 DS1996 3 2 1 10 140 Yes 18 Yes 1 DS1996 3 2 2 10 140 Yes 11 Yes 1 DS1996 3 2 1 125 14 Yes 60 No DS1996 3 2 2 125 14 Yes 60 Yes 2 DS1996 3 2 1 125 140 Yes 14 Yes 1 DS1996 3 2 2 125 140 Yes 24 Yes 1 1 This failure resulted in loss of messages to the 1 – Wire® devices from the CAN bus. 2 This failure resulted in loss of messages to the 1 – Wire® devices, but did not require a hard reset. From Table 6.4, lost CAN bus messages are noted in all cases where running the 1 – Wire® bus in overdrive speed. As was the case with the test performed in Section 6.2.1.2, debugging the system found that if a CAN bus message came in while running the 1 – Wire® bus in overdrive and the 1 – Wire® devices were not all operating in overdrive speed yet, the present CAN bus message got dropped. Although, technically this is still not a failure in the sense of a catastrophic failure, it is still a problem in that if this had been a safety-critical system, any loss of data or messages could be catastrophic. When sending a 1 – Wire® command to multiple CAN nodes it was sometimes noted that the data received from the CAN nodes was not the data requested by the 1 – Wire® Master and stored by the 1 – Wire® slaves. For instance, consider the second test case in Table

6.4. There are two receiving CAN nodes and both the CAN bus and 1 – Wire® bus are operating at their slower speeds of 10 kbps and 14 kbps, respectively. Only in certain instances is data lost when it is requested from the CAN nodes. After inserting lines of debug code and recording the commands sent to the CAN nodes from the 1 – Wire® Master, no correlation is found between one particular command being sent to the CAN nodes from Table 6.4 and data loss. It was discovered, however, that in certain cases if both CAN nodes send their data before it can be fully processed by the 1 – Wire® Bus Master, data loss to the 1 – Wire® slaves occurs. This results in the first byte of requested data being overwritten by the second byte of data. The CAN node that transmits its byte of data first determines which byte of data is actually stored to the 1 – Wire® slaves. It is also discovered that there is no loss of data in the commands being send from the 1 – Wire® Master to the receiving CAN nodes. Again, a possible solution to this problem is to implement either a FIFO or a prioritized FIFO buffer to possibly prevent the data requested from the CAN nodes from being overwritten. As was mentioned in Section 6.2.1.2, another possible solution is to implement some type of handshaking or acknowledgement when the data byte requested from the CAN nodes are actually successfully stored in the memory of the DS1996 1 – Wire® devices. Even though this would impact the speed of the bus, the reliability gained by preventing data loss would greatly outweigh the reduction in data throughput. Finally, no conclusion is reached regarding the loss of data in the test cases (tests 3,4,7, and 8) where the 1 – Wire® slaves are operating at overdrive speed. It is unknown as to whether the data loss to the 1 – Wire® slaves is a result of all devices not operating in overdrive speed or if data loss is a result of both CAN nodes transmitting the requested data before the 1 – Wire® 204

6.4. There are two receiving CAN nodes and both the CAN bus and 1 – Wire® bus are<br />

operating at their slower speeds of 10 kbps and 14 kbps, respectively. Only in certain instances<br />

is data lost when it is requested from the CAN nodes. After inserting lines of debug code and<br />

recording the commands sent to the CAN nodes from the 1 – Wire® Master, no correlation is<br />

found between one particular command being sent to the CAN nodes from Table 6.4 and data<br />

loss. It was discovered, however, that in certain cases if both CAN nodes send their data<br />

before it can be fully processed by the 1 – Wire® Bus Master, data loss to the 1 – Wire® slaves<br />

occurs. This results in the first byte of requested data being overwritten by the second byte of<br />

data. The CAN node that transmits its byte of data first determines which byte of data is<br />

actually stored to the 1 – Wire® slaves. It is also discovered that there is no loss of data in the<br />

commands being send from the 1 – Wire® Master to the receiving CAN nodes.<br />

Again, a possible solution to this problem is to implement either a FIFO or a prioritized<br />

FIFO buffer to possibly prevent the data requested from the CAN nodes from being<br />

overwritten. As was mentioned in Section 6.2.1.2, another possible solution is to implement<br />

some type of handshaking or acknowledgement when the data byte requested from the CAN<br />

nodes are actually successfully stored in the memory of the DS1996 1 – Wire® devices. Even<br />

though this would impact the speed of the bus, the reliability gained by preventing data loss<br />

would greatly outweigh the reduction in data throughput.<br />

Finally, no conclusion is reached regarding the loss of data in the test cases (tests 3,4,7,<br />

and 8) where the 1 – Wire® slaves are operating at overdrive speed. It is unknown as to whether<br />

the data loss to the 1 – Wire® slaves is a result of all devices not operating in overdrive speed or<br />

if data loss is a result of both CAN nodes transmitting the requested data before the 1 – Wire®<br />

204

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!