We have a 2024 Voyah Free model already in ABRP. Please specify the difference of your vehicle request to the one that already exists/
ABRP User #1373137
•
Oct 15
Ok, thank you for your answer! I use a Veepeak OBDCheck BLE+ Bluetooth OBD2 module, linked to ABPR, but no data is coming through. So I thought the reason for that was that behind model Voyah Free in ABPR it still says ‘estimate’. But if it only means that data should come through but not yet fully calibrated it might be the module then. Or maybe you have a suggestion to create the correct sensor to integrate… In ABPR , under live data, only the location is shown… it does however say ‘connected’ to <Car Scanner>.
Mahde - ABRP
Team•
Oct 15
Car Scanner is quite new to us in ABRP as we added it recently. Could you try doing the following to see if you can get the SoC from the vehicle?
In ABRP, go to Live Data, pick Car Scanner and copy the token. In Car Scanner, turn on its ABRP setting with that token and set their custom SoC PID as the SoC value. Then keep Car Scanner running while driving, and don't connect the dongle from ABRP's own OBD screen at the same time, because only one app can use it.
You might need to make changes to the PIDs of the vehicle if you values are not the same, but please send us the information you receive after the instructions I sent above. It might not work as it can differ from vehicle to vehicle but we will continue with other procedures to see if these give results for the SoC in your case.
ABRP User #1373137
•
Oct 15
hi, when doing the above, and choosing as a connection profile Voyah free in car scanner, there is no SOC in the listed sensors in car scanner. I tried to create a custom sensor with values I got from AI , but no data in ABRP; for example I created a request with header 7E4, command 22CF06, etc.
Mahde - ABRP
Team•
Oct 16
Do you not find the sensor named “Hybrid/EV remaining battery” in the menu “All sensors” or in the “Live data” section?
Please send a screenshot of the available sensors and info that shows up in the menu of senors and live data.
ABRP User #1373137
•
Oct 16
hi , I guess the problem is twofold here:
1. I find EV related sensors that are in the list of both <all sensors> as well as <sensors supported by car (with Voyah free set) as well as ABPR sensors (‘list of sensors that could potentially used to collect and transfer data to ABRP’) under ABPR Integration, but with the car truned on etc, none of them show a value, so likely they are not read at all:
‘search on ‘EV’
search on battery:
also no sensor with ‘hybrid/ev remaining battery’
although with a calculated custom sensor with a calculation one could use maybe the HV battery power , it does not show any live value, only OBD Module Voltage (from the unit itself probably, so not read) and the “Distance travelled’ show values live (red and yellow..) the ev related ones do not have any value:
So I guess I first need to sort out why these even in the car scanner are not pesent, let alone they are passed thorugh to ABRP ;-)
ABRP User #1373137
•
Oct 16
I also tried a few óbvious PID’s thorugh the terminal`, but no luck, all no data:
ABRP User #1373137
•
Oct 16
I guess the Voyah free profile is for the Gas version of the Voyah free…
ANd maybe Voyah just shields the EV readings?
Mahde - ABRP
Team•
Oct 19
Since Car Scanner is separate from ABRP it means that these values need to show in the chart first before it can be present via ABRP. Do the values not change when you are driving too?
ABRP User #1373137
•
Oct 23
indeed, it does not show any values while driving either (only the ones from the ODB2 unit itself, like unit voltage and gps speed, so that is a problem I need to sort out first.. No clue why it is not producing the values, the Veepeak module is used and recommended by many, so \i guess it has something to do with Voyah not serving values via the port just like that. Thnaks for thinking along , happy to hear any suggestion how to investigate that if you have any…
Mahde - ABRP
Team•
Oct 23
Are you able to choose any other OBD devices that you can test with? We have introduced Car Scanner recently to ABRP and therefore we have not been able to make many tests with it. This feedback helps us understand how it works better. Have you been able to find other users online showing which settings that have selected for the same OBD device?
ABRP User #1373137
•
Oct 23
no I onlybhave the veepeak device. im currently looking for other users, but not ine found yet … Consulting Claude on what settings might be relevant, fe niw teying a different protocol and finding out what sensors actually do give a value back
Mahde - ABRP
Team•
Oct 23
For this issue I would suggest contacting the developer which you do in the settings meny of Car Scanner and scrolling down to “Contact developer”. You can then select the issue type that best matches your current problem and they can help you with the issue.
ABRP User #1373137
•
Oct 25
Ok I have scripted (python) the search for possible candidates for sensor commands (read 19800 values out of the module and had AI analyse it ) that could represent SOC , and I have a few now that actually give values back that are corrresponding with the car’s app . I can either put the command and calculation in an existing carscanner sensor or I can create a custom sensor with a certain name. How do I make sure that ABPR takes that sensor into the live data read? Just name it ‘SOC’ (currently it only shows Location??
Mahde - ABRP
Team•
Oct 27
Could you try by changing the already existing sensor and creating a new one with the commands you have calculated? Afterwards, you go to ABRP Integration and test with both sensors at a time in “ABRP sensors”.
While the vehicle is on and Car Scanner is running, open the Live Data in ABRP. If you see SoC now then the sensor has picked it up from Car Scanner. Please send screenshots of the results you receive and of the ABRP integration menu in Car Scanner.
How to find ABRP integration in Car Scanner:
Settings → ABRP Integration
You will also have to type in vehicle token which you get when connecting the vehicle in ABRP (which you have done already, but you can find it by pressing Car Scanner option at Live Data in ABRP).
ABRP User #1373137
•
Oct 27
I had already coupled ABPR to Carscanner with the token. The thing is, If in carscanner profile Voyah Free is set, the only live data visible in ABRP is ‘location’ as in the screenshot.
In the Carscanner profile for Voyah Free, there is no standard sensor called ‘SOC’ available, so I cannot change an existing one.
So I guess I need to know how a configured sensor in Carscanner will appear in the set of live data in ABRP
If I go to ABPR sensors in Carscanner with the voyah free profile set, a list is shown, but none of these appear in ABPR. (Maybe because they are not read).
So in other words, which values does ABRP read in the CArscanner integration, so that I can assign my custom sensor to one of these values?
UPDATE: I found out where to set the sensor to be the SOC for ABRP: in the sensor setting there is an option ‘ABRP role overwrite’ which can be set to Soc. Once I did that I reconneted ABPR , and there the option appeared ‘use live data’. So now I have my Soc in ABPR.
Last question therefor, what othe values does ABRP possibly read to use in the route planner, like fe. Battery temperature etc?
Log in to comment and vote
Mahde - ABRP
Oct 15
Hello @ABRP User #1373137,
We have a 2024 Voyah Free model already in ABRP. Please specify the difference of your vehicle request to the one that already exists/
ABRP User #1373137
Oct 15
Ok, thank you for your answer! I use a Veepeak OBDCheck BLE+ Bluetooth OBD2 module, linked to ABPR, but no data is coming through. So I thought the reason for that was that behind model Voyah Free in ABPR it still says ‘estimate’. But if it only means that data should come through but not yet fully calibrated it might be the module then. Or maybe you have a suggestion to create the correct sensor to integrate… In ABPR , under live data, only the location is shown… it does however say ‘connected’ to <Car Scanner>.
Mahde - ABRP
Oct 15
Car Scanner is quite new to us in ABRP as we added it recently. Could you try doing the following to see if you can get the SoC from the vehicle?
In ABRP, go to Live Data, pick Car Scanner and copy the token. In Car Scanner, turn on its ABRP setting with that token and set their custom SoC PID as the SoC value. Then keep Car Scanner running while driving, and don't connect the dongle from ABRP's own OBD screen at the same time, because only one app can use it.
You might need to make changes to the PIDs of the vehicle if you values are not the same, but please send us the information you receive after the instructions I sent above. It might not work as it can differ from vehicle to vehicle but we will continue with other procedures to see if these give results for the SoC in your case.
ABRP User #1373137
Oct 15
hi, when doing the above, and choosing as a connection profile Voyah free in car scanner, there is no SOC in the listed sensors in car scanner. I tried to create a custom sensor with values I got from AI , but no data in ABRP; for example I created a request with header 7E4, command 22CF06, etc.
Mahde - ABRP
Oct 16
Do you not find the sensor named “Hybrid/EV remaining battery” in the menu “All sensors” or in the “Live data” section?
Please send a screenshot of the available sensors and info that shows up in the menu of senors and live data.
ABRP User #1373137
Oct 16
hi , I guess the problem is twofold here:
1. I find EV related sensors that are in the list of both <all sensors> as well as <sensors supported by car (with Voyah free set) as well as ABPR sensors (‘list of sensors that could potentially used to collect and transfer data to ABRP’) under ABPR Integration, but with the car truned on etc, none of them show a value, so likely they are not read at all:
‘search on ‘EV’
search on battery:
also no sensor with ‘hybrid/ev remaining battery’
although with a calculated custom sensor with a calculation one could use maybe the HV battery power , it does not show any live value, only OBD Module Voltage (from the unit itself probably, so not read) and the “Distance travelled’ show values live (red and yellow..) the ev related ones do not have any value:
So I guess I first need to sort out why these even in the car scanner are not pesent, let alone they are passed thorugh to ABRP ;-)
ABRP User #1373137
Oct 16
I also tried a few óbvious PID’s thorugh the terminal`, but no luck, all no data:
ABRP User #1373137
Oct 16
I guess the Voyah free profile is for the Gas version of the Voyah free…
ANd maybe Voyah just shields the EV readings?
Mahde - ABRP
Oct 19
Since Car Scanner is separate from ABRP it means that these values need to show in the chart first before it can be present via ABRP. Do the values not change when you are driving too?
ABRP User #1373137
Oct 23
indeed, it does not show any values while driving either (only the ones from the ODB2 unit itself, like unit voltage and gps speed, so that is a problem I need to sort out first.. No clue why it is not producing the values, the Veepeak module is used and recommended by many, so \i guess it has something to do with Voyah not serving values via the port just like that. Thnaks for thinking along , happy to hear any suggestion how to investigate that if you have any…
Mahde - ABRP
Oct 23
Are you able to choose any other OBD devices that you can test with? We have introduced Car Scanner recently to ABRP and therefore we have not been able to make many tests with it. This feedback helps us understand how it works better. Have you been able to find other users online showing which settings that have selected for the same OBD device?
ABRP User #1373137
Oct 23
no I onlybhave the veepeak device. im currently looking for other users, but not ine found yet … Consulting Claude on what settings might be relevant, fe niw teying a different protocol and finding out what sensors actually do give a value back
Mahde - ABRP
Oct 23
For this issue I would suggest contacting the developer which you do in the settings meny of Car Scanner and scrolling down to “Contact developer”. You can then select the issue type that best matches your current problem and they can help you with the issue.
ABRP User #1373137
Oct 25
Ok I have scripted (python) the search for possible candidates for sensor commands (read 19800 values out of the module and had AI analyse it ) that could represent SOC , and I have a few now that actually give values back that are corrresponding with the car’s app . I can either put the command and calculation in an existing carscanner sensor or I can create a custom sensor with a certain name. How do I make sure that ABPR takes that sensor into the live data read? Just name it ‘SOC’ (currently it only shows Location??
Mahde - ABRP
Oct 27
Could you try by changing the already existing sensor and creating a new one with the commands you have calculated? Afterwards, you go to ABRP Integration and test with both sensors at a time in “ABRP sensors”.
While the vehicle is on and Car Scanner is running, open the Live Data in ABRP. If you see SoC now then the sensor has picked it up from Car Scanner. Please send screenshots of the results you receive and of the ABRP integration menu in Car Scanner.
How to find ABRP integration in Car Scanner:
Settings → ABRP Integration
You will also have to type in vehicle token which you get when connecting the vehicle in ABRP (which you have done already, but you can find it by pressing Car Scanner option at Live Data in ABRP).
ABRP User #1373137
Oct 27
I had already coupled ABPR to Carscanner with the token. The thing is, If in carscanner profile Voyah Free is set, the only live data visible in ABRP is ‘location’ as in the screenshot.
In the Carscanner profile for Voyah Free, there is no standard sensor called ‘SOC’ available, so I cannot change an existing one.
So I guess I need to know how a configured sensor in Carscanner will appear in the set of live data in ABRP
If I go to ABPR sensors in Carscanner with the voyah free profile set, a list is shown, but none of these appear in ABPR. (Maybe because they are not read).
So in other words, which values does ABRP read in the CArscanner integration, so that I can assign my custom sensor to one of these values?
UPDATE: I found out where to set the sensor to be the SOC for ABRP: in the sensor setting there is an option ‘ABRP role overwrite’ which can be set to Soc. Once I did that I reconneted ABPR , and there the option appeared ‘use live data’. So now I have my Soc in ABPR.
Last question therefor, what othe values does ABRP possibly read to use in the route planner, like fe. Battery temperature etc?