Hmmm.
The nature of the comms is that it is sporadic. The comms is initiated by both ends so comms being sent or received needs to be initially captured. The comms is in a range of 10 through 20 bytes at a time which is relatively small packets. It is important for the comms to be recorded quickly and that they be recorded with timestamping. Measures to ensure speed of recording and protective measures in case of some sort of failure (power, dislodged cable etc,.) are what I'm trying to reasonably define so that I can advertise on something like Freelancer.
Comms need to contain certain identifying features to help validate the data. So the filtering is removing the 'extraneous' information from th e comms frame to record only the actual data. A bit like taking the letter from the envelope. Not all comms seen on the port is valid. There will be broken frames and other 'noise'.
In terms of speed, I'd think say 20 interactions of 20 byte packages per second would be a solid start. So 400 bytes per second.
Comms in and out need to be monitored although some of the comms may not be recorded in the longer term. So if you can imagine a situation whereby comms goes out requesting something and expecting a certain reply. If that reply comes in then there would be little need to keep some of the data in the longer term. If the reply doesn't come in then a record of the attempt to communicate needs to be kept. All of this is further downstream of my immediate requirements though. For now, I need the ability to record all comms in a secure manner.
I hope this further clarifies my situation.
If I can be more precise in my initial job requirements this is the aim. Should I have a set of files through which comms is written? eg. say five(5) 1k files for the data sent and five(5) 1k files for data received?
Thanks for the reply,
|