I grabbed a UDP conversation on my machine. There are some differences from yours. Makes me wonder if your PNP bridge app will just work on other machines as is. Unrelated, the controller knows the serial number of my machine. When the PC sends out the 010000000000... (line 12) the controller responded with my machine serial number. The SN seemed to go one way only. That is, the PC never sent the SN down. Probably not significant.
Yeah the command 01 is a read and 02 is a write...
I will put up all the current files
and generate a release tonight for people to experiment with
UPDATED
Today I put in a question about one command, we will see if they reply !
Anfang, the only real mystery right now is these little gems
0.009 PCsend 8
0000 17 00 00 00 10 00 00 00 ........
machine respond (2)
Data: 1700
0.0237 PC send 12
0000 02 00 00 00 f5 01 00 00 00 00 00 00 ............
MR (2)
Data: 0200
0.0386 PC send (12)
0000 02 00 00 00 f6 01 00 00 00 00 00 00 ............
MR (2)
Data: 0200
these are sent at start
and are also sent during homing
I am thinking they are some sort of LOCK, or they ALLOW the machine to travel past the opto-interuptor end-stops.
I think :
02 00 00 00 f5 01 00 00 01 00 00 00
see the 01 in the #8 byte of this data write at $f5 (01) ?
this happens before homing an axis
f401, f501, f601. I suspect it permits past stop movement for Z,Y and X
attached- .h files I have generated.
and a tvm920def.h file I use in c++
and also the diary of mine for the protocol! in order that I did it...... so the last line is my latest work.....
qihe.txt
anyway, all will be figured out shortly, I have not spent any time for two days, maybe tonight I will get some more done between my job.... a good challenge, also to get in another programmer mind....
I will put a data dump into it tonight so that we can do a data dump of those readout data dwords.. (readout 00 to 0x2f at startup)