Good morning Peter,
you are really close to the end of the tunnel. You wrote that you use M1, why do you drive M0 with game engine?
Try: p 1 32767<13>
If you want to see movements only for one axis, try LFS.
You can see, that sway is connected to Axis1a, so you have to write in the second line of game engine:
p 1 <Axis1a> <13>.
If you are not sure where your problem is, try this:
I clicked a little app together to get a better test. You need dot net 4.6.1 to run it.
To your ASCII issue. In the firmware I sent you, I removed the bug. To this, you cannot use parameter w and r in ODrive tool anymore, but as sim rig user you will not need it.
As I told you before, ODrive is not a out of the box product. You can go and buy a ready build sim rig for thousands and thousands of €. Or you can go the stoney way and do it by yourself. We are the first people who build a sim rig with ODrive. I found nobody doing this before. So its a development process with up and downs.
During my project, I often come to a point that I thought there is no solution for my problem. But after digging and help of the community, it goes further and further, sometimes in small steps but it moves. I wait 6 weeks for the endstop firmware, without any progress.
You are in the lucky situation that somebody (me ) allready has a running configuration. You can be sure, that your project will be supported to 100%.
Greetings / Zennix