![]() Reloading the plan using destinations only had another problem. I turned left on Round Hill Rd and got back onto the parkway with very little southbound traffic. I exited onto Old Mill Rd, which was still slow, but faster than the parkway. ABRP did not direct me off onto Old Mill Rd, but the traffic showed clear after the Round Hill Rd exit. The traffic on the Merritt Parkway was heavy and ground to a near halt near the Old Mill Rd exit in Greenwich. It is through the Applegreen Electric network. I noticed the Wilbur Cross and Merritt Parkways have charging stations at some service areas with signs of more being installed. I exited onto Wilbur Cross Pkwy and gradually got into more areas of slowdowns. Rush hour traffic got heavy moving south. I like this route better with a right entrance to I-91 instead of a left entrance from Exit 86. ABRP directed me to Exit 87 for the airport and then to I-91 south. The typical GPS routing uses Exit 86, which was backed up. I had a late lunch at my favorite spot off of I-84 in CT, and continued over the Charter Oak Bridge (US-5/Route 15) to I-91 south. After a slight delay, the trip continued west on the Mass Pike and I-84. The Reference consumption appeared to be messed up as well. The website and phone app share the same settings. It turned off the Automatic setting because the plan was created before configuring for the BLE dongle. I had to reboot and reload the full plan into ABRP. The overheating went away when the phone was moved to another location. The phone was located to the right of the wireless charging location on the center console. The phone was also overheating and ABRP hanged on recalculating. A stop at the Framingham rest area was needed to correct things. Since the GPS indicated a position way back on the route, ABRP recalculated the charging and showed EA Auburn Mall charger as the next stop. Soon after I got on the Mass Pike (I-90), the GPS was not displaying the right location, a known bug. There was no problem reconnecting later on as long as the dongle stayed powered in the OBD2 port.Įverything seemed to be working (finally!!!) with the lunch stop showing as the next waypoint. I found out later that unplugging the dongle from the car breaks the connection between the phone and the dongle. Relinking the dongle was needed to fix it. The car was charged to 100% before the trip.ĭue to family issues, I left late the next day. I became a ABRP premium member to get Android Auto integration. MC-IOS is the BLE device and will show up in the ABRP OBD2 link setup, even on an Android phone. It was slightly confusing as the dongle shows up as two bluetooth devices, vLinker MC-Android and vLinker MC-IOS. ![]() ABRP was setup the night before a holiday weekend trip to NJ. Currently ABRP only supports BLE for OBD2 linking. The result was the Vgate vLinker MC+ supporting both regular Bluetooth and BLE. ![]() I was on the lookout for a OBD2 dongle that supported both Bluetooth Low Energy (BLE) and Ford MS-CAN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |