Wsjtx does however at least show what is being sent and received in two places other than the screen. In the UDP data stream, and logged in the all.txt file.
What I managed to do for my experiment is to track the all.txt file with a small node.js app, encode that message to ft8 frequency offsets and send that number via serial port to the Arduino that controls the si5351.
It is clumsy but it kinda works. And no visible latency either.?
While this is far from finished and useful, it is an idea how annoying "audio coupling" between wsjtx and a transceiver that does direct signal generation can be done with a small software shim.
In theory, it wouldn't be too hard to add optional "current message output" to existing wsjtx cat serial data, but haven't explored that yet.?
Vojislav [YU4HAK]