Skip to content
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

Ford S-MAX connection #286

Open
radimsejk opened this issue Dec 17, 2024 · 11 comments
Open

Ford S-MAX connection #286

radimsejk opened this issue Dec 17, 2024 · 11 comments

Comments

@radimsejk
Copy link

Hi,

I struggle to understand data from the WICAN out of my car. I have the WICAN connected to car and paired to my WiFi. Mqtt connection also works. But:

  1. I do not understand those incoming messages
  2. I would like to extract tank level, coolant or some other engine temperature and battery voltage.
  3. Optional: I would like to extract error codes
  4. Optional: I would like to extract state of my high beam lights (Blink high beam to do some action at home)

I have Ford S-Max 2012.

Here is the monitor screen:
IMG_20241217_074609

Is there some manual or can someone help me with understanding those data? Thank you.

@meatpiHQ
Copy link
Owner

@radimsejk Please try the new Beta version, this is still not yet released. It will make it easier for you. After you update, set the protocol to AutoPid, and reboot. Then go to the Automate page, enable standard PID, select the ECU protocol and then scan for the available parameters. Let me know if you find any issues.

Make sure the unzip and upload the extracted bin file.
wican-fw_obd_v400Beta3.zip

@radimsejk
Copy link
Author

Thank you very much for fast reply. I will try it tonight.

@radimsejk
Copy link
Author

So after update I am not able to connect to my WiFi. When I connect to the Wican AP I can see all WiFi and MQTT settings is correct. But even after reboot it does not connect.

@meatpiHQ
Copy link
Owner

@radimsejk is your wifi network still using WPA2 only?

@radimsejk
Copy link
Author

Yes. I have not changed it from last time. Could it be that the stored settings is somehow corrupted? Is there a way to "factory reset" the device?

But at least even without WiFi I can see some car variables now.
IMG_20241218_072545

@meatpiHQ
Copy link
Owner

@radimsejk no the stored settings are not corrupted. In this version I enabled WPA3 with WPA2 fallback. But it seems that the fallback is not working. You should consider changing your network to WPA3.

I can compile a version with an option to select WPA2, but it's best to change to WPA3, since WPA2 is verunable.

@radimsejk
Copy link
Author

The selector for WPA would be great. I think a lot of people is still using WPA2. I will try to run the WPA3 on my network but I am afraid of problems with my other devices. I heard that it could cause problems, maybe just like the Wican fallback bug.

@radimsejk
Copy link
Author

I have verified that it works with WPA3 (tested using the hotspot on my phone). However, my home network does not support WPA3. I would greatly appreciate it if you could compile a WPA2 version or a version with a WPA selector. Thank you!

@meatpiHQ
Copy link
Owner

@radimsejk please try and let me know if it works for you.

wican-fw_obd_v400Beta4.zip

@radimsejk
Copy link
Author

radimsejk commented Dec 22, 2024

Should OTA be working? I’m unable to update from Beta 3 to Beta 4 using OTA. It says 'Updating,' but afterward, the page becomes unreachable. I have to reboot the device to get it working again, but it still runs Beta 3.

@radimsejk
Copy link
Author

I tried updating via OTA using my PC (previously, I was using my phone), and the update was successful. I can now connect to my home network with WPA2 selected. Thank you again for your help! I will proceed with the integration and report back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants