3
Truncate or Control display of digits for Analyzer results
- Open
- Subscribe
|
J |
Joey |
Hi,
See attached screenshots.
It would be a quality-of-life improvement for the LIN analyzer if data hex representation was 8-bit, like the data being sent on the bus. It seems like now the data is represented in the native format of the system, in my case 64 bits. This adds a lot of noise and wastes horizontal screen space.
I assume this would be a minor change, easily implemented.
Kind regards,
Joey
Activity Newest / Oldest
Tim
(#87589)
"When I display LIN in hexadecimal in the analyzer, it outputs 1Byte of data in 8Byte, which makes it difficult to work with most of the wasted fields.
Can you please make it possible to display 1Byte?
Or, if you could give priority to displaying numerical values on the back side, we would be able to see the values even if the columns are small."
Tim
Another request to fix this here:
github.com/saleae/simple-parallel-analyzer/issues/12
"SImple Parallel analyzer always shows decoded binary and hexadecimal values as 16-bit format. It would be great if it can show the value using minimum digits as decimal value shows.
The attached screenshot shows AD0~AD7 values as
decimal at ALE
hexadecimal at #RD, would be nice if it shows as 0xHH
binary at #WR, would be nice if it shows as 0b BBBB BBBB"
Luca
Same representation problem also on I2S/PCM decoder.
It could be nice to have a fix so data exported on csv can be easily elaborated with excel
Tim
(#76508)
"Hi
(am new here :-) )
How can I change the CAN to 8 bytes in the CAN Analyzer?
I get the identifier 0x0000000000000640
I only want 0x0640
I only want an 11-bit identifier instead of a 29-bit identifier
m.G. Pukshofer
p.s.:
Is there a possibility to change the program to German?"
Mark
This this a bit trickier than we would like. Technically we could just change the internal representation from integer to byte array to fix this, but that could break any high level analyzers that depend on the existing LIN analyzer data format.
This is a high priority for the next analyzer / HLA / data table refresh. Currently, we don't store any additional formatting information about the numbers we store - e.g. how many bits should be displayed.
Unfortunately, we can't simply trim leading zeros in this case, due to limitations of the data table indexing system. We need to fix that at the same time as changing the display of any data type.
I can't wait to get started on the next pass on these features, but unfortunately we're just a team of 3 developers at the moment, and can only work on one area of the app at a time.
In the meantime, it would be possible to quickly write a simple python HLA to change the format of this data, either convert it to string or to a shorter byte array, and then hide the original analyzer output from the table.
Tim
#55960
"Despite using 16 channels, you print values as 64 bit values -- this is very bad to read, even though you seem to zero the top bits.
I'm using the simple parallel analyzer, please adapt your interger size to the channel (either selected channels or maximum channels). Also, that other data (type: data, start and duration) is totally useless."
Tim
discuss.saleae.com/t/logic-2-3-9/756/10
Tim
Hi Joey, thanks for letting us know this issue. I changed the title for your post to help us find this a bit more easily. It looks like other analyzers have a similar issue, so I wanted to keep the title a bit more generic.