Flex Text Commands and Responses

Yes, I have read this Wiki. Unfortunately, it is incomplete and way out of date. So, still looking for documentation. Meanwhile, I am have AI (Chat GPT) take the FlexLib C++/C# source code interface files and generate documentation. It has to infer a lot of how one would use all these methods and in what scope and sequences. So, it may not work. Ideally, it takes someone at Flex to sit down and write the explanations with examples. Anyway, that is where I am. If anyone knows of any leads on this type of documentation, please post. de WA1QZX

Yeah, I am using ChatGPT AI which is assisting me in writing a Dash Board type app for my Flex Radios (the type dash board you may commonly see inNode-Red). Except, this app is a native macOS app written using Apple Xcode / Swift / SwiftUI. Why? Because I want to learn Swift as a language. To your suggestion, I am working with AI as sort of a partner because I like to design and code - it is what I have done all my career as a professional software engineer. Anyway, I looked at this Wiki documentation and it is without a doubt, old and incomplete. And then, I fed it to AI partner to see what he/she? thought about this and after analysis it was determined by AI that the documentation does not reach the level of quality and completeness for our use. And worse, it is not up-to-date. That brought my Partner and I to 3 ideas or paths to go down: 1) Continue to look for documentation of the Flex command/response level API - that is an ongoing search - hence this post. 2) Reverse Engineer the 4.2 FlexLib C++/C# API source code and infer command/response syntax and use. 3) Write the application without a complete set of documentation - which is what we are doing now. The app is coming along well. But, when it comes to Flex Radio commands sent and received, we are basically throwing spaghetti against the wall and see what is thrown back real-time, So we are issuing commands: Flex> sub radio all , Flex> sub slice all, etc and have AI analyze the response from parser / parser log we created. That way, I and my AI partner can listen to what we call the "Radio Chatter" to see what is actually going on. By listening, recording and analyzing the data on port 4992 we can see everything as it happens and what the message formats are. BUT, We would rather have a document that explained it accurately and completely from the start, rather than sniffing around. I am still looking and asking around for documentation. I found a patchwork of attempts to write documentation, but they all appear to be dated. If you know of any documentation, please post resources. Thanks! de WA1QZX