Menu ▾ ▴

#118 Show userdefined message output from sent from frontend

QTools
accepted
Quantum Leaps
Qspy (3)
1
2017-09-07
2016-10-19
Thomas Kaspar
No

In our current software we are using user defined qspy messages to get and set sensor/actuator states inside our target software. We implemented an own protocoll to transfere these information.
We can currently see only the messages that are sent from the target in the qspy output but we don't see the messages sent from the frontend.
The current output from target to looks as follows in the log:
0000010696 User70: 161 0 3 2 116 255
We currently use a Python script to decode this output according our protocol, but the problem is that we see only the messages from target to frontend, but not the messages from frontend to target.
Can these messages are shown in the same way as the messages from the target?
The protocol dependent conversion does not need to be done by qspy.

Discussion

  • Quantum Leaps

    Quantum Leaps - 2016-10-19
    • status: open --> accepted
     

  • Quantum Leaps

    Quantum Leaps - 2016-10-19

    The QSPY back-end could display packets received from the front-end. The front-end packets don't have a timestamp, so they could be displayed, for example, as:

    ===>target Pkt123: DE AD BE EF 12 34 56
0000010696 User70: 161 0 3 2 116 255

    This would stand out in the QSPY output.

    However, unlike the user-defined trace records from the Target, the packets from the front-end don't carry any formatting information, so it is not clear how to format the payload of such packets. The example above shows the payload as a bunch of hex bytes (similarly as the result of the PEEK command), but it is not clear that this is the best way. Please suggest a better way, if possible.

    --MMS

     

Anonymous
Anonymous

Add attachments
Cancel