MPSciLink

[chromguy]

I managed to get MPScandroid installed on my phone, it connected to the module, but I never get a steady light on the bluetooth module. 2 quick flashes, a pause, repeat.

This is normal for the HC-06 model we use.

[wheming]

This is normal for the HC-06 model we use.

There has been some differences we've seen in the BT modules.
As Miles stated above, this is a normal characteristic but only for some of the HC-06 we received.
Some earlier ones users will notice a constant LED when connected.

Both BT modules have a fast blink when not connected. But some havr a constant led when connected, and some have a 2-flash every 4 seconds or so.

You can verify connection by checking mpscilink version from the mpscandroid main menu:




And also check connection and SD, BT, and ECU comm status, baud rates from the Misc/Nextion Tasks / Module Settings tab:







Also, another bit of user info:
Manually sideload a display update.
Need to copy the updated MPSciLnk.tft to the root directory of your mpscilink device SD card (2GB SanDisk recommended by Morris).
Dock card in SD slot on display then power up with 5v. You can use the included wire harness and usb adapter.
Red +5v, Black (-)
When powered with a card installed, it will look for any .tft file and try to install. You can't have more than one in the sd card root directory.

Upon successful update, you will get a message on the Nextion. Power down and remove card.
Repower, and you'll see the display may be different. When you select CLOCK on the display, you should see the Nextion Verion # updated.

