mholow
commented
7 months ago This is a decent idea and something I’ve thoughts about. It’s easy to act as an e6 server (like this app does) because we don’t need to worry about the few handshake messages that get exchanged in the beginning. I’m guessing e6 actually cares about “challenge” in the handshake.
Without official documentation on that e6 interface and without having e6 myself to test, it may be difficult to implement
In theory though we do already know the format of all the e6 messages (r10api.cs) so if someone was willing to try it would entail making a new class in the connections folder that is similar to openconnectconnection.cs in the way that it opens a connection, implements a send method, and calls methods on connection manager in response to messages from e6
GhostRider076
I first want to tell you THANK YOU! This is a wonderful piece of software that you've created. It has increased my enjoyment of my simulator 100 fold. My 11 year old can now start up GS Pro in 2 clicks instead of needing me to mess with all the synchronization bugs and nonsense associated with the Garmin Golf App. Everything works perfectly now 100% of the time. The direct pc bluetooth connection is awesome software. No more garmin golf app for me. Thank you.
I am a GS Pro user AND an E6 Connect user, too. I was studying the code last weekend to try to determine how to pass through shot data captured by the bluetooth connection. I would like to send the data to an actual E6 server instead of GS Pro based on a flag in the config file.
I was thinking I could add some conditional logic to the ConnectionManager.SendShot method to send a message to the E6 server instead of GSPRO. I guess I will need to figure out what the E6 messages look like as if they were coming from the Garmin Golf App.
Any hints you could provide would be helpful and appreciated.