ASCWriter logging inaccurate timestamps

[ludobouan]

When logging CAN messages from multiple high speed CAN buses using the notifier, messages are often not logged in chronological order. This is fine, however ASCWriter changes the message timestamp if it is logged after a message with an later timestamp. Is this the intended behavior ?
Accurate timestamps should be privileged over forcing ascending timestamps in the .asc file.

# figure out the correct timestamp
if timestamp is None or timestamp < self.last_timestamp:
    timestamp = self.last_timestamp

As you can see below this gives the false impression messages are all sent within 0.1 milliseconds

   9.3868 2  A1       
   9.3868 2  1EF  
   9.3896 2  A6        
   9.3896 2  A7          
   9.3896 2  AA     
   9.3896 2  B6          
   9.3896 2  114        
   9.3896 2  3AA
   9.3936 2  417       
   9.3936 2  25C   
   9.3936 2  FF    
   9.3936 2  A3        
   9.3936 2  AB          
   9.3936 2  B4        
   9.3951 2  202           
   9.3951 2  206             
   9.3951 2  289  

[ludobouan]

I would also like to add that the ASCWriter writes only 4 decimal points for the timestamp, whereas Vector .asc files usually have 6. In the reference cited in the docs here, you can see in the example 6 decimal points are used in the timestamp.