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

add support fro maxus eDeliver3 #583

Merged
merged 15 commits into from
Mar 12, 2021
Merged

add support fro maxus eDeliver3 #583

merged 15 commits into from
Mar 12, 2021

Conversation

KilveEng
Copy link
Contributor

@KilveEng KilveEng commented Mar 8, 2021

added support so far for the following
SOC
pack voltage
charge power
charge amps
odometer

@dexterbg
Copy link
Member

dexterbg commented Mar 8, 2021

Shane,

thanks for the submission. I've got some minor change requests:

  • Please rename your vehicle name "eDeliver3" & component "edeliver" to include the manufacturer name first, possibly shorten both if that gets too long. Your short name "MED3" is fine.
  • Use the component specific macro in your component.mk instead of CONFIG_OVMS_VEHICLE_NONE.
  • Add some documentation, at least the usual boiler plate page containing the features supported so far. Example/template: https://docs.openvehicles.com/en/latest/components/vehicle_renaultzoe/docs/index.html – don't forget to add the link to the top level README.md.
  • Add an entry to the changes.txt file (user level change history).

Not a strict necessity, but a general recommendation: clean up your code with regards to a) code style (primarily indentation style) and b) dead code, seemingly remains of some copy & pastes from another module.

Regarding code style, there's a nice automatic tool called "astyle" for this. Example configuration: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master/vehicle/OVMS.V3/components/vehicle_vweup/src/.astylerc

You can keep this PR open, further changes submitted to your master will automatically be added here.

Regards,
Michael

@KilveEng
Copy link
Contributor Author

KilveEng commented Mar 8, 2021 via email

@dexterbg
Copy link
Member

dexterbg commented Mar 8, 2021

Shane,

create a docs directory in your component, copy the index.rst file from the Zoe component and change the content accordingly. The file will be added to the documentation menu automatically. You can test that by doing a local build, see docs/README.md on how to install sphinx locally. The link in the main README.md needs to be added manually once the URL is known. See other links there on how to form the URL.

The changes.txt grows at the top, add your entry after the "??" line. Use another "New vehicle" entry from that file as a template.

Regards,
Michael

@dexterbg
Copy link
Member

Shane, if you're having troubles with sphinx, I can do the initial docs for you.

@KilveEng
Copy link
Contributor Author

KilveEng commented Mar 11, 2021 via email

KilveEng and others added 2 commits March 11, 2021 18:37
renamed vehicle, tidy up, amend changes.text, add docs/index.rst, amends so poll changes
@dexterbg dexterbg merged commit 45e6c74 into openvehicles:master Mar 12, 2021
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

Successfully merging this pull request may close these issues.

None yet

2 participants