wutaijieing
commented
4 months ago 
what is it? I don't quite understand, how do I need to operate it specifically?
Open wutaijieing opened 4 months ago
wutaijieing
commented
4 months ago what is it? I don't quite understand, how do I need to operate it specifically?
AlexBAV
commented
4 months ago Sorry, those were posted by mistake.
Are you talking about export of the Raw Data View or Raw Exporter? Could you please provide more details.
wutaijieing
commented
4 months ago Sorry, those were posted by mistake.
Are you talking about export of the Raw Data View or Raw Exporter? Could you please provide more details.
In the data captured by Device Monitoring Studio, it will mark each segment of data sent or received with different colors, similar to parity discrimination. How to automatically identify these color marks in Hex Editor Neo? It is best to be able to recognize the data exported from Raw Data View. Also, the exported dmslog8 file can be opened with Hex Editor Neo by default, but it only has a regular view and cannot be visually distinguished by color in Hex Editor Neo，The description comes from Google Translate, perhaps the expression is not very clear
wutaijieing
commented
4 months ago
It looks like this effect...
AlexBAV
commented
4 months ago We internally have Hex Editor Neo's structure definition for .dmslog8 Device Monitoring Studio log file format. It decodes log data down to individual monitoring packets and may be combined with protocol definitions included in Device Monitoring Studio to decode packet data even further.
However, we don't have a finished solution for USB (we have some slightly outdated solution for serial monitoring, though).
We can privately share dmslog8.h with you so you could have a look. If you are interested in this, please send us an e-mail.
How to automatically identify the structure of USB data exported by Device Monitoring Studio in hex? Or distinguish between red and blue data blocks, etc.