To get an updated Nextion display file for your display, (and this can be done without a BT connection to the device, as you'll see in the pics below.)
Open MPScandroid,
Misc/Nextion Tasks /Save Nextion Layout to Droid/
Select display size. (Downloads display file to your mpscandroid data folder on your Android.)










You'll have to transfer the file to your mpscilink device SD card.
It will be located in the following folder path:

/storage/emulated/0/Android/data/com.mpsuite.mpscandroid/files/nextion/MpSciLnk.tft

[knownenemy]

Received the MPSciLink device today!!!
I haven’t even hooked it up yet and my mind is completely BLOWN!
You guys killed it with this item.
Maybe a bit sappy, but you guys surely sacrificed your time and funds simply to enhance our little TurboMopar community, and I just can’t thank you enough.

MIND=BLOWN

Thank you 👍🏻


Sent from my iPhone using Tapatalk

[iangoround]

I got mine today too. My hardware baggie in the enclosure bag seems to be lacking the standoffs so I can hold the case together. I didn't see them floating around the box either.

Super excited to get this thing hooked up.

[wheming]

I got mine today too. My hardware baggie in the enclosure bag seems to be lacking the standoffs so I can hold the case together. I didn't see them floating around the box either.

Super excited to get this thing hooked up.

I have contacted the enclosure supplier. I don't think any of those recent ones got any. You are at least the 4th I've heard from that didn't have any.
I'll be in touch with everyone when i figure out how best to handle it.

[iangoround]

I have contacted the enclosure supplier. I don't think any of those recent ones got any. You are at least the 4th I've heard from that didn't have any.
I'll be in touch with everyone when i figure out how best to handle it.

Thats a bummer.

I might just glue the bottom parts together and use some zip ties on the top for now, or run to the hardware store and get some long machine screws.

[wheming]

Thats a bummer.

I might just glue the bottom parts together and use some zip ties on the top for now, or run to the hardware store and get some long machine screws.

Please don't.
We will make it right by getting you the proper parts.
Can you post a pic of your included hardware so i know?
The vendor will mail the standoffs directly to those missing to save time.
I just need to know who is missing them.

[minigts]

Same here, lacking the standoffs for the corners. Just identifying mine.

[iangoround]

I'm having some trouble getting it to talk to me. I've downloaded the latest Arduino drivers and can sucessfully flash the Arduino from MPTune. But if I go to MPSciLink> Version Info with the device hooked up over USB nothing happens.

On MPScanDroid 2.0.0.1 with my Pixel I've built a simple gauge layout for my LM Daytona and a profile. It seems to connect, but again asking for MPSciLink Version doesn't give me a window with the version info in it. In Nextion Tasks, the "save lst files to droid" option seemed to work and I can see the files if I go looking for them with a file manager, but when I try to send Lst files to MPSciLink it gives me the error "did not get file size confirm from device" "Save nextion layout to droid" also seems to work, but "send nextion layout to MPSciLink" gives me the error "did not get hmi file write size confirm from device." The module settings option gives me a pop up that says "did not receive the module settings from device"

The microsd card I stuck in there is a 32gb Sandisk because it's what I had laying around. Would that cause the issue?

[iangoround]

I found an older 256MB sd card and stuck that in there. Still not playing along.

[iangoround]

The SD card icon finally popped up with the 256mb card, but thats all.

here's the msgfile.txt from the sd card:

--Session started at 1 ---ecu port opened successfully at baud rate of 7812
--bluetooth info--
eeprom bt baud rate is 57600
try to open btport at 57600
btport did not respond at baud rate
btport did not respond at baud rate
try to open btport at 9600
btport did not respond at baud rate
btport did not respond at baud rate
try to open btport at 38400
btport did not respond at baud rate
btport did not respond at baud rate
try to open btport at 57600
btport did not respond at baud rate
btport did not respond at baud rate
try to open btport at 115200
btport did not respond at baud rate
btport did not respond at baud rate
try to open btport at 4800
btport did not respond at baud rate
btport did not respond at baud rate
bluetooth is not available
---Initialize Nextion Display---
successfully connected at 115200
--Other info--
mpscilink version is ver1.0.1.1
bandgap voltage is 521
analog port logging rate is 150
---------------------------------

[wheming]

The SD card icon finally popped up with the 256mb card, but thats all.

here's the msgfile.txt from the sd card:

I'm trying to add you to my messenger.

[thedon809]

I cannot monitor data with the nextion display unless I first log with my phone. Is it because im using a LM? The log button on the display seemingly does nothing.https://youtu.be/_ZO6amcNLLE

[wowzer]

thedon809, i'll hook my system back up and download the last public versions to make sure nothing is corrupted or out of sync. you do not need a sd card to monitor. i just tried it. using an LM should not matter, it's just ALOT slower. i assume the msgfile.txt file you posted is outdated? it doesn't look like the bluetooth is working based on that file. plus after you connect the first time to mpscilink with your phone it should auto connect the next time you start it.

[thedon809]

thedon809, i'll hook my system back up and download the last public versions to make sure nothing is corrupted or out of sync. you do not need a sd card to monitor. i just tried it. using an LM should not matter, it's just ALOT slower. i assume the msgfile.txt file you posted is outdated? it doesn't look like the bluetooth is working based on that file. plus after you connect the first time to mpscilink with your phone it should auto connect the next time you start it.

That was iangorounds MSG file. Not mine. My phone will auto connect most of the time. Sometimes i have to hit bluetooth off and back on. My radios do the same thing sometimes.

[wowzer]

thedon809, i'll hook my system back up and download the last public versions to make sure nothing is corrupted or out of sync. you do not need a sd card to monitor. i just tried it. using an LM should not matter, it's just ALOT slower. i assume the msgfile.txt file you posted is outdated? it doesn't look like the bluetooth is working based on that file. plus after you connect the first time to mpscilink with your phone it should auto connect the next time you start it.

[wheming]

Morris, I've been working with Ian and he is up and running now. He is also LM, and sees the same anomaly that Alex described.
After successful mpscandroid log he can log or monitor with mpscilink.
But after a power cycle, the gauge list is there, but will not start a log or monitor session with mpscilink.

[iangoround]

Commenting to hopefully fix the thread subscription notifications.

also heading to the garage with a charger for more testing.

[wowzer]

Morris, I've been working with Ian and he is up and running now. He is also LM, and sees the same anomaly that Alex described.
After successful mpscandroid log he can log or monitor with mpscilink.
But after a power cycle, the gauge list is there, but will not start a log or monitor session with mpscilink.

thx wayne, if i get time tonight i'll see if i can recreate it. otherwise might be a few days since going out of town.

so, to be clear. the only way a user can monitor or log with the device after a power cycle is to first log with mpscandroid, after which it will work properly? i assume mpscandroid is started AFTER the device is powered up. does mpscandroid connect automatically to the device after the first time?

all the gauge info is stored in the arduino eeprom after the initial log by mpscandroid. so the data must be getting "lost" or reset.

i'll also look at enhancing the log file to hopefully track down info. if you would post up again the log file after a power cycle and the unsuccessful monitor attempt i'ld appreciate it.

[iangoround]

so, to be clear. the only way a user can monitor or log with the device after a power cycle is to first log with mpscandroid, after which it will work properly? i assume mpscandroid is started AFTER the device is powered up. does mpscandroid connect automatically to the device after the first time?

Correct. The only way I can get mpscilink to log or monitor is to first get get a successful log with mpscandroid. I have to do this every time the mpscilink device is powered on. mpscandroid is started up after the mpscilink is on and the nextion display shows the sd and bt icons. mpscandroid does connect automatically to mpscilink.

Also, getting the initial successful log with mpscandroid is a bit of a hassle. I've had this problem with mpscan as well with my old FTDI cable. Last night Wayne and I were messing around with the sequence in which things were started and I found this worked about 1/2 the time to get a good log started in mpscandroid:

1. Power on mpscilink from constant 12v source
2. key on but do not start car
3. once display shows SD/BT icons, launch mpscandroid and enter the logging screen
4. start car
5. start logging in mpscandroid

I'm not sure if that problem is related to some mpscan/mpscilink/mpscandroid software issue or an oddity of my particular LM.

When I get home from work tonight I can play with it some more. What would you like me to try?