-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BYD Atto 3 setup #164
Comments
I loaded the all sensors page while connected and this is what Car scanner logged. |
@l2smith2 thanks. Can you please export the logs |
ah didnt know about that export log function |
@l2smith2 Here's what you need to set it up, Initialisation: ATS0;ATAT1;ATST96;ATSH7E7;ATFCSH7E7;ATFCSD300000;ATFCSM1; SOC: Some more info: The BYD PIDs are available this is a very useful post, although they are not using Auto pid request. The PID request for SoC is 221FFC, notice there is an additional 1 at the end. This means that it is expecting a single frame response. 221FFC without the 1 will also work. These are the parameters that I think is useful for the Initialisation. |
Ok so its now publishing soc which initially I thought was just 10% too high but it never seems to change while charging so i'm not sure what value it actually is reading. I know nothing about OBD2 and PIDs so this is a trial by fire. I'm trying to find the right documents/guides to read but I feel I'm missing something. Can you run me through how you get the PID for different values and the expression from the tx rx frames? and what those initializations are doing? Thanks for the help with this. |
@l2smith2 something does not look right. Can you please post a screenshot of your Automate page? |
{"bus":"0","type":"tx","ts":5192,"frame":[{"id":2023,"dlc":8,"rtr":false,"extd":false,"data":[3,34,0,5,170,170,170,170]}]} {"bus":"0","type":"rx","ts":44476,"frame":[{"id":2031,"dlc":8,"rtr":false,"extd":false,"data":[4,98,0,5,69,170,170,170]}]} Ok so using car scanner and looking at HV Battery SOC which is 69% currently I get this returned. Looking at the BYD seal desciption he gets {"bus":"0","type":"rx","ts":37872,"frame":[{"id":2031,"dlc":8,"rtr":false,"extd":false,"data":[7,98,31,254,44,26,152,58]}]} and converts it to
|
@l2smith2 please go back to my original configuration and change the I just removed the ATS0 command.
Yes that's normal. And keep the mqtt log disabled. |
What is the reported SoC?
You need to find the PID, checkout this post #122 12v battery voltage will be supported in the next firmware release. |
((B5*256)+B4)/100 reports the correct state of charge now, currently soc = {"SoC":87.4,"raw":"07621FFC2422653A"} I dont understand how to find the PID from https://github.com/meatpiHQ/wican-fw/discussions/122 Complete Noob |
Great! No worries, let me know which parameters you want and I can try to find it for you later. |
If we could figure out these values to start, This is from the BYD seal guy but seems the same. lowest voltage cell (3,32V): highest voltage cell (3,33V): lowest temperature cell (22 °C) highest temperature cell (23 °C) Battery total Voltage (572 V) Battery Average temperature (22 °C) |
Any Idea what these values may be? Also the meatpi seems to be the highest wifi traffic user on my network. |
@l2smith2 I'll add these to BYD car profile soon. Does your car broadcast CAN frames all the time? If so please add any fake filter to stop it. I will add a "disable mqtt publish" to stop all these frames. |
I think it has been doing that. Never really goes to sleep anymore even with voltage set high |
Which firmware version are you on? |
3.11 beta I believe |
Ok so probably it's keeping the ECU on all the time. I'll fix it and send you a firmware to try. |
It doesn't report Rx and TX msgs under separate topics in MQTT explorer either |
you can record the info you're seeing using carscanner. Once you do, share that file and I can help you set it up.
https://www.carscanner.info/records/
Originally posted by @meatpiHQ in #163 (comment)
The text was updated successfully, but these errors were encountered: