01-02-2014, 05:03 PM
No, the 2.5us doesn't matter for data (because valid data has to be >3us), but for weakbits it does to be accurate.
The 0001 value is only available as 12.250-12.750, anything over 13us is considered a weakbit, and anything under 2.9us is a weakbit. 0001 is a very unique case for the ASIC, and I actually think that it is a unintentional side affect when the controller clocking exceeds the 12us range, but does not exceed some other theshold (~13us) that causes a timer reset. The range under the 1541-II and 1571 is slightly higher, up to 14us is supported as still being 0001.
The 0001 value is only available as 12.250-12.750, anything over 13us is considered a weakbit, and anything under 2.9us is a weakbit. 0001 is a very unique case for the ASIC, and I actually think that it is a unintentional side affect when the controller clocking exceeds the 12us range, but does not exceed some other theshold (~13us) that causes a timer reset. The range under the 1541-II and 1571 is slightly higher, up to 14us is supported as still being 0001.