No need for me to show your complete quote.. but it is way above my pay grade and might as well be in Greek..
You could post your questions in the Early Adopters Forum (linked above) for a prompt response as others are doing so....just a thought...
Yeah good point, I will do so!
Trying to put it In less technical terms: it appears, from what I can see so far, that the communication between computer and DNA 40 is done by simple text commands. The computer might send a command like "set profile 1 x y z a b c" and the mod replies "OK", and that will trigger the mod to update profile 1 with data indicated by x y z a b c.
This is great, much better than the alternative which would be the PC sending unreadable (by humans) data to the mod in a special format.
In your EScribe, if you go to Tools -> Serial Terminal, I believe you will get what's called a command line interface - a blank screen in which you can type commands like I described above, and see responses from the mod. My hope is that everything the mod can do, everything the EScribe software is able to control/query on the mod, can be triggered by knowing the right command and typing it into that interface.
That would mean the main purpose of EScribe is to provide an easy-to-use front screen to what, behind the scenes, is a series of text commands sent back and forth. As opposed to EScribe being the only way to do those things (because it communicates with the mod in a human-unreadable way.)
Even better, the way the PC connects to the mod (how it knows it's plugged in; how it sends the commands I described above) appears to be a very standard, generic connection type. One that has been around for years, and that exists on all types of operating system (Mac, Linux, Android.)
Putting all this together, it appears that it would be easy to connect to the DNA 40 from any computer and to send commands to it - changing settings, getting back data. And even to replicate EScribe on those other operating systems, at least in some form.
The above is just early speculation. It could be that the command/text interface is limited to only certain commands (such as ones for getting back data, which is what the manual mentions as an example of using Serial Terminal.) Or it might not be using only the generic communication method I saw it install, that might be only part of the story.
But anyway yeah I'll post this on the Evolv forum later, and when I get my board working I will play around and see what I can do.
