[dazq]

Cant seem to get it working. Uploded my 202402 ini file , trying to connect but doesnt work. Car dies when connecting and thats it. Any ideas ?

Which serial port are you connecting too?
Realdash is best connected to serial3 ( also known as secondary serial) leaving the main serial/usb for tuning with PC etc.
Connecting to primary serial while running will cause it to restart unless you have a modified cable/serial firmware or Arduino board. It's an Arduino thing

[Toms wknd]

I tried different ini files, different realdash versions, different android devices, nothing seems to work for me. I can connect to Bluetooth no problem, but android dash wont work.

[Toms wknd]

Do i have to do something in arduino software ? i tried both, serial 0 and serial 3 . i have 3 m52 pnp boards, and none of them are connecting via bt. it just keeps repeating that its connecting to HC-06 over and over again. tried connecting with usb cable disconnected and that didn't help. i tried connecting it as megasquirt ecu, heard that people had some luck that way, but same thing. can stalls every time it tries to connect

[NickZ]

Ah HC-06, most HC-06 don't work on speeduino, You need a HC-05 bluetooth device,

[PSIG]

I'm following this thread as I've used buckets of HC-06, the Wiki outlines the use of HC-06, and most suppliers sell the HC-06. It needs to work properly in any case (along with any other serial device), so the root issue needs to be identified for if there is a problem on the Speeduino-side. Probably not, but I'm watching here.

I have had a few random issues with HC emulators/clones (non-417 chips) but nothing definitive. No need of the HC-05 Master and other modes for this application, so I don't use them (except years ago), and I have no current input or info for those. Looking forward to a resolution for the OP.

[NickZ]

I bought 100 HC-06 a few years ago, none of them would work with speeduino, Ive had problems with some HC-05. I have found 1 version of HC-05 that i don't have a problem with.

Just on a side note, I also have a shipment of CH340 chips that i opened the other week and work perfectly on a mac on a speeduino ecu, but will not work on a windows OS, comes up with Protocol error, Im guessing they are fake as the text isn't the same as the normal ones i use. But i don't understand why TS on windows has the protocol error just with that chip, my normal ch340 work fine.

[JHolland]

Just on a side note, I also have a shipment of CH340 chips that i opened the other week and work perfectly on a mac on a speeduino ecu, but will not work on a windows OS, comes up with Protocol error, Im guessing they are fake as the text isn't the same as the normal ones i use. But i don't understand why TS on windows has the protocol error just with that chip, my normal ch340 work fine.

The newer versions of the driver block counterfeit chips.

[PSIG]

+1, I use old driver versions in my Windows machines, and set Windows to never update drivers, except manually. This all started with the FTDI drivers that bricked chips years ago, but now others are using the same bad technique. Hopefully the newer blocking CH340 drivers don't permanently break the chips like FTDI did.