Hello to those techs who responded to my CAN comments
Please accept this as a generic response, as there have been quite a few questions posted.
The scope I was using is a Tektronix TDS 4000 it is quite literally brand new, as such my skills in using it are somewhat less than it's capabilities,however it does have a specific automotive triggering package CAN protocols conform to an international standard therefor we can predict common functionality with regards to message packages, the tool can trigger on edge BUS ,ID,ACK,and error frames therefor we are able to set a very accurate trigger and view data or waveforms as binary or HEX .The next development this is where I have yet to carry out I suspect a great deal of R&D is to obtain the ID codes for specific components.
Given the performance that this tool offers in terms of sample rate, memory and triggering it should then prove a simple task to fault find any data errors on CAN networks.
I do have the support a technical angel who is also able to monitor postings on this site.
I do suggest that you log on to Tektronix website via our link if you wish.
I have also spoken with Autodata and they are going to look at this issue from a different angle, I see a future need for HEX code interrogation in exactly the same way we currently use Dtc's.
I am also hopeful in the near future of working with a manufacturer on related issues.

Best regards
Frank