Originally Posted by
jasonjeremiah
I've decided to take up the mantel of attempting to fix the communication issues that plague newer Motorguide Xi5/Xi3 trolling motors and Lowrance units. I have pinpointed the issue to be the newer pinpoint GPS module being used in 2019+ models of the Xi5/Xi3 trolling motors. There was some programming change made that has lead to comm issues when speaking to the Lowrance units. Using the hand fob alone, the trolling motor works fine. It's when the trolling motor is networked to the Lowrance and user tries to follow a route or goto a waypoint that issues arise. Specifically, the trolling will not follow the route or it will get to the waypoint and start doing circles or other erratic behavior. I have tried every setting and combination of settings to make this work, but it will not. There are more than 50 people with the same issue and possibly hundreds, if not thousands. I know this as one of the members of the group was getting signatures together to attempt a class action lawsuit against the parent companies of both products. I spent more than a year trying to get Lowrance and Motorguide to come up with a solution, but as they were both working on new trolling motor technology, they refused to diagnose or provide a solution for the issue and in the end, stopped communicating altogether with myself, and others having the issue.
I gave up on complaining, attempting to diagnose and even caring about it anymore. I walked away from my boat and fishing and haven't even had the boat out of the garage for over a year and a half. In that time, I've gotten back into using my telescopes and astrophotography and have created some GPS/Wifi PCB circuits based on Homebrew/Arduino ESP32 microprocessor and was successful in creating an adapter that allows wireless and BT communication between my PC and the Goto mount of several of my telescopes. I've been interpreting communication packets between the two and writing software code that interprets and relays the communication. Doing this has made me think about attempting to diagnose the communication issues between the Motorguide and Lowrance products.
Based on several Youtube videos, some of which are in Spanish, I'm 99% certain this issue is related to some change made in the Pinpoint GPS module made by Motorguide. Prior to 2019, the module used had a rubber like covering and no NMEA type connectors. Trolling motors using this older GPS module have zero issues communicating with Lowrance and following routes. Sometime in late 2018 or early 2019, Motorguide started producing a new Pinpoint GPS module that has a hard plastic covering and NMEA connectors. This has been used in all Xi5's and Xi3's manufactured in 2019 + and will only partially communicate with Lowrance units. One user has successfully installed "older" Pinpoint modules on 3 different Xi5 trolling motors that previously had the newer Pinpoint modules installed and were not working properly. In one of these, the main control board had even been changed as MG thought that may be the issue. Installing an older Pinpoint module fixed the following route and goto waypoint issue that previously plagued the unit. User then put the old control board back in, and MG trolling motor and Lowrance still played nice and worked great, so it was definitely an issue in the Pinpoint module itself.
All of this tells me that there is at least partial incompatibility in the RX and TX packets being transmitted between the networked trolling motor and the Lowrance head unit. It may be something as simple as the commands being communicated as a single byte, where they should be transmitted as two bytes, or commands being echoed back to the sender. I'm wondering if the newer module has the RX/TX lines tied together? Serial commands being used may also be in an older format and coding definitions need to be defined in order to translate communication. All of this would be easy for the manufacturers of either product to diagnose with a logic analyzer and write new coding in the form of an update to fix these issues, but they've both moved on to newer technology, knowing that those of left trying to make this combo work have given up and ran out of the warranty period. I will never buy another product from either manufacturer again and know they could not care less.
What I need is a logic analyzer to plug into the NMEA 2000 network to look at the transfer packets being sent between the two and try to diagnose the discrepancy in what is being communicated and attempt to write a software update or implement a new device based on an ESP processor to do the translation TX/RX. I'm sure such an analyzer must exist. I'm wondering if it would be possible to cobble together a USB -> Serial -> NMEA connector cable of some sort to read the communication? I just get the feeling this is a simple software coding fix that if either manufacturer would seriously look into for 5 minutes (as they do have the proper tools and know the relevant coding commands) it could easily be fixed with and update. But since they will not, I would be willing to give it a go myself if I had a way to look at what's being transmitted. Anyone have any suggestions?