Hey Bartimaeus, saw your other thread before the reply here. This can all be done. It wasn't something I was planning to work on until early next year, but it might not take that much time to at least have this functionality crudely implemented in the beta code stage, if you are game for the protocol going through a number of revisions before it gets locked into a 'final' state. Everything on the CA is working in limited memory and assembly programming, so using strings as the ID and ASCII numbers will be tricky and might take a while, but if we just have it such that 01 = RShunt, 02 = Amps Limit, 03 = Speed Limit etc. it won't be too difficult. Most of the data is stored as either signed or unsigned 16 bit integers, so you'd have to binary format the data that way. Presuming that's no problem?Bartimaeus wrote: I'd be willing to work with whatever kind of setup you would want to go with. I was thinking that having an ISR for receiving serial that checks for a "enter config" command, and then from there the phone can send each setting one at a time with an id tag in front of it. After the cycle analyst gets the data for a setting it can send a confirmation byte that tells the phone to send the next setting.