Hey thats a good idea John, but again it would require some modifications to the current loggers.. I have something that might work since I allow the requestID itself to determine its length instead of `1byte or 2byte by default.

 

In mitsulogger, you can send a request that responds with 16 bytes, and I can create other requests in the XML to parse the bytes by offset (mid$) and translate them to responses. Its something even an enduser can do. This was to allow the application to evolve without constant rewrites. I'm also going to be adding a section to the XML that represents VBScript functions that will be available to the request evaluations.

 

So can I use v1.5 alpha and set the response bytes to 17 right now to read my 16 bytes (since you include the echo in your response bytes number?)

 

I think 1.5alpha is hard coded at 2 bytes, but 1.6 alpha and 1.6beta were fixed to allow variable response lengths in the XML, I'm working on getting it released this weekend. I'll try to catch you online later and get it to you to try out. I was planning on getting Innovate support into 1.6 beta 2 but this stuff is more important.