Closed vadrianc closed 4 years ago
You are right this is not supported so far.
@vadrianc Can you provide a Pull Request to provide the missing function?
According to the AUTOSAR standard 4.0, DiagnosticLogAndTrace.pdf, Table 7-24 Assembly of Type Info, these parameter types are not included, not defined. Therefor the standard needs to be extended, before implementing something. Or do I miss something?
If this is an extension to the standard it hink this is no problem if we provide an extension in the source code. It is only important, that it will be compatible to the standard.
My idea is to not extend the standard. The PDU would be transferred as UINT and the dlt-viewer will shows this as HEX, because of the definition in the FiBEX file.
Ok then the Fibex types will be extended or based on the existent Fibex standard.
I would prefer the latter. I have to sear, if we have that FiBEX standard. Our could you send me the related informations?
Regards Olaf
Is this still an issue? Can you provide a solution for this?
As far as I know, this is still an issue. Due to project constraints, I wasn't able to to work on that.
Any Update on this issue?
No update, please reopen if still an issue.
If a hexidecimal, binary or pointer argument is sent in a DLT non-verbose packet, DLT Viewer does not display the value when applying the corresponding Fibex file.
This related to the issue reported here https://github.com/GENIVI/dlt-viewer/issues/66, since the "S_HEX8", "S_HEX16", "S_HEX32", "S_HEX64", "S_BIN8", "S_BIN16" and "S_PTR" are not parsed by the non verbose plugin and the argument type defaults to 0, which means the values are interpreted as strings.