Profile: BlueFire Admin
Send me the App’s event log (Settings/Send the Event Log) and I’ll take a look. Let me know when you have sent the event log too.
Also, try the suggestions in the Getting Started document's Troubleshooting section.
https://bluefire-llc.com/store/getting-started-document
You can also query these forums for help or for others with a similar configuration.
https://rvforums.com - Do a search for BlueFire to see all the posts.
https://www.irv2.com/forums/f103/vmspc-replacement-option-425748.html - You can search other IRV2 forums using BlueFire.
The 3.22 update did not get the firmware files from our FTP server so that's why it worked. My guess is that T-Mobile is blocking all FTP access since that can be a huge file download issue on their network. I can play around with it here since I'm also a T-Mobile customer.
Nope, you're right on with the baud rate and message format. It is a constant stream of data though.
It can be totally up to the OEM engineers who program the ECMs as to what and how the data is transmitted.
Brake pressure has always been a hit a miss proposition. Try playing around with the Performance settings.
Go to the Customize Dash page and select the Full Screen option. Your dash will not be displayed in full screen mode.
Maybe try to side-load it? - https://bluefire-llc.com/store/bluefire-apps
You can also query these forums for help or for others with a similar configuration.
https://rvforums.com - Do a search for BlueFire to see all the posts.
https://www.irv2.com/forums/f103/vmspc-replacement-option-425748.html - You can search other IRV2 forums using BlueFire.
Send me the App’s event log (Settings/Send the Event Log) and I’ll take a look. Let me know when you have sent the event log too.
J1708 is a SAE standard messaging format. The hardware protocol is J1587 which is essentially RS485 but with the SAE J1587 specifications. If the other buses adhere to the J1587 and J1708 specifications then the adapter will work on them.