ElectricMotorcycleForum.com
Makes And Models => Zero Motorcycles Forum | 2013+ => Topic started by: MrDude_1 on June 16, 2016, 08:43:15 PM
-
(http://zeromanual.com/images/zero-manual.png)
So I have been handed a project that I think is a great idea for the community, but I dont have time or resources to properly fill it out.
http://zeromanual.com/ (http://zeromanual.com/)
The idea is simple. The community comes together and helps fill out a wiki of how-tos, and information.
Later when someone needs something, like how to change the belt, or torque specs... they can easily look it up without pawing through 100s of forum pages.
I am the owner of the URL and pay for the server hosting, so I can say with certainty that it will be up for a very very long time. Ad free and open for everyone.
If anyone wants to add to the site, please do. Its an open wiki. I have registration required to edit, but only to keep bots and vandalism to a minimum.
-
Thanks for setting this up and hosting it. I'll do my part to fill in the areas I've bookmarked or tracked.
-
Thanks for setting this up and hosting it. I'll do my part to fill in the areas I've bookmarked or tracked.
Thanks for putting in the time on it.
Its frustrating for me, because even though I am at a PC all day, I only get a few blips of time here and there. Not enough to format large pages and articles.
For example, I stopped 4 times while writing this post, because work comes first. lol.
-
Is it possible to upload a doc to the wiki? I putted around for a few minutes but couldn't figure that out. I have an OEM manual for dis/assembly of the tail fairing I received when backchanneling with Zero that was super helpful when I did a project a couple weeks ago. A bit too cumbersome (it's maybe 7 pages with a couple dozen helpful pics/diagrams) to try and deconstruct PDF and paste into the wiki interface but happy to upload if able.
-
Is it possible to upload a doc to the wiki? I putted around for a few minutes but couldn't figure that out. I have an OEM manual for dis/assembly of the tail fairing I received when backchanneling with Zero that was super helpful when I did a project a couple weeks ago. A bit too cumbersome (it's maybe 7 pages with a couple dozen helpful pics/diagrams) to try and deconstruct PDF and paste into the wiki interface but happy to upload if able.
I keep a large repository of relevant available PDFs on a Dropbox account which I've shared privately. I'm unsure whether to host some things publicly, but it's probably a good idea.
Also, Zero may not want that released, so perhaps just list a way to contact you about it...
-
This is now significantly updated with some of the major areas I've tracked. I'm editing on a per-section basis so hopefully if others pile on we won't collide much.
http://zeromanual.com/index.php/Unofficial_Service_Manual (http://zeromanual.com/index.php/Unofficial_Service_Manual)
-
Is it possible to upload a doc to the wiki? I putted around for a few minutes but couldn't figure that out. I have an OEM manual for dis/assembly of the tail fairing I received when backchanneling with Zero that was super helpful when I did a project a couple weeks ago. A bit too cumbersome (it's maybe 7 pages with a couple dozen helpful pics/diagrams) to try and deconstruct PDF and paste into the wiki interface but happy to upload if able.
I keep a large repository of relevant available PDFs on a Dropbox account which I've shared privately. I'm unsure whether to host some things publicly, but it's probably a good idea.
Also, Zero may not want that released, so perhaps just list a way to contact you about it...
I'm happy to send it to you and you can host it from your dropbox if you wish. I'll continue to one-off email it to those that request it. Zero and I collaborated for a week getting this project done and instruction manual authored and I was told it will be hung on their website, so I can't envision any issues with hanging it on the wiki.
-
I'm happy to send it to you and you can host it from your dropbox if you wish. I'll continue to one-off email it to those that request it. Zero and I collaborated for a week getting this project done and instruction manual authored and I was told it will be hung on their website, so I can't envision any issues with hanging it on the wiki.
Excellent.
I just went through the setup process and you can now upload the following file types:
png, gif, jpg, jpeg, pdf, ppt, jp2, webp, doc, docx, xls, xlsx.
To upload a file, look to the left side of the site, and "upload file" should be under tools.
This also lets you upload images for diagrams and such.
I will eventually make it so you can embed and show the PDF on the page without downloading it, but that takes more setup time and I am currently at work.
-
I just tested the PDF upload with Burton's diagram for 2013 Model S. Seems to work perfectly for linking. I'll have to research what I need to do to enable embedding PDFs.
Let me know if you have any issues.
-
Before getting too deep, would it be worthwhile to think a bit more about the site's topography? I see some "MY2013" type headings, and that's good, but is there a way to break it down by model number as well? Seems rather painful and inefficient to sort through all the model years and models to get the information relevant to my bike.
Granted, wikis are known for their search utilities, but is there a quick and easy way to organize things up front?
-
Before getting too deep, would it be worthwhile to think a bit more about the site's topography? I see some "MY2013" type headings, and that's good, but is there a way to break it down by model number as well? Seems rather painful and inefficient to sort through all the model years and models to get the information relevant to my bike.
Granted, wikis are known for their search utilities, but is there a quick and easy way to organize things up front?
Yeah, there is alot of content on one page at the moment. I am kind of letting it organically flush itself out.
As more stuff piles up under one heading, it will be changed into a link and moved to a separate page.
Theres a hard balancing act here..
on one hand if you split things up too fine, you get alot of dead or empty links and its hard to read through.
on the other hand, if you dont split things off, it all piles up into one HUGE page that is impossible to look through.
Any user can make a new page, Im not restricting it. Right now though I think people are just trying to get the info they had trouble finding earlier, out into the wiki.
-
Before getting too deep, would it be worthwhile to think a bit more about the site's topography? I see some "MY2013" type headings, and that's good, but is there a way to break it down by model number as well? Seems rather painful and inefficient to sort through all the model years and models to get the information relevant to my bike.
Granted, wikis are known for their search utilities, but is there a quick and easy way to organize things up front?
Yeah, there is alot of content on one page at the moment. I am kind of letting it organically flush itself out.
As more stuff piles up under one heading, it will be changed into a link and moved to a separate page.
Theres a hard balancing act here..
on one hand if you split things up too fine, you get alot of dead or empty links and its hard to read through.
on the other hand, if you dont split things off, it all piles up into one HUGE page that is impossible to look through.
Any user can make a new page, Im not restricting it. Right now though I think people are just trying to get the info they had trouble finding earlier, out into the wiki.
Agreed about all of this. I did realize I put charger options in when I should have just described the charging inputs and behavior. So that'll get split out shortly.
-
Before getting too deep, would it be worthwhile to think a bit more about the site's topography? I see some "MY2013" type headings, and that's good, but is there a way to break it down by model number as well? Seems rather painful and inefficient to sort through all the model years and models to get the information relevant to my bike.
Granted, wikis are known for their search utilities, but is there a quick and easy way to organize things up front?
This topic hits on information architecture, but for now it's easier to say "here's a table of brake pads by model year" than to look up model year and see a separate document and have to click elsewhere to find comparisons. It's a tradeoff, and I'm with MrDude on letting it evolve a bit and err on the side of "getting the info put together first" and sort it out later.
-
Just a quick one to say thanks for doing this Mr Dude. I look forward to having a look round and hopefully contributing myself.
-
Hope Zero is watching this post and assist in providing some info.
-
Just a quick correction on the front page:
This wiki is not affiliated by Zero Motorcycles at all. It is maintained by riders just like you.
Should read
This wiki is not affiliated with Zero Motorcycles at all. It is maintained by riders just like you.
Or affiliated to would work. I hope you don't mind me pointing this out - it's just one of the first things new visitors will read.
-
Just a quick correction on the front page:
This wiki is not affiliated by Zero Motorcycles at all. It is maintained by riders just like you.
Should read
This wiki is not affiliated with Zero Motorcycles at all. It is maintained by riders just like you.
Or affiliated to would work. I hope you don't mind me pointing this out - it's just one of the first things new visitors will read.
funny, I thought I already fixed that. I must not have clicked save.
No problem. Point out stuff. Im working full time with a newborn at home, so my work so far could be described as sporadic and sleep-deprived at best.
-
What a great resource!
Let's all read it and fix any issues and improve and expand it!
-
Where's the information about using the Zero as an off-grid power storage? i.e. 12VDC output at 100A+ or the nominal battery pack voltage for conversion to 110/220VAC. I've only seen hints on the forum about a product available that makes this possible.
-
Where's the information about using the Zero as an off-grid power storage? i.e. 12VDC output at 100A+ or the nominal battery pack voltage for conversion to 110/220VAC. I've only seen hints on the forum about a product available that makes this possible.
Someone knowledgeable about that will have to speak up about it, or you'll have to do the legwork to find out. :)
I've added some known lighting modifications and hard case options.
-
This is interesting for the wiki, a quick seat release:
http://electricmotorcycleforum.com/boards/index.php?topic=4612.msg31318#msg31318 (http://electricmotorcycleforum.com/boards/index.php?topic=4612.msg31318#msg31318)
-
I've compiled a brake pad table which is probably correct but took a ton of sifting through forums and my own brake pad replacement receipts, AND a belt replacement procedure compiled from three forum threads and some very helpful comments and photos on a Facebook thread.
http://zeromanual.com/index.php/Unofficial_Service_Manual#Brakes (http://zeromanual.com/index.php/Unofficial_Service_Manual#Brakes)
http://zeromanual.com/index.php/Unofficial_Service_Manual#Belt_Replacement (http://zeromanual.com/index.php/Unofficial_Service_Manual#Belt_Replacement)
-
This is interesting for the wiki, a quick seat release:
http://electricmotorcycleforum.com/boards/index.php?topic=4612.msg31318#msg31318 (http://electricmotorcycleforum.com/boards/index.php?topic=4612.msg31318#msg31318)
Filed under "advanced modifications": http://zeromanual.com/index.php/Advanced_Modifications (http://zeromanual.com/index.php/Advanced_Modifications)
-
I'm still compiling information, since I have some free time for a little while these days. I only know so much, so mainly I'm trying to figure out reliable conclusions from forum threads and such, so coverage is definitely incomplete.
One request: Mediawiki's WYSIWYG editor support would probably encourage more people to contribute. The owner / site admin needs to enable it IIRC.
-
I'm still compiling information, since I have some free time for a little while these days. I only know so much, so mainly I'm trying to figure out reliable conclusions from forum threads and such, so coverage is definitely incomplete.
One request: Mediawiki's WYSIWYG editor support would probably encourage more people to contribute. The owner / site admin needs to enable it IIRC.
I'll go look into that right now.
I prefer writing in code, but I am a programmer... lol
-
One request: Mediawiki's WYSIWYG editor support would probably encourage more people to contribute. The owner / site admin needs to enable it IIRC.
I'll go look into that right now.
I prefer writing in code, but I am a programmer... lol
Thanks! I am too, by profession, but a little usability for simple editing should go a long way.
-
One request: Mediawiki's WYSIWYG editor support would probably encourage more people to contribute. The owner / site admin needs to enable it IIRC.
I'll go look into that right now.
I prefer writing in code, but I am a programmer... lol
Thanks! I am too, by profession, but a little usability for simple editing should go a long way.
agreed.
the VisualEditor extension looks like the way to go with this. Im uploading it now, but the Parsoid service is a prerequisite. That install is a little more involved, so I may have to wait until I get home before I can set it up.
-
That is far better than the basic RTF support I'd seen before. Good luck with the install/config!
-
That is far better than the basic RTF support I'd seen before. Good luck with the install/config!
thanks. I just took a backup of everything... just in case. lol.
-
I'm still compiling information, since I have some free time for a little while these days. I only know so much, so mainly I'm trying to figure out reliable conclusions from forum threads and such, so coverage is definitely incomplete.
...
It's incomplete but it is improving rapidly. This should rapidly become the master repository of knowledge and summary of the conclusions of these forum threads.
-
I'm amazed at how quickly the wiki is developing. I think it's mostly Brian's hard work and dedication at the moment. Plus Mr Dude's efforts to get the wiki up and running, administer it and so on. I can't fathom how either of them have managed to put so much time in!
What's really great about this is that there is already a strong foundation of info there which will encourage people to visit and contribute.
Some of you may recall I started a thread on this forum for useful resources. The wiki deserves to be at the top of the list! :-)
-
I haven't had much time to add to it yet, but I wanted to thank you guys for getting this going. It'll be a very good resource!
One tangential question. What do you think about making the content free under the Creative Commons BY-SA license? (https://creativecommons.org/licenses/by-sa/4.0/) That way, anyone who wishes to copy (archive, fork, print, ...) would be free to do so. A good example of a site using this license is Wikipedia. If you scroll to the very bottom of their home page, you'll see:
This page is available under the Creative Commons Attribution-ShareAlike License.
What that may mean, though, is that if we copy text and pictures from this forum over to the wiki, we may have to ask permission of the forum writer first. Unless... Is the content on this forum under CC BY-SA ?
-
I haven't had much time to add to it yet, but I wanted to thank you guys for getting this going. It'll be a very good resource!
Man, I agree can't say how much I agree! This is epic, and a gamechanger, and (again) just plain stupid epic for us on the forum. Many, many kudos to Brian and Mr Dude, but everyone else who had a hand in it as well, for making this possible. I may not agree with everyone all the time, but that's the power of the wiki!
-
First off an apology for not having more done... While it is up and running, the nicer editor is not working yet. Partly because its on a FreeBSD box and there are no directions for making it run off that (so I have alot of research in "why doesnt this part work") and partly because I have both a newborn AND im buying a house. very little free-time besides lulls at work.
I haven't had much time to add to it yet, but I wanted to thank you guys for getting this going. It'll be a very good resource!
One tangential question. What do you think about making the content free under the Creative Commons BY-SA license? (https://creativecommons.org/licenses/by-sa/4.0/) That way, anyone who wishes to copy (archive, fork, print, ...) would be free to do so. A good example of a site using this license is Wikipedia. If you scroll to the very bottom of their home page, you'll see:
This page is available under the Creative Commons Attribution-ShareAlike License.
What that may mean, though, is that if we copy text and pictures from this forum over to the wiki, we may have to ask permission of the forum writer first. Unless... Is the content on this forum under CC BY-SA ?
the forums agreement is here: http://electricmotorcycleforum.com/agreement.txt (http://electricmotorcycleforum.com/agreement.txt)
Apparently nothing posted here is copyrighted. Atleast thats my read of this section:
You also agree not to post any copyrighted material unless you own the copyright or you have written consent from the owner of the copyrighted material.
as for the wiki.. at this time theres no copyright or license selected. Personally I consider everything about it to be public domain, but I havent really even given much thought about it. I certainly do not think I "own" the content on there, even though I pay for the server... And I cant see how any one person can claim ownership of a document that is community created. I would imagine that currently its as free as it can get. A lawyer may argue that theres no explicit right to copy, but who has the rights to ownership to ask in the first place?
Im just avoiding all that by leaving it mildly ambiguous and not worrying about it. I'll only structure it if some legal issue pops up. For example years ago I ran into an issue with trademarks and fair use. Thats why there is a disclaimer on the bottom of every page of the zero wiki. Its dumb but if zero didnt protect their trademark and let me use it without that disclaimer, they could end up losing control of their trademark. I can avoid the whole issue with a simple disclaimer saying they own the rights, and claiming fair use... and they're safe, im safe and we all move on happy.
-
Usual disclaimer I'm not a lawyer however I saw someone mention Public Domain and felt compelled to speak up about it.
Having no copyright (i.e. the use of term Public Domain) is the same as having an undefined copyright which is then exploitable by a bad actor to extort your users for settlement money and court costs, or at the very least a DMCA takedown notice and warrantless wiretap / request to compel the service provider to identify users. Good ol' hollywood-cronyism and terrorism-fearing USA, and all countries under its trade agreement influences. If you happen to be from Germany, things get even more complicated with libel and reputation of the authoring person factoring into matters of copyright.
So yeah if this is something we're at all concerned about, having correct attribution for information and media sources (including our own under a legitimate copyright license) is important. Just so you know!
-
Agreed about copyright; pretty sure the site owner just hasn't filled one in and will do so once they think it through. CC BY-SA would fit my publication intent, anyway.
-
That's weird, how would running on FreeBSD have anything to do with the absence of the editor? I thought the editor would be client-side, anyway. Maybe the thing to do is get the latest version of the wiki platform in tarball form and use that instead of what the latest one that came with that version of FreeBSD is. Though, it could be something as simple as a config file option to be set.
First off an apology for not having more done... While it is up and running, the nicer editor is not working yet. Partly because its on a FreeBSD box and there are no directions for making it run off that (so I have alot of research in "why doesnt this part work") and partly because I have both a newborn AND im buying a house. very little free-time besides lulls at work.
I haven't had much time to add to it yet, but I wanted to thank you guys for getting this going. It'll be a very good resource!
One tangential question. What do you think about making the content free under the Creative Commons BY-SA license? (https://creativecommons.org/licenses/by-sa/4.0/) That way, anyone who wishes to copy (archive, fork, print, ...) would be free to do so. A good example of a site using this license is Wikipedia. If you scroll to the very bottom of their home page, you'll see:
This page is available under the Creative Commons Attribution-ShareAlike License.
What that may mean, though, is that if we copy text and pictures from this forum over to the wiki, we may have to ask permission of the forum writer first. Unless... Is the content on this forum under CC BY-SA ?
the forums agreement is here: http://electricmotorcycleforum.com/agreement.txt (http://electricmotorcycleforum.com/agreement.txt)
Apparently nothing posted here is copyrighted. Atleast thats my read of this section:
You also agree not to post any copyrighted material unless you own the copyright or you have written consent from the owner of the copyrighted material.
as for the wiki.. at this time theres no copyright or license selected. Personally I consider everything about it to be public domain, but I havent really even given much thought about it. I certainly do not think I "own" the content on there, even though I pay for the server... And I cant see how any one person can claim ownership of a document that is community created. I would imagine that currently its as free as it can get. A lawyer may argue that theres no explicit right to copy, but who has the rights to ownership to ask in the first place?
Im just avoiding all that by leaving it mildly ambiguous and not worrying about it. I'll only structure it if some legal issue pops up. For example years ago I ran into an issue with trademarks and fair use. Thats why there is a disclaimer on the bottom of every page of the zero wiki. Its dumb but if zero didnt protect their trademark and let me use it without that disclaimer, they could end up losing control of their trademark. I can avoid the whole issue with a simple disclaimer saying they own the rights, and claiming fair use... and they're safe, im safe and we all move on happy.
-
It looks like they've gone to 3rd party plugins to make this happen.
https://www.mediawiki.org/wiki/WYSIWYG_editor (https://www.mediawiki.org/wiki/WYSIWYG_editor)
You're running version 1.26.3
This plugin should probably work:
https://github.com/Mediawiki-wysiwyg/WYSIWYG-CKeditor (https://github.com/Mediawiki-wysiwyg/WYSIWYG-CKeditor)
It's close, the most recent version it appears to have been adapted to is 1.26.2. Any problems should be really really minor.
-
That's weird, how would running on FreeBSD have anything to do with the absence of the editor? I thought the editor would be client-side, anyway. Maybe the thing to do is get the latest version of the wiki platform in tarball form and use that instead of what the latest one that came with that version of FreeBSD is. Though, it could be something as simple as a config file option to be set.
Im trying to setup the VisualEditor extension.
The Parsoid service is a prerequisite.
There are no direct directions on what I need to do to get Parsoid running on the FreeBSD server.
I tried the obvious developer install directions, but had a bunch of errors.
Im working though it one step at a time. I got a few tips on what to look at and setup from someone that did it before.
When Im done, I'll probably edit THEIR wiki with how to get it working on FreeBSD.. lol
as to why the Visual Editor extension when the other one is easier? Because its a much better editor. I think having the better editor will help us keep a better wiki. Even if it is more work.
Why does it need special setup? Because you have to translate between Wiki markup and HTML that is what the Parser Service does.
-
Do you have a capture of the error output?
Is there any content in /var/log/parsoid/parsoid.log (or similar)?
-
I've added a Usage article (commuting, sport, offroad, travel): http://zeromanual.com/index.php/Usage (http://zeromanual.com/index.php/Usage)
Naturally, I deal with commuting and travel, mainly, so wrote about those so far.
-
I just went to copy a couple files into the wiki and realized I never turned on drag and drop.
Now if you want to add images or files to a wiki page, you can drag and drop them into the editor, upload them from there, and insert links or images as needed.
-
I just went to copy a couple files into the wiki and realized I never turned on drag and drop.
Now if you want to add images or files to a wiki page, you can drag and drop them into the editor, upload them from there, and insert links or images as needed.
Thank you! Upload has been a little tedious, but mainly trying to crop and scale photos offline and then go through the form to see them on the page.
Do you have the chance to add a default copyright declaration option like CC-SA or public domain?
-
That's weird, how would running on FreeBSD have anything to do with the absence of the editor? I thought the editor would be client-side, anyway. Maybe the thing to do is get the latest version of the wiki platform in tarball form and use that instead of what the latest one that came with that version of FreeBSD is. Though, it could be something as simple as a config file option to be set.
Im trying to setup the VisualEditor extension.
The Parsoid service is a prerequisite.
There are no direct directions on what I need to do to get Parsoid running on the FreeBSD server.
I tried the obvious developer install directions, but had a bunch of errors.
Im working though it one step at a time. I got a few tips on what to look at and setup from someone that did it before.
When Im done, I'll probably edit THEIR wiki with how to get it working on FreeBSD.. lol
Hey, I work on unix systems quite a bit. If you'd like a hand with it, shoot me a message.
-
I just went to copy a couple files into the wiki and realized I never turned on drag and drop.
Now if you want to add images or files to a wiki page, you can drag and drop them into the editor, upload them from there, and insert links or images as needed.
Thank you! Upload has been a little tedious, but mainly trying to crop and scale photos offline and then go through the form to see them on the page.
Do you have the chance to add a default copyright declaration option like CC-SA or public domain?
I'll make a note to do that tomorrow morning at work. Im running out the door now and unlikely to get to it tonight.
Plus I have to read whats different between them. lol.
as far as photos go, I use this:
https://imageresizer.codeplex.com/ (https://imageresizer.codeplex.com/)
once installed, you can just right click on some images in windows explorer, and bulk resize.
You can also rotate that way if needed.
then drag/drop into the editor.
click upload
and add inline as needed from the upload links.
from 2 pdfs to wiki page, I did this in about 1 minute flat, but I'm all setup to do stuff like this at work, and I have insane upload speed.
http://zeromanual.com/index.php/FX_Chain_OEM_install_instructions (http://zeromanual.com/index.php/FX_Chain_OEM_install_instructions)
-
Hey, I work on unix systems quite a bit. If you'd like a hand with it, shoot me a message.
I might do that tomorrow. its frustrating me.
-
Thank you! Upload has been a little tedious, but mainly trying to crop and scale photos offline and then go through the form to see them on the page.
as far as photos go, I use this:
https://imageresizer.codeplex.com/ (https://imageresizer.codeplex.com/)
once installed, you can just right click on some images in windows explorer, and bulk resize.
You can also rotate that way if needed.
then drag/drop into the editor.
click upload
and add inline as needed from the upload links.
from 2 pdfs to wiki page, I did this in about 1 minute flat, but I'm all setup to do stuff like this at work, and I have insane upload speed.
http://zeromanual.com/index.php/FX_Chain_OEM_install_instructions (http://zeromanual.com/index.php/FX_Chain_OEM_install_instructions)
I didn't mean technically how to crop and resize, but the fact that I'm cropping and resizing offline and then looking online after upload; so I'm thankful for easier upload.
Hopefully, that'll help a Windows user, of course.
-
Good progress on the wiki manual, guys! Let's keep at it, update it to reflect the communal knowledge we've gained on these forums (fora?)
-
Thank you! Upload has been a little tedious, but mainly trying to crop and scale photos offline and then go through the form to see them on the page.
as far as photos go, I use this:
https://imageresizer.codeplex.com/ (https://imageresizer.codeplex.com/)
once installed, you can just right click on some images in windows explorer, and bulk resize.
You can also rotate that way if needed.
then drag/drop into the editor.
click upload
and add inline as needed from the upload links.
from 2 pdfs to wiki page, I did this in about 1 minute flat, but I'm all setup to do stuff like this at work, and I have insane upload speed.
http://zeromanual.com/index.php/FX_Chain_OEM_install_instructions (http://zeromanual.com/index.php/FX_Chain_OEM_install_instructions)
I didn't mean technically how to crop and resize, but the fact that I'm cropping and resizing offline and then looking online after upload; so I'm thankful for easier upload.
Hopefully, that'll help a Windows user, of course.
Probably.. its only 90% of the worlds PCs. :p
-
My free time will be scarce again soon, but I feel like most of the knowledge captured on this forum and from hearsay has been transferred to the wiki.
I will be glad when I can just browse the wiki instead of dealing with people being jerks on this forum, taking the opportunity to mock or twist others' words so they can "well, actually" everything to posture themselves as superior.
-
I expended the section on removing the tail plastics (http://zeromanual.com/index.php/Unofficial_Service_Manual#Tail_Plastics) and added some photos. In doing so, I noticed that some of my photos were not rotated properly so I fixed them and tried to re-upload them. Unfortunately, I don't seem to have the necessary privilege to overwrite current photos (so I changed the names and duplicated them).
Note how it's asking if I want to replace the current file but doesn't give me the option to do it.
-
I expended the section on removing the tail plastics (http://zeromanual.com/index.php/Unofficial_Service_Manual#Tail_Plastics) and added some photos. In doing so, I noticed that some of my photos were not rotated properly so I fixed them and tried to re-upload them. Unfortunately, I don't seem to have the necessary privilege to overwrite current photos (so I changed the names and duplicated them).
Note how it's asking if I want to replace the current file but doesn't give me the option to do it.
I removed all the duplicated files.
You should be able to click each image to open its page.
From there you should have a link to "Upload a new version of this file"
-
I've added pictures and write-up on replacing front brake lever. Can someone please edit for me? I don't know what I'm doing on formatting or style.
I will also be attempting a touring windscreen, top rack, handlebar guards, and accessory plug install... documenting everything with pictures. Please help yourselves to edit or re-arrange my contributions.
-
I've added pictures and write-up on replacing front brake lever. Can someone please edit for me? I don't know what I'm doing on formatting or style.
I will also be attempting a touring windscreen, top rack, handlebar guards, and accessory plug install... documenting everything with pictures. Please help yourselves to edit or re-arrange my contributions.
That's awesome! Don't worry about the wiki niceties yet. Until we get a nicer editor, it's totally understandable to not want to fiddle with the formatting guide using random punctuation to finesse it. I'm glad to help make it look nice.
Also, it's good that you're going through this now while writing it down, because my bike and probably others' who are helping are already customized so we've forgotten what it's like and don't have stock bikes to photograph.
-
the brake pads section of the manual is confusing and wrong in regards to the '15 and '16 FX. The FX has a different front pad than the rest of the model line.
I've edited the page. Feel free to check my work, I dunno what I'm doing just yet.
-
the brake pads section of the manual is confusing and wrong in regards to the '15 and '16 FX. The FX has a different front pad than the rest of the model line.
I've edited the page. Feel free to check my work, I dunno what I'm doing just yet.
It looks good, and is much appreciated. Honestly, putting together the brake pads table was super-confusing trying to sort out who got what right, and which model they reported on (because no one's very clear about their own model - it's always just "my bike").
-
Thanks for all the work you're putting in! It's a great idea!
-
The FX has a different front pad than the rest of the model line.
Thank you! This is the kind of stuff thats close to impossible to figure out by searching the forum.
-
What is the preferred image size and format for images on the Wiki?
-
What is the preferred image size and format for images on the Wiki?
Oh, I don't know. Look at the dimensions of the photos there. I suppose I tend to downsize each dimension to 25% of original and keep the aspect ratio.
The goal is to present whatever is being talked about at just enough resolution to identity but not too big to break up the reading flow. Also no one needs to see every last scratch in a metal surface; too much detail is distracting.
-
Just to put it out there, I'd pay for good instructions on how to perform the "Drive Motor commissioning and timing" service every 8,000 miles or 12 months now required on all 2016 models (http://www.zeromotorcycles.com/owner-resources/) using the Sevcon (http://www.sevcon.com/products/2-wheel-pure-ev.aspx) Handheld Calibrator (P/N 662/14050).
Those seem to run about $450 to buy or $50/week to rent at thunderstruck-ev.com (http://www.thunderstruck-ev.com/sevcon-gen4-hand-held-calibrator.html) (Sevcon P/N 662/14050). Looks like you'd still need to build/buy a harness and the instruction manual doesn't clarify the calibration process for me on a first pass. It's significantly cheaper than the $900 (http://www.electricmotorsport.com/ev-parts/controllers/calibrators-programmers/sevcon-gen4-36-48-275.html) software package and probably easier to use.
-
Just to put it out there, I'd pay for good instructions on how to perform the "Drive Motor commissioning and timing" service every 8,000 miles or 12 months now required on all 2016 models (http://www.zeromotorcycles.com/owner-resources/) using the Sevcon (http://www.sevcon.com/products/2-wheel-pure-ev.aspx) Handheld Calibrator (P/N 662/14050).
Those seem to run about $450 to buy or $50/week to rent at thunderstruck-ev.com (http://www.thunderstruck-ev.com/sevcon-gen4-hand-held-calibrator.html) (Sevcon P/N 662/14050). Looks like you'd still need to build/buy a harness and the instruction manual doesn't clarify the calibration process for me on a first pass. It's significantly cheaper than the $900 (http://www.electricmotorsport.com/ev-parts/controllers/calibrators-programmers/sevcon-gen4-36-48-275.html) software package and probably easier to use.
Yes, that's something I've considered. I have the harness and a laptop with older DVT; just need to walk through it from start to finish with someone who's done it before, and understand how not to screw it up.
-
Just to put it out there, I'd pay for good instructions on how to perform the "Drive Motor commissioning and timing" service every 8,000 miles or 12 months now required on all 2016 models (http://www.zeromotorcycles.com/owner-resources/) using the Sevcon (http://www.sevcon.com/products/2-wheel-pure-ev.aspx) Handheld Calibrator (P/N 662/14050).
Those seem to run about $450 to buy or $50/week to rent at thunderstruck-ev.com (http://www.thunderstruck-ev.com/sevcon-gen4-hand-held-calibrator.html) (Sevcon P/N 662/14050). Looks like you'd still need to build/buy a harness and the instruction manual doesn't clarify the calibration process for me on a first pass. It's significantly cheaper than the $900 (http://www.electricmotorsport.com/ev-parts/controllers/calibrators-programmers/sevcon-gen4-36-48-275.html) software package and probably easier to use.
holy crap you're right.. page 6.5 of the 2016 S-models manual (english)...
Well that sucks. Is it free for the dealership to do it? 8000 miles, thats like every 4 months.
-
Just to put it out there, I'd pay for good instructions on how to perform the "Drive Motor commissioning and timing" service every 8,000 miles or 12 months now required on all 2016 models (http://www.zeromotorcycles.com/owner-resources/) using the Sevcon (http://www.sevcon.com/products/2-wheel-pure-ev.aspx) Handheld Calibrator (P/N 662/14050).
Those seem to run about $450 to buy or $50/week to rent at thunderstruck-ev.com (http://www.thunderstruck-ev.com/sevcon-gen4-hand-held-calibrator.html) (Sevcon P/N 662/14050). Looks like you'd still need to build/buy a harness and the instruction manual doesn't clarify the calibration process for me on a first pass. It's significantly cheaper than the $900 (http://www.electricmotorsport.com/ev-parts/controllers/calibrators-programmers/sevcon-gen4-36-48-275.html) software package and probably easier to use.
holy crap you're right.. page 6.5 of the 2016 S-models manual (english)...
Well that sucks. Is it free for the dealership to do it? 8000 miles, thats like every 4 months.
Haha...go look at the rider log thread and see how many Zero owners are putting on 2K miles per month. Granted it's a relatively small sample set but I don't think there are that many out there. The most I put on my bike in one month was the first month I bought it and I did 1500 miles and I have put 13K total in 2 years (anniversary is 1 August!). I don't have a car and ride year round but my commute is only 21 miles round trip. I'm sure guys in the South and on the coast get closer to 2K per month but it's just hard to rack em up when it takes an hour of charging to go 10 miles. We'll see how much that changes when I finally get the Super Charger.
Regardless your point about frequency is valid. 8K is not a lot even if you only put 1K or even 500 per month. I would hope the calibration would at least be covered for the first 5 years while the power train is under warranty but what happens after that??
I wonder if this is unique to the IPM and thus doesn't apply to FX and S/DS ZF9.8?
Sent from my Nexus 6P using Tapatalk
-
Yep. Added touring screen http://zeromanual.com/index.php/Common_Modifications#OEM_Touring_Screen (http://zeromanual.com/index.php/Common_Modifications#OEM_Touring_Screen)
I really wasn't sure where to put the piping, all I had to go on was the image on Zero's product page for that accessory. The instructions that were included are for model year 2013 and the brackets look different. I'll come back to this to fill out tools needed, but I was in a rush and it was getting dark outside when I took the pictures.
Having the touring screen directs a lot of the wind away from the area between the windscreen and the rider's chest. It's great. You shouldn't have a bike without one. I think my range is affected positively by the windscreen, but that might have something to do with the windscreen's effects allowing me to concentrate on riding at a more consistent speed.
-
Yep. Added touring screen http://zeromanual.com/index.php/Common_Modifications#OEM_Touring_Screen (http://zeromanual.com/index.php/Common_Modifications#OEM_Touring_Screen)
I really wasn't sure where to put the piping, all I had to go on was the image on Zero's product page for that accessory. The instructions that were included are for model year 2013 and the brackets look different. I'll come back to this to fill out tools needed, but I was in a rush and it was getting dark outside when I took the pictures.
Having the touring screen directs a lot of the wind away from the area between the windscreen and the rider's chest. It's great. You shouldn't have a bike without one. I think my range is affected positively by the windscreen, but that might have something to do with the windscreen's effects allowing me to concentrate on riding at a more consistent speed.
Nice! It's an MRA screen, and their instructions are not much better, but windscreens are pretty easy to figure out.
It does, then, sound like the touring windscreen is better than the commuter windscreen for drag and comfort, which makes sense to me having installed an MRA spoiler to get the same effect a while ago. I would say you should expect a 5-10% range increase for 55mph, and probably more like 15% when you're a bit tucked.
I only went beyond this screen because tucking leads to fatigue and I wanted an all-day canopy experience. I am still considering a glider canopy or something similarly ambitious as Craig Schultz's front design once I clear some simpler hurdles.
-
I have an " exploded view" pdf of the 2014 FX.
Is it already in the unofficial manual, or should I add it?
Sent from my XT1585 using Tapatalk
-
I have an " exploded view" pdf of the 2014 FX.
Is it already in the unofficial manual, or should I add it?
Add it if it is your original work. Respect the copyright laws and intellectual property issues.
-
I'm still the primary contributor to this website by far. I'm wondering what factors inhibit participation:
- Time.
- Knowledge.
- Wiki syntax.
- Editing difficulties due to large pages or not knowing where to add things.
- Generally feeling intimidated.
The documentation is large enough now to split up into more pages, and has enough to motivate some rationales for how to organize it. On the other hand, shaping a wiki into pages usually is never reversed because of the effort involved.
Is the wiki already useful enough that it's unclear how to improve it?
-
In my case it is lack knowledge and the fact that I haven't even had to perform any chassis maintenance so far on my Zero, so I have no real specific experience to pass along that would be useful. Good for me, not so good for the Manual.
-
Regardless your point about frequency is valid. 8K is not a lot even if you only put 1K or even 500 per month. I would hope the calibration would at least be covered for the first 5 years while the power train is under warranty but what happens after that??
I wonder if this is unique to the IPM and thus doesn't apply to FX and S/DS ZF9.8?
I looked all through the Owner's Manual for my 2015 FX and could not find that. Whew!
-
I'm still the primary contributor to this website by far. I'm wondering what factors inhibit participation:
- Time.
- Knowledge.
- Wiki syntax.
- Editing difficulties due to large pages or not knowing where to add things.
- Generally feeling intimidated.
The documentation is large enough now to split up into more pages, and has enough to motivate some rationales for how to organize it. On the other hand, shaping a wiki into pages usually is never reversed because of the effort involved.
Is the wiki already useful enough that it's unclear how to improve it?
I'm trying to put together a "How to Charge" section using the different methods and chargers and combination of methods,etc.. I've found that in my quest to look for info, it's scattered all over in forums, FB and the internet, and not in one location.
-
I'm trying to put together a "How to Charge" section using the different methods and chargers and combination of methods,etc.. I've found that in my quest to look for info, it's scattered all over in forums, FB and the internet, and not in one location.
That's a good idea, and highlights how difficult it is to organize this information, because you'll wind up having to link to or duplicate descriptions of the charging circuits and how the bike behaves, and then the Usage page covers commuting and touring which treat charging differently!
I look forward to the results, but will try to think of a way to organize it as well.
-
Just found this ... looks like a fantastic resource -- many thanks!
-
I'm still the primary contributor to this website by far. I'm wondering what factors inhibit participation:
- Time.
- Knowledge.
- Wiki syntax.
- Editing difficulties due to large pages or not knowing where to add things.
- Generally feeling intimidated.
For me it's mostly Time. I've expended sections using my own photos when I could, but I still have lots of pictures that I took while working on the bike that I haven't had time to incorporate into the wiki due to other priorities. This wiki is AWESOME though! And it follows the usual trend of wikis: 90% of the wiki is maintained by 10% of the people (or maybe even 99% / 1%, I'm just making those numbers up, but you get the idea...)
-
I'm still the primary contributor to this website by far. I'm wondering what factors inhibit participation:
- Time.
- Knowledge.
- Wiki syntax.
- Editing difficulties due to large pages or not knowing where to add things.
- Generally feeling intimidated.
For me it's mostly Time. I've expended sections using my own photos when I could, but I still have lots of pictures that I took while working on the bike that I haven't had time to incorporate into the wiki due to other priorities. This wiki is AWESOME though! And it follows the usual trend of wikis: 90% of the wiki is maintained by 10% of the people (or maybe even 99% / 1%, I'm just making those numbers up, but you get the idea...)
It's generally 80/20, but 90/10 happens so yes I do take your point. I'm glad it is awesome - sometimes I need to look something up and realize that it's actually not too hard to read and is sort of well-organized, and then I'm pleasantly surprised by information someone added.
On the other hand, I'm wary of being a power-user (using both site search and page search to navigate) and missing out on how to make it easier to get into.
I was reminded this weekend of some super-basic things that we could cover and haven't. Mainly mechanical replaceability where Zero wisely picked, say, footpeg mounts that match other bikes. I just don't know how to confirm that quickly other than with my V-Strom.
-
On a regular basis I read something and go "ooh, that looks like something I can add"... and then I find its already been added.
This morning I found out the gauge clusters pre-2013 bikes were made by Koso.
2008-2011 Koso XR-SR
2012-2013 Koso RX-1N
So I went to add in that useful info.. but it was already there.
Its been suggested to add part numbers for things that people swap around, like the sprocket/gears... but since we all know we cant directly order zero parts anyway, its not easy to add.
-
I've updated a variety of topics recently given a number of things I've heard, measured, and observed:
http://zeromanual.com/index.php?title=Special:RecentChanges&from=20160918000000&to=20160920000000 (http://zeromanual.com/index.php?title=Special:RecentChanges&from=20160918000000&to=20160920000000)
We do need someone with an FX to step up about supporting that platform, which I have so little access to that I'm avoiding documenting in detail.
-
I was reminded this weekend of some super-basic things that we could cover and haven't. Mainly mechanical replaceability where Zero wisely picked, say, footpeg mounts that match other bikes. I just don't know how to confirm that quickly other than with my V-Strom.
For each part we really just need one popular bike that uses the same parts. For example, I am looking to upgrade the foot pegs on my 2014 Zero S. Now that I am putting on more miles per day the stock foot pegs just aren't cutting it.
I would like to get a set of these pegs from Revzilla that have rubber padding and flip out heel rest for longer rides. But they need a bike specific mount. I'm sure the mount that is meant for some other bike will work fine for the Zero...but which one?? I'm tempted to buy the mount for a bunch of different bikes and hope that I find one that works and then return the rest...of course...I really don't want to do that....but I really want more comfortable pegs. I know I could just use DS pegs as suggested during our conversation...which would definitely be better than the S/SR pegs....but I think I could do better...if I just knew which mount.
http://www.revzilla.com/motorcycle/kuryakyn-switchblade-foot-pegs (http://www.revzilla.com/motorcycle/kuryakyn-switchblade-foot-pegs)
-
I'm still the primary contributor to this website by far. I'm wondering what factors inhibit participation:
- Time.
- Knowledge.
- Wiki syntax.
- Editing difficulties due to large pages or not knowing where to add things.
- Generally feeling intimidated.
The documentation is large enough now to split up into more pages, and has enough to motivate some rationales for how to organize it. On the other hand, shaping a wiki into pages usually is never reversed because of the effort involved.
Is the wiki already useful enough that it's unclear how to improve it?
This might sound daft, but the platform and my daily routines probably have something to do with it. I keep up with the forum thanks to Tapatalk on my phone. It's something I check during lunch breaks (like now). It's very convenient and easy to view content and do a quick reply to a forum post. Using a web browser on a phone is more awkward and often requires two hands. One to hold the phone, one to zoom in and out. Also, updating a wiki feels a bit more involved and more like doing real work at a desk, rather than just idly texting.
I can't say time, because one way or another I've spent many hours on here thanks to my phone and Tapatalk. Perhaps it's context. When I'm sat at a desk, it's always at work and I'm always busy enough to need to focus on that.
Great work though Brian! I'll be sure to pay the wiki a visit soon and I do want to make some time to contribute if I have some worthwhile material.
-
Or maybe I'm just a bone idle lazy bum? I'll let you decide... ;-)
-
You're not lazy or daft. Updating a wiki is definitely involved. I'm a little disappointed that MrDude wasn't able to install some kind of wysiwyg editor. I know PHP is a royal pain on some levels so am not criticizing. Hopefully something can be done to make it more accessible.
I will say that I often keep the syntax reference open in a browser window just to sort out my edits, especially for tables.
For what it's worth, there are apps for Wikipedia which format it really well and add ways to navigate more easily on a mobile device. I should see whether I can get a good experience by targeting our wiki with one of those.
-
You're not lazy or daft. Updating a wiki is definitely involved. ...
I will say that I often keep the syntax reference open in a browser window just to sort out my edits, especially for tables.
For what it's worth, there are apps for Wikipedia which format it really well and add ways to navigate more easily on a mobile device. I should see whether I can get a good experience by targeting our wiki with one of those.
It's not that complicated but it's definitely not optimized for phone use. Mostly is a matter of making sure you're registered, logged in, and clicking edit. I always preview before posting, but it's better to make incremental improvements rather than to hold back because it's not perfect. It can't be improved if it was never entered.
-
Bumping the thread to indicate some updates and promote awareness since the FB group often has questioners who are unaware of it:
State of purpose extended a bit: http://zeromanual.com/index.php/Why_an_unofficial_wiki%3F (http://zeromanual.com/index.php/Why_an_unofficial_wiki%3F)
Common Mods grew enough to warrant an outline: http://zeromanual.com/index.php/Common_Modifications (http://zeromanual.com/index.php/Common_Modifications)
The manual is growing by quite a bit and I spent time hunting down a bunch of factoids to clarify whatever I could. http://zeromanual.com/index.php/Unofficial_Service_Manual (http://zeromanual.com/index.php/Unofficial_Service_Manual)
I added a State of Charge section in the battery area just to try to tackle that conceptually.
-
More updates:
- Usage for travel (http://zeromanual.com/index.php/Usage#Travel) got some expansion.
- The Buyers Guide (http://zeromanual.com/index.php/Potential_Buyers_Guide) got detail about charging, range, maintenance, and repair (http://zeromanual.com/index.php?title=Potential_Buyers_Guide&curid=163&diff=943&oldid=726).
- Aftermarket (http://zeromanual.com/index.php/Zero_Aftermarket) for suspension and brakes (http://zeromanual.com/index.php?title=Zero_Aftermarket&curid=10&diff=940&oldid=860).
- The manual itself got a lot of re-organization around brakes, wheels, and suspension (http://zeromanual.com/index.php?title=Unofficial_Service_Manual&curid=9&diff=946&oldid=907), but also some updates about precharge, throttle troubleshooting, and lifting the bikes with stands.
-
You're doing incredible work on the wiki!
-
Could the Wiki have a section to post questions? I know its basically what we do on the forum but sort of like a "want to buy" or "looking for" section maybe titled "want to know" or "seeking answers"
Sometimes it's hard to think of info to put out unless there is a need to remind someone of what they already know.
-
Could the Wiki have a section to post questions? I know its basically what we do on the forum but sort of like a "want to buy" or "looking for" section maybe titled "want to know" or "seeking answers"
Sometimes it's hard to think of info to put out unless there is a need to remind someone of what they already know.
Good point! I think we're finally at the point where the questions don't overwhelm the lack of answers.
That's what discussion pages are for, if you've ever poked around Wikipedia long enough. Each page gets a "discussion" page where you can post. Click on the "discussion" tab for any page to make/update one.
I made a trivial start for the Manual page:
http://zeromanual.com/index.php/Talk:Unofficial_Service_Manual (http://zeromanual.com/index.php/Talk:Unofficial_Service_Manual)
-
I considered NEW2Elec's question further, that there's room for something high-level like the Usage page for problems that might require a combination of solutions, like:
- reducing standover height
- staying warm in cold weather
- getting more performance
- trading performance for efficiency
- offroad customizations
- carrying larger cargo items
Aside: while editing this morning, the site went down ("Cannot access the database"). Hopefully that's temporary or just for periodic maintenance.
-
I considered NEW2Elec's question further, that there's room for something high-level like the Usage page for problems that might require a combination of solutions, like:
- reducing standover height
- staying warm in cold weather
- getting more performance
- trading performance for efficiency
- offroad customizations
- carrying larger cargo items
Aside: while editing this morning, the site went down ("Cannot access the database"). Hopefully that's temporary or just for periodic maintenance.
I should have been notified if it was down for any reason. I'll go pull up the logs now.
-
Aside: while editing this morning, the site went down ("Cannot access the database"). Hopefully that's temporary or just for periodic maintenance.
I should have been notified if it was down for any reason. I'll go pull up the logs now.
Thanks for bringing the site back up! Had it run out of temp directory space or such?
-
Aside: while editing this morning, the site went down ("Cannot access the database"). Hopefully that's temporary or just for periodic maintenance.
I should have been notified if it was down for any reason. I'll go pull up the logs now.
Thanks for bringing the site back up! Had it run out of temp directory space or such?
To be honest, I cant be 100% positive. The site was up and functioning normally when I was there, but I did have a notice from the hosting company about server upgrades and potential downtime of 15mins. I think you were there while they were doing their hardware upgrade. its all working now.
While I was there, I also added the apple-compatible bookmarking/fav icons... I noticed how often it was hit in the log, so just made some.
-
Weird. Thanks for the favicons.
-
To support software log analysis for other owners (helping us understand what our bikes do, what's normal and what's not normal, and comparing bikes), I've compiled a table to decode all VINs across all models and years:
http://zeromanual.com/index.php/Unofficial_Service_Manual#VIN (http://zeromanual.com/index.php/Unofficial_Service_Manual#VIN)
Thankfully, decoding logs is only relevant for 2013+ models, where the VIN codes are relatively stable.
I am very glad to say that we can just write "S platform" (S/DS/SR/DSR/SP/DSP/SRP/DSRP) or "X platform" (FX/FXS/FXP/FXSP/FXL/FXLP/X/XU/MX) to be very clear about the cluster of models that all share the same frame and general body plan. And that on top of that, folks at Zero will actually know what we're talking about and not think of us as confused rubes!
The only real surprise was the 2014 FXL and FXLP, which I've never heard of and aren't in any documentation I can find other than the one VIN table for the 2014 X platform.
Also: WHEW. That was extremely tedious work.
-
Just wanted to jump in and say thanks to all the guys who made the manual possible!
-
I've added an ergonomics page, which is a mixture of critical-tending descriptions and general solution outlines. It would be better if maybe I or someone could sort of describe what body types fit what bikes, just as a more positive tone. There's plenty to add like highway peg possibilities or the tank grips to help with crouching or something.
Any thoughts?
http://zeromanual.com/index.php/Ergonomics (http://zeromanual.com/index.php/Ergonomics)
-
I've also updated the aftermarket charging section. I'm careful about talking about DigiNow since I'm sort of an insider but I think it comes out in a fair way.
http://zeromanual.com/index.php/Zero_Aftermarket#Level_2_AC (http://zeromanual.com/index.php/Zero_Aftermarket#Level_2_AC)
-
I've also updated the aftermarket charging section. I'm careful about talking about DigiNow since I'm sort of an insider but I think it comes out in a fair way.
http://zeromanual.com/index.php/Zero_Aftermarket#Level_2_AC (http://zeromanual.com/index.php/Zero_Aftermarket#Level_2_AC)
if you want to make an insider diginow page of whatever info you're allowed to make public, go for it.
-
I updated the travel section recently: http://zeromanual.com/index.php/Usage#Travel (http://zeromanual.com/index.php/Usage#Travel)
I re-organized it quite a bit, and highlighted some basic calculations to illustrate what effects charging and streamlining could have on travel. It should be easier to follow now.
I used the Charge Tank as a charging benchmark along with a generic 1C capability as the upper end of the range.
For aerodynamics, I just assumed stepwise reductions in drag down to 70% of stock.
This is a draft for an interactive document I'm working on to simulate electric motorcycle travel, to see how well it can be explained and planned.
-
In researching to replace my turn signal bulbs with LEDs, I learned a lot about the stock bulbs, so I posted the info in the relevant section of the manual. I'll post an entry on my final product when done.
Sent from my Z981 using Tapatalk
-
Received a MY13-16 Drop Bars (Non-Police) accessory kit from Zero and so added some pictures to the unofficial manual. The package was not guarded well and suffered damage in shipping, so I tried again and the next attempt survived shipping and had a slightly different label from Zero.
-
Received a MY13-16 Drop Bars (Non-Police) accessory kit from Zero and so added some pictures to the unofficial manual. The package was not guarded well and suffered damage in shipping, so I tried again and the next attempt survived shipping and had a slightly different label from Zero.
Thanks! I see you got the bolts I was missing and the bottom plate. I got a pretty bare-bones set, just enough to make work, I suppose, maybe a dealer leftover but given my source it's understandable.
Did the bolt descriptions I gave match well enough?
-
I'll just quickly recap some changes:
Long-term storage elaboration:
http://zeromanual.com/index.php/Usage#Storage (http://zeromanual.com/index.php/Usage#Storage)
Re-organized L2 chargers:
http://zeromanual.com/index.php/Zero_Aftermarket#Level_2_AC (http://zeromanual.com/index.php/Zero_Aftermarket#Level_2_AC)
Anderson connectors (basic overview):
http://zeromanual.com/index.php/Anderson_connector (http://zeromanual.com/index.php/Anderson_connector)
FX dummy plug photo contributed:
http://zeromanual.com/index.php/Common_Modifications#FX_Dual_to_Single_Battery (http://zeromanual.com/index.php/Common_Modifications#FX_Dual_to_Single_Battery)
Travel gets its own page now (my agenda showing):
http://zeromanual.com/index.php/Travel (http://zeromanual.com/index.php/Travel)
EV charging guide, with links to charging networks, and how to figure out whether you can unplug that car:
http://zeromanual.com/index.php/EV_Charging#Other_EVs (http://zeromanual.com/index.php/EV_Charging#Other_EVs)
-
Excellent! Thank you for all the hard work.
-
Received the ChargeTank Hardware And Inlet Bracket Kit p/n #12-08047XX (old p/n 12-0804713) (http://zeromanual.com/index.php/Zero_Aftermarket#OEM_Charge_Tank). Taking pictures will do a write-up if I can figure out how it is supposed to mount.
For various parts received do we want to keep this information inline or should we refer to a single listing of Zero OEM parts and p/n's? It seems that a table of known part numbers with associated installation write-ups might be handy.
*edit* added link to section being worked on (http://zeromanual.com/index.php/Zero_Aftermarket#OEM_Charge_Tank)
-
Received the ChargeTank Hardware And Inlet Bracket Kit p/n #12-08047XX (old p/n 12-0804713). Taking pictures will do a write-up if I can figure out how it is supposed to mount.
For various parts received do we want to keep this information inline or should we refer to a single listing of Zero OEM parts and p/n's? It seems that a table of known part numbers with associated installation write-ups might be handy.
A table is a good way to get people to fill in more data and understand the part numbering system or something. It's more work, but you went through all that trouble on the torques table, and this should be easier (since it's partial) than that? I may regret claiming that, though...
-
A table is a good way to get people to fill in more data and understand the part numbering system or something. It's more work, but you went through all that trouble on the torques table, and this should be easier (since it's partial) than that? I may regret claiming that, though...
The torques (fastener specifications) table is flawed; the source of information should be in a database, and the view be a windowed query embedded as a table. When making a write-up on belt adjustment say, I'd like there to be an embedded table view that shows only the relevant datum for axle bolt, belt tensions, sorted on the model(s) and year(s) we are interested in.
I could not figure out how this would work from within Media Wiki. I'll get back to the fastener specifications when there's a way to make it more useful in write-ups. There's plenty of fastener specifications that are either not in the owners manuals and/or are standard engineering values. On that note, I don't have an engineering degree. Is there some well known reference to figure out what torque value is? A brief search engine attempt shows several fastener manufacturers guides and recommendations, but is there a recommended source of information that should be preferred to cite when no official recommendation is available?
-
A table is a good way to get people to fill in more data and understand the part numbering system or something. It's more work, but you went through all that trouble on the torques table, and this should be easier (since it's partial) than that? I may regret claiming that, though...
The torques (fastener specifications) table is flawed; the source of information should be in a database, and the view be a windowed query embedded as a table. When making a write-up on belt adjustment say, I'd like there to be an embedded table view that shows only the relevant datum for axle bolt, belt tensions, sorted on the model(s) and year(s) we are interested in.
Yes, a wiki is just a document and the table system falls over beyond sorting.
At some point, I'm strongly considering shifting to Github where I can colócate documents with a database-backed application without losing my patience with system administrative overhead. (Postgres with caching and some React thrown in front, say, with cloud style hosting)
In the meantime, I'll go check to see whether the wikidata project has an answer for this specific case built into mediawiki.
I could not figure out how this would work from within Media Wiki. I'll get back to the fastener specifications when there's a way to make it more useful in write-ups. There's plenty of fastener specifications that are either not in the owners manuals and/or are standard engineering values. On that note, I don't have an engineering degree. Is there some well known reference to figure out what torque value is? A brief search engine attempt shows several fastener manufacturers guides and recommendations, but is there a recommended source of information that should be preferred to cite when no official recommendation is available?
Okay, so your concern is already limiting what we put in there so that makes it not theoretical.
If we infer data points, we'd want to make that reasonably obvious.
I don't know sources like this myself. Maybe someone else knows.
-
Just a note that I'm really busy in the last couple of weeks, so I haven't done much with the wiki and am way behind reading forum threads.
-
Now playing with LibreOffice Base 5.3 for a forms database, also purchased a calipers and a few fastener thread guides. Goal is to design a database that can soak up all of the "meat space" specifications we can know about for export to the wiki, or maybe as some kind of complementary thing that can be referenced from the wiki.
Notably I remember being asked to confirm what kind of fasteners were part of the Non-Police DS Drop Bar kit. I had not the means then to be sure, but that along with other things I can physically measure will become part of the database.
LibreOffice Base 5.3 and newer use Firebase 3.0 which has some useful database features over the earlier use of Firebase 2.5
-
sounds to me like this database is a great fit for Ruby on Rails hosted on Heroku using Postgresql. All free
using github for the repo.
-
sounds to me like this database is a great fit for Ruby on Rails hosted on Heroku using Postgresql. All free
using github for the repo.
Want to set up that web backend? I can do data entry and form the database structure and some of the queries I'd want to see. Having a technical database as a companion to the unofficial manual wiki makes a kind of sense.
Open for comment, does this idea fit well with the wiki?
-
sounds to me like this database is a great fit for Ruby on Rails hosted on Heroku using Postgresql. All free
using github for the repo.
Want to set up that web backend? I can do data entry and form the database structure and some of the queries I'd want to see. Having a technical database as a companion to the unofficial manual wiki makes a kind of sense.
Open for comment, does this idea fit well with the wiki?
I see it as a just being a link (as it is now from the index) to the web site on heroku.
I think we would need guest and admin profiles so the average user does not accidentally change any data. What do you think?
I can do it and post a link here for you to look at and give feed back.
-
I see it as a just being a link (as it is now from the index) to the web site on heroku.
I think we would need guest and admin profiles so the average user does not accidentally change any data. What do you think?
I can do it and post a link here for you to look at and give feed back.
I'm open to either approach, for a web database app and edit data online, or a view-only web app that any changes made are commits to the git repo.
For example of usage I would like to include in the wiki a reference to fastener torque value for a 2012 MX swingarm main pivot bolt. The URL http://x.yz/ZeroMotorcycles/2012/MX/SwingarmMainPivotBolt (http://x.yz/ZeroMotorcycles/2012/MX/SwingarmMainPivotBolt) would emit a table view of the related data. MediaWiki would be configured to accept an IFrame embed from that URL path so that this appears seamless when being viewed by any user.
-
I see it as a just being a link (as it is now from the index) to the web site on heroku.
I think we would need guest and admin profiles so the average user does not accidentally change any data. What do you think?
I can do it and post a link here for you to look at and give feed back.
I'm open to either approach, for a web database app and edit data online, or a view-only web app that any changes made are commits to the git repo.
For example of usage I would like to include in the wiki a reference to fastener torque value for a 2012 MX swingarm main pivot bolt. The URL http://x.yz/ZeroMotorcycles/2012/MX/SwingarmMainPivotBolt (http://x.yz/ZeroMotorcycles/2012/MX/SwingarmMainPivotBolt) would emit a table view of the related data. MediaWiki would be configured to accept an IFrame embed from that URL path so that this appears seamless when being viewed by any user.
Just a rough cut (not sure about the Citation bit, I just made it text) Play around with it let me know if you want more fields. Styling will come latter.
table on server (https://peaceful-basin-65567.herokuapp.com/fasteners)
-
Just one mention about this plan..
the idea of the Wiki is to contain the information on in the wiki. NOT to link to external sources. While they can of course be referenced, the information needs to still be in the wiki site itself.
Otherwise you're dependent on another website to be up and useful. The entire point is so that if this board were to crash and go away, or someones random personal page with good info was to disappear, you would still have all the info you need in one place. The wiki itself is professionally hosted, backed up and maintained in a data center with mirrors in 3 physically different parts of the country.. so it should never be "lost". But anything it links to can be.
Im still lost on how some static data belongs in a different database. I dont know if you're aware, but everything in the wiki, is in a database, complete with versioning history and everything. nothing is lost.
-
Just one mention about this plan..
the idea of the Wiki is to contain the information on in the wiki. NOT to link to external sources. While they can of course be referenced, the information needs to still be in the wiki site itself.
Otherwise you're dependent on another website to be up and useful. The entire point is so that if this board were to crash and go away, or someones random personal page with good info was to disappear, you would still have all the info you need in one place. The wiki itself is professionally hosted, backed up and maintained in a data center with mirrors in 3 physically different parts of the country.. so it should never be "lost". But anything it links to can be.
Im still lost on how some static data belongs in a different database. I dont know if you're aware, but everything in the wiki, is in a database, complete with versioning history and everything. nothing is lost.
I would suggest heroku is a far more stable host than this site, as often I find it down. Heroku is a professional hosting server that many companies use. Admittedly this is on a hobby dev within the server (which is free hosting up to 10,000 rows in the DB)
You can read about it here (https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier).
Ultimately BrianTRice should have the last say as to what he wants or what is a good idea as its his baby. I will just go with the flow.
A real DB lets you run queries to subset the data so thats the advantage as Shadow pointed out.
-
Just one mention about this plan..
the idea of the Wiki is to contain the information on in the wiki. NOT to link to external sources. While they can of course be referenced, the information needs to still be in the wiki site itself.
Otherwise you're dependent on another website to be up and useful. The entire point is so that if this board were to crash and go away, or someones random personal page with good info was to disappear, you would still have all the info you need in one place. The wiki itself is professionally hosted, backed up and maintained in a data center with mirrors in 3 physically different parts of the country.. so it should never be "lost". But anything it links to can be.
Im still lost on how some static data belongs in a different database. I dont know if you're aware, but everything in the wiki, is in a database, complete with versioning history and everything. nothing is lost.
I would suggest heroku is a far more stable host than this site, as often I find it down. Heroku is a professional hosting server that many companies use. Admittedly this is on a hobby dev within the server (which is free hosting up to 10,000 rows in the DB)
You can read about it here (https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier).
Ultimately BrianTRice should have the last say as to what he wants or what is a good idea as its his baby. I will just go with the flow.
A real DB lets you run queries to subset the data so thats the advantage as Shadow pointed out.
Thanks for setting this up! I fully agree that the data should live in the wiki database, but there is no way obvious to me how to do this. I'm of course willing to make measurements on my Zero and do data entry! There just needs to be some good mechanism for the data to be useful after it is entered.
My own ambition, beyond maybe what Brian would like, is that "Zero Manual" not be limited Zero Motorcycles vehicles. ;)
At danger of over-thinking this... more general purpose for the field names would allow us to form a parts database. Mostly I am thinking of fasteners and torque values, where i.e. Bolt Depot's Identifying Fasteners (https://www.boltdepot.com/fastener-information/Identifying-Fasteners.aspx) guide says five fields is enough. All of the world's life in science studies are described by seven categories, and the well known "O.S.I." model has seven layers as well. I think we need at least five to describe fasteners, and seven is pretty close to that so we can assume seven categories.
The basic tables layout having [foreign key] and {unique key}:
MakeYearModels (Make, Year, Model)
Cats ({Name}, A, B, C, D, E, F, G) ; "Fastener"=>Type,Material,Diameter,Length,Thread,NULL,NULL
Items ([CatName], A, B, C, D, E, F, G) ; [Fastener], Shoulder Bolt, Alloy Steel, 10mm, 100mm, M8
and beyond this we can go into applications Apts of those items
Apts ([MakeYearModel], [Item], Name, Minimum, Nominal, Maximum, Unit)
OEMParts ([MakeYearModel], [Item], Partnumber, Description)
Citations ([Application], Description, URL)
This works if you have multiple Items (bolt, with a nut, each is a fastener) for an Apt. That part of the idea needs a little refinement perhaps.
The overall desire I have is for a parts database, with torque/pressure/partnumbers, and perhaps references back into the wiki, that we can query by URL and inset to the wiki.
-
I would suggest heroku is a far more stable host than this site, as often I find it down.
When you say "this site" do you mean electricmotorcycleforum or zeromanual.com?
Heroku is a professional hosting server that many companies use. Admittedly this is on a hobby dev within the server (which is free hosting up to 10,000 rows in the DB)
You can read about it here (https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier).
Ultimately BrianTRice should have the last say as to what he wants or what is a good idea as its his baby. I will just go with the flow.
A real DB lets you run queries to subset the data so thats the advantage as Shadow pointed out.
Zero manual is hosted on Pair Networks.. and does support mySQL databases... if you want me to setup a real database on there in mySQL I can. just the code and everything will need to be on that server, for the same reason.. as long as the site exists, the information is all there. no external info needed. It would be a real development project though.
-
Thanks for setting this up! I fully agree that the data should live in the wiki database, but there is no way obvious to me how to do this. I'm of course willing to make measurements on my Zero and do data entry! There just needs to be some good mechanism for the data to be useful after it is entered.
I am all for making data entry easier and searchable... if theres some tool or program we can add to do this easily I can go forit.. but if its a custom development situation I would have to delegate someone else to do it for me. As much as I love helping I dont have the time to follow through. I recently changed jobs to something with a faster pace, and Im not online throughout the day with downtime anymore.
My own ambition, beyond maybe what Brian would like, is that "Zero Manual" not be limited Zero Motorcycles vehicles. ;)
the Zero Manual site is for zero bikes.. thats a large enough segment to cover. If we end up with a great site/product I dont mind making another site, either specific to something else or generic, but remember... someone has to put the information in. We are lucky to have someone like BrianTRice to input massive amounts of data and format things clearly. Most bikes wont have someone like him that is both dedicated and knowledgeable on the subject.
At danger of over-thinking this... more general purpose for the field names would allow us to form a parts database. Mostly I am thinking of fasteners and torque values, where i.e. Bolt Depot's Identifying Fasteners (https://www.boltdepot.com/fastener-information/Identifying-Fasteners.aspx) guide says five fields is enough. All of the world's life in science studies are described by seven categories, and the well known "O.S.I." model has seven layers as well. I think we need at least five to describe fasteners, and seven is pretty close to that so we can assume seven categories.
The basic tables layout having [foreign key] and {unique key}:
MakeYearModels (Make, Year, Model)
Cats ({Name}, A, B, C, D, E, F, G) ; "Fastener"=>Type,Material,Diameter,Length,Thread,NULL,NULL
Items ([CatName], A, B, C, D, E, F, G) ; [Fastener], Shoulder Bolt, Alloy Steel, 10mm, 100mm, M8
and beyond this we can go into applications Apts of those items
Apts ([MakeYearModel], [Item], Name, Minimum, Nominal, Maximum, Unit)
OEMParts ([MakeYearModel], [Item], Partnumber, Description)
Citations ([Application], Description, URL)
This works if you have multiple Items (bolt, with a nut, each is a fastener) for an Apt. That part of the idea needs a little refinement perhaps.
The overall desire I have is for a parts database, with torque/pressure/partnumbers, and perhaps references back into the wiki, that we can query by URL and inset to the wiki.
theres already a semi-standard way this is done for OEMs, salvage yards, insurance quotes, and parts suppliers. However I dont have access to their software or specs. if someone wants to look into this further, and it can be run on our servers, i might support it. A good plan would need to be constructed, and as I said, im time limited. right now,im litterally typing this in a meeting as that seems to by my only downtime right now. lol
-
Just one mention about this plan..
the idea of the Wiki is to contain the information on in the wiki. NOT to link to external sources. While they can of course be referenced, the information needs to still be in the wiki site itself.
Otherwise you're dependent on another website to be up and useful. The entire point is so that if this board were to crash and go away, or someones random personal page with good info was to disappear, you would still have all the info you need in one place. The wiki itself is professionally hosted, backed up and maintained in a data center with mirrors in 3 physically different parts of the country.. so it should never be "lost". But anything it links to can be.
Im still lost on how some static data belongs in a different database. I dont know if you're aware, but everything in the wiki, is in a database, complete with versioning history and everything. nothing is lost.
I would suggest heroku is a far more stable host than this site, as often I find it down. Heroku is a professional hosting server that many companies use. Admittedly this is on a hobby dev within the server (which is free hosting up to 10,000 rows in the DB)
You can read about it here (https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier).
Ultimately BrianTRice should have the last say as to what he wants or what is a good idea as its his baby. I will just go with the flow.
A real DB lets you run queries to subset the data so thats the advantage as Shadow pointed out.
I don't know that I have a last say. I'm just writing.
I love Postgres and despise Rails, as a former tech consultant asked to save decaying Rails projects and constantly using Postgres to improve customer data facilities. But those don't matter if someone else will always take care of it.
Private hosting is a drag for sure. I can't do much other than use the web interface. I'm not sure I have much time to do more for a while, but the ability to share responsibilities and pitch in means we can collectively do better.
I will say that I tried setting up automated content backup into a git repository, but the perl-based toolchain was too fragile to arrange properly.
-
MrDude_1 forgive my ignorance, but do you have access to the servers the Zero Manuals are on, or the MySQL DB the data lives in?
When you say "our servers" what servers are they?
-
Just one mention about this plan..
the idea of the Wiki is to contain the information on in the wiki. NOT to link to external sources. While they can of course be referenced, the information needs to still be in the wiki site itself.
Otherwise you're dependent on another website to be up and useful. The entire point is so that if this board were to crash and go away, or someones random personal page with good info was to disappear, you would still have all the info you need in one place. The wiki itself is professionally hosted, backed up and maintained in a data center with mirrors in 3 physically different parts of the country.. so it should never be "lost". But anything it links to can be.
Im still lost on how some static data belongs in a different database. I dont know if you're aware, but everything in the wiki, is in a database, complete with versioning history and everything. nothing is lost.
I would suggest heroku is a far more stable host than this site, as often I find it down. Heroku is a professional hosting server that many companies use. Admittedly this is on a hobby dev within the server (which is free hosting up to 10,000 rows in the DB)
You can read about it here (https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier).
Ultimately BrianTRice should have the last say as to what he wants or what is a good idea as its his baby. I will just go with the flow.
A real DB lets you run queries to subset the data so thats the advantage as Shadow pointed out.
I don't know that I have a last say. I'm just writing.
I love Postgres and despise Rails, as a former tech consultant asked to save decaying Rails projects and constantly using Postgres to improve customer data facilities. But those don't matter if someone else will always take care of it.
Private hosting is a drag for sure. I can't do much other than use the web interface. I'm not sure I have much time to do more for a while, but the ability to share responsibilities and pitch in means we can collectively do better.
I will say that I tried setting up automated content backup into a git repository, but the perl-based toolchain was too fragile to arrange properly.
Brian I love Ruby and am trying to change into Ruby Development, but I don't have a lot of experience yet. What version of Ruby and Rails are the decaying projects you speak of? A senior Ruby dev. can deliver a quality site in 5 weeks with Rails that would take 4 months with PHP. I don't know why everyone who is not a Rails dev hates it. But then maybe the Rails was not written well?
You write Ruby code different than in other languages, I have seen ruby code written by a C developer and its been far from good ruby code. There is a lot more to ruby than learning the op codes.
-
Just one mention about this plan..
the idea of the Wiki is to contain the information on in the wiki. NOT to link to external sources. While they can of course be referenced, the information needs to still be in the wiki site itself.
Otherwise you're dependent on another website to be up and useful. The entire point is so that if this board were to crash and go away, or someones random personal page with good info was to disappear, you would still have all the info you need in one place. The wiki itself is professionally hosted, backed up and maintained in a data center with mirrors in 3 physically different parts of the country.. so it should never be "lost". But anything it links to can be.
Im still lost on how some static data belongs in a different database. I dont know if you're aware, but everything in the wiki, is in a database, complete with versioning history and everything. nothing is lost.
I would suggest heroku is a far more stable host than this site, as often I find it down. Heroku is a professional hosting server that many companies use. Admittedly this is on a hobby dev within the server (which is free hosting up to 10,000 rows in the DB)
You can read about it here (https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier).
Ultimately BrianTRice should have the last say as to what he wants or what is a good idea as its his baby. I will just go with the flow.
A real DB lets you run queries to subset the data so thats the advantage as Shadow pointed out.
I don't know that I have a last say. I'm just writing.
I love Postgres and despise Rails, as a former tech consultant asked to save decaying Rails projects and constantly using Postgres to improve customer data facilities. But those don't matter if someone else will always take care of it.
Private hosting is a drag for sure. I can't do much other than use the web interface. I'm not sure I have much time to do more for a while, but the ability to share responsibilities and pitch in means we can collectively do better.
I will say that I tried setting up automated content backup into a git repository, but the perl-based toolchain was too fragile to arrange properly.
Brian I love Ruby and am trying to change into Ruby Development, but I don't have a lot of experience yet. What version of Ruby and Rails are the decaying projects you speak of? A senior Ruby dev. can deliver a quality site in 5 weeks with Rails that would take 4 months with PHP. I don't know why everyone who is not a Rails dev hates it. But then maybe the Rails was not written well?
You write Ruby code different than in other languages, I have seen ruby code written by a C developer and its been far from good ruby code. There is a lot more to ruby than learning the op codes.
My experience with ruby started a decade ago after the first web apps were written in it, and I tried to make some consulting contracts work to revitalize Rails projects. Rails projects do not survive without an active team continually working on them, period. You're not wrong about Ruby or PHP, but the delivery story is not as important as the maintenance and handoff story for a loosely coupled community, which is where rails in particular falls over for relying too much on hard to debug syntactic sugar, deep module dependencies, and heavy runtime overhead.
For what it's worth, I cut my teeth on programming environment implementation and know the implementors of a good number of compilers, languages, and user interface frameworks. I've even implemented a few myself. I'm deeply aware of what underlies my preferences and don't want to overweigh them here.
PS I despise tech industry culture, and electric motorcycle tinkering is one way I try to stay positive, which is why I really don't want to debate this personally. What I don't want is someone else's decision to become my problem after they lose interest.
-
This discussion sounds good to me, I'll get some data layout going offline. Whatever we come up with it can live on the zeromanual site, parallel to the wiki database. That's good enough for me to know it's worth the time to do the data entry.
-
Just one more question Brian, why do you love postgresql? Is that compared to MySQL or more?
-
Have I got my wires crossed? Was the unofficial owners manual started by MrDude_1 and not BrianTRice?
-
Just one more question Brian, why do you love postgresql? Is that compared to MySQL or more?
I work in analytics and have gotten tons of mileage out of Postgres over 15 years. MySQL has been awkward to use successfully. Not exactly bad, but it doesn't perform nice indexing and operations on fancy data types that help beyond the basic CRUD operations.
-
Have I got my wires crossed? Was the unofficial owners manual started by MrDude_1 and not BrianTRice?
MrDude owns the domain and runs the hosting. I just have a mediawiki web account. I'm capable of administering the site in principle but have limited time. I'd likely convert it to a Github wiki or the like if I had to maintain it just to avoid hassles.
But that would change if plenty of people joined in as editors. Which might require mediawiki upgrades to improve the editing UI, and I can't reasonably demand that because PHP can be a pain.
-
I would suggest heroku is a far more stable host than this site, as often I find it down.
When you say "this site" do you mean electricmotorcycleforum or zeromanual.com?
Heroku is a professional hosting server that many companies use. Admittedly this is on a hobby dev within the server (which is free hosting up to 10,000 rows in the DB)
You can read about it here (https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier).
Ultimately BrianTRice should have the last say as to what he wants or what is a good idea as its his baby. I will just go with the flow.
A real DB lets you run queries to subset the data so thats the advantage as Shadow pointed out.
Zero manual is hosted on Pair Networks.. and does support mySQL databases... if you want me to setup a real database on there in mySQL I can. just the code and everything will need to be on that server, for the same reason.. as long as the site exists, the information is all there. no external info needed. It would be a real development project though.
I suggested heroku because it as easy as "git push heroku" to deploy rails there. MySQL is fine with rails because its DB agnostic. I would suspect that setting up the site with ruby and rails would be a major project as well.
-
MrDude_1 forgive my ignorance, but do you have access to the servers the Zero Manuals are on, or the MySQL DB the data lives in?
When you say "our servers" what servers are they?
I have hosting level access to everything. Its professionally hosted by Pair Networks. Its their hardware/datacenter and support.
So while I dont have deep level access to the server, I can do (or have done) anything I need to setup whatever I want... although some things cost more money than others.
Have I got my wires crossed? Was the unofficial owners manual started by MrDude_1 and not BrianTRice?
This whole thing started with a conversation between me and a close friend that owns a Zero. We talked about it, but I thought that was the end of it. Then he bought the domain on my Hover account (close friend, he has access)... and came over to my house to see if I could setup a wiki on it. I setup the wiki software, made a logo, and had it running that evening... but there was no real content... nor was it deeply planned for content sorting.
The next day at work I made a few pages, but didnt have much.
Then someone made a comment about where to put some information, and I said "meh, what the heck, i need to share this anyway" and mentioned it on here.
Then Brian heard about it, and he really stepped up to put the content on there. While I mearly setup the wiki, he went above and beyond to find info, sort everything lay it all out.... While I consider it community owned and others have contributed, I would say Brian started it above all else, because it would probably have fizzed out without him. Hes the reason I can go "what size xxx is that" and go look it up in under a minute. I havent really contributed much to it, other than just paying for the server every year.
What I don't want is someone else's decision to become my problem after they lose interest.
Thats kind of how I feel too. one of the reasons its a mediawiki is that its somewhat stable and hands off to keep going. Theres other software out there, but I dont want to have to mess with the backend on a regular basis. I dont really have the free time, and when I do get free time, I just dont have the interest.
I consider the wiki layout a huge step-up from the old "geocities-style" personal webpages most private vehicle information sites used to be... but its not really a parts catalog... although one could be wedged in there, a few pages with microfiche, chart and a tag could work well enough. IMO.
I suggested heroku because it as easy as "git push heroku" to deploy rails there. MySQL is fine with rails because its DB agnostic. I would suspect that setting up the site with ruby and rails would be a major project as well.
yeah, I personally am not a big ruby fan either... or PHP for that matter... my intrest is more low-level hardware/firmware, even though my day job as a software engineer is for a dotcom... outside of work, I kind of dispise working on anything "web"... mostly because its feels like im just running other peoples code like a script kiddy... too far from the hardware, or even the real code thats doing the work.
Have I got my wires crossed? Was the unofficial owners manual started by MrDude_1 and not BrianTRice?
MrDude owns the domain and runs the hosting. I just have a mediawiki web account. I'm capable of administering the site in principle but have limited time. I'd likely convert it to a Github wiki or the like if I had to maintain it just to avoid hassles.
But that would change if plenty of people joined in as editors. Which might require mediawiki upgrades to improve the editing UI, and I can't reasonably demand that because PHP can be a pain.
I do need to update the UI, I just forgot about updating it. New kid, new job, etc... makes it easy to forget about things like that.
I think I started to look at what my options were, but there was some kind of conflict between what I wanted and the version of something I had.. I'll try to look at it soon.
-
I've added a short section for washing one's bike: http://zeromanual.com/index.php/Usage#Washing (http://zeromanual.com/index.php/Usage#Washing)
I've also added a short section for how to plan when to charge based on one's commute: http://zeromanual.com/index.php/Usage#Charge_Cycle_Plan (http://zeromanual.com/index.php/Usage#Charge_Cycle_Plan)
I lent my 2013DS to a friend for commuting, who had never tried an electric motorcycle before, in order to get the right feedback on how to charge and what it feels like for a newcomer.
-
Added links to self-reference the existing guide i.e. where seat removal is Step Number One in some other process.
Added:
http://zeromanual.com/index.php/Advanced_Modifications#Leave-In_Kettle_Cord (http://zeromanual.com/index.php/Advanced_Modifications#Leave-In_Kettle_Cord)
http://zeromanual.com/index.php/Unofficial_Service_Manual#On-board_Charging_Port (http://zeromanual.com/index.php/Unofficial_Service_Manual#On-board_Charging_Port)
http://zeromanual.com/index.php/Common_Modifications#Helmet_Lock_Removal (http://zeromanual.com/index.php/Common_Modifications#Helmet_Lock_Removal)
http://zeromanual.com/index.php/Common_Modifications#Chargetank_Inlet_Bracket (http://zeromanual.com/index.php/Common_Modifications#Chargetank_Inlet_Bracket)
Split:
http://zeromanual.com/index.php/Zero_Aftermarket#DigiNow_Super_Charger_V1 (http://zeromanual.com/index.php/Zero_Aftermarket#DigiNow_Super_Charger_V1)
http://zeromanual.com/index.php/Zero_Aftermarket#DigiNow_Super_Charger_V2 (http://zeromanual.com/index.php/Zero_Aftermarket#DigiNow_Super_Charger_V2)
Looking for more specific advice on the helmet lock relocation (http://zeromanual.com/index.php/Advanced_Modifications#Helmet_Lock_Relocation) write-up. I want to try this mod but I hesitate to drill holes in the frame until I'm more sure about the placement. Also want to verify if re-using the same bolts etc.
-
I too am not one that likes to bore holes into frames, especially ones made from aluminum. How about gluing a helmet lock to the frame using JB Weld? That stuff ought to hold the lock well enough to support a helmet and prevent anyone from trying to pry off the lock. After all it would be a lot easier to just cut the nylon helmet chin strap or the thin U locking loop of the helmet lock that secures the helmet strap.
-
I would suggest heroku is a far more stable host than this site, as often I find it down.
When you say "this site" do you mean electricmotorcycleforum or zeromanual.com?
Heroku is a professional hosting server that many companies use. Admittedly this is on a hobby dev within the server (which is free hosting up to 10,000 rows in the DB)
You can read about it here (https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier).
Ultimately BrianTRice should have the last say as to what he wants or what is a good idea as its his baby. I will just go with the flow.
A real DB lets you run queries to subset the data so thats the advantage as Shadow pointed out.
Zero manual is hosted on Pair Networks.. and does support mySQL databases... if you want me to setup a real database on there in mySQL I can. just the code and everything will need to be on that server, for the same reason.. as long as the site exists, the information is all there. no external info needed. It would be a real development project though.
I meant the electricmotorcycleforum
-
togo (http://electricmotorcycleforum.com/boards/index.php?action=profile;u=7278) was diligent enough to get a console copy of all the MBB console commands, so I cleaned them up and hyperlinked them to various parts of the wiki that explain concepts:
http://zeromanual.com/index.php/MBB_Console (http://zeromanual.com/index.php/MBB_Console)
-
I am trying to make an offline version of the manual that one can load onto a phone/tablet/laptop/etc. but am having trouble getting everything working in harmony.
I'm having the closest experience to success on this stack (after too many "yak-shaving" experiences) but it really doesn't work without the visualeditor plugin:
https://github.com/openzim/mwoffliner
I do need to update the UI, I just forgot about updating it. New kid, new job, etc... makes it easy to forget about things like that.
I think I started to look at what my options were, but there was some kind of conflict between what I wanted and the version of something I had.. I'll try to look at it soon.
I hope we can clear this hurdle soon, because it seems to unlock a bunch of benefits at once. Honestly, I assume that for some cloud/virtualized hosting services, there's a software image that has this all set up, as long as one is willing to put up with some particular Linux distro.
If that doesn't work, what might?
-
Here's a belated overview of the last month's changes:
I've updated the onboard charger section with some operational guidance:
http://zeromanual.com/index.php/Unofficial_Service_Manual#Charger (http://zeromanual.com/index.php/Unofficial_Service_Manual#Charger)
http://zeromanual.com/index.php/Unofficial_Service_Manual#Charger_Operation (http://zeromanual.com/index.php/Unofficial_Service_Manual#Charger_Operation)
The "lift" section got some Pit Bull stand specifications finally:
http://zeromanual.com/index.php/Unofficial_Service_Manual#Lift (http://zeromanual.com/index.php/Unofficial_Service_Manual#Lift)
The BMS has a photo guide:
http://zeromanual.com/index.php/Unofficial_Service_Manual#Battery_Management_System (http://zeromanual.com/index.php/Unofficial_Service_Manual#Battery_Management_System)
http://zeromanual.com/index.php/Unofficial_Service_Manual#BMS_Parts (http://zeromanual.com/index.php/Unofficial_Service_Manual#BMS_Parts)
http://zeromanual.com/index.php/Unofficial_Service_Manual#BMS_Architecture (http://zeromanual.com/index.php/Unofficial_Service_Manual#BMS_Architecture)
The Battery area is re-organized with sections for the monolith, brick, and long brick:
http://zeromanual.com/index.php/Unofficial_Service_Manual#Cell_Arrangement (http://zeromanual.com/index.php/Unofficial_Service_Manual#Cell_Arrangement)
Relatedly, I assembled a Precharge Theory page based on Doug S's interesting explanations and my observations and study:
http://zeromanual.com/index.php/Precharge_Theory (http://zeromanual.com/index.php/Precharge_Theory)
I took some cropped stock images from Zero's website to help illustrate the frame. I think this is okay, and unfortunately not enough photos exist of the frame for a clear depiction but hopefully we can acquire some to avoid this grey-area usage. At least the images link to the parts of Zero's website where I found them:
http://zeromanual.com/index.php/Unofficial_Service_Manual#Frame (http://zeromanual.com/index.php/Unofficial_Service_Manual#Frame)
The DC-DC converter has a little troubleshooting guide:
http://zeromanual.com/index.php/Unofficial_Service_Manual#DC.2FDC_12V_converter (http://zeromanual.com/index.php/Unofficial_Service_Manual#DC.2FDC_12V_converter)
I found that there's a hint of a chain kit in some 2017 parts catalogs(!). Some interested owner should inquire about this:
http://zeromanual.com/index.php/Zero_Aftermarket#Chain_Kit (http://zeromanual.com/index.php/Zero_Aftermarket#Chain_Kit)
The recalls page now sticks with NHTSA pages:
http://zeromanual.com/index.php/Recalls (http://zeromanual.com/index.php/Recalls)
I clarified the contribution policy after discussing some motivations and copyright issues:
http://zeromanual.com/index.php/Contribution_Policy (http://zeromanual.com/index.php/Contribution_Policy)
Off-bike charging for FX/FXS bikes is now fairly detailed:
http://zeromanual.com/index.php/Advanced_Modifications#Charging_Off_Bike (http://zeromanual.com/index.php/Advanced_Modifications#Charging_Off_Bike)
-
Brian,
I wanted to say Thanks for your unofficial manual.
It's amazing how many have made contributions.
I've scanned over the manual many times and now have a better understanding of the ins and outs of the bike.
I have benefited numerous times.
Just recently, I acquired several items:
[1] Grip Lock - It works well for me.
[2] Pit-Bull Trailer Restraint System - Zero Motorcycles (Axle: 23-04736)
It's just right. It was a quick install. All of my trailering worries have been put to rest.
I decided to give it a go because I recently had my forks repaired as a seal was leaking. I wondered if I had caused the problem by having the straps too tight while the bike was strapped to the trailer.
Without the manual, I would never have known about those two useful items and much more.
Thanks again....
-
I wanted to say Thanks for your unofficial manual.
It's amazing how many have made contributions.
I've scanned over the manual many times and now have a better understanding of the ins and outs of the bike.
I have benefited numerous times.
Just recently, I acquired several items:
[1] Grip Lock - It works well for me.
[2] Pit-Bull Trailer Restraint System - Zero Motorcycles (Axle: 23-04736)
It's just right. It was a quick install. All of my trailering worries have been put to rest.
I decided to give it a go because I recently had my forks repaired as a seal was leaking. I wondered if I had caused the problem by having the straps too tight while the bike was strapped to the trailer.
Without the manual, I would never have known about those two useful items and much more.
Thanks again....
I'm so glad it's helpful!
I spend a lot of time fussing over certain areas trying to strike a balance where it's useful but doesn't get owners into trouble.
I'm not very strong when it comes to motorcycle suspension and would love more words of wisdom from someone experienced with them. More contributors to the manual are welcome; there's plenty to do, and maybe I'll try to better highlight what threads here are still queued for incorporation or what information we've been looking for so the curious know where they could help.
-
This is your regular reminder that this manual is still maintained mainly by my efforts, and that my queue for incorporating others' input is massively deep at this point.
PLEASE, if it ever occurs to you that the manual is wrong or out of date, FIRST make an account on the wiki and add your information in a callout on the page or use a "Talk" page. I can read the changelog and go respond to that much more easily than trying to make new content from scratch by reading forum or Facebook posts.
The manual is basically an unpaid part-time job in the current situation, and I'd rather it be a group effort. Thank you.
-
This is your regular reminder that this manual is still maintained mainly by my efforts, and that my queue for incorporating others' input is massively deep at this point.
PLEASE, if it ever occurs to you that the manual is wrong or out of date, FIRST make an account on the wiki and add your information in a callout on the page or use a "Talk" page. I can read the changelog and go respond to that much more easily than trying to make new content from scratch by reading forum or Facebook posts.
The manual is basically an unpaid part-time job in the current situation, and I'd rather it be a group effort. Thank you.
Amen! Add/edit the manual yourselves. It's fun and easy! I've done it and you can too!
Sent from my Z981 using Tapatalk
-
Yes, it's fun and easy. Why wait for others when you can do it yourself?
-
Hi Brian -
I tried out downloading the manual using HTTrack Website Copier (https://www.httrack.com/). I used the Windows version in GUI mode. There is command line mode and there is Linux/Mac version.
It took over 3 hours to download the 300 MB site. Log summary line below.
HTTrack Website Copier/3.48-21 mirror complete in 3 hours 24 minutes 13 seconds : 2703 links scanned, 2389 files written (296627796 bytes overall), 2389 files updated [303084543 bytes received at 24735 bytes/sec], 4.1 requests per connection
(304 errors, 868 warnings, 0 messages)
While it mentions errors, I didn't notice any issues other than the styling. The results looked just fine to me without the styling. I used all default settings except for Browser ID. With the default Browser ID I was immediately getting a 403. I changed it to "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" and it worked.
This first line from the logs shows the options that were used.
HTTrack3.48-21+htsswf+htsjava launched on Sat, 26 Aug 2017 17:36:31 at http://zeromanual.com/index.php/Main_Page (http://zeromanual.com/index.php/Main_Page) +*.png +*.gif +*.jpg +*.jpeg +*.css +*.js -ad.doubleclick.net/* -mime:application/foobar
(winhttrack -qiC2%Ps2u1%s%uN0%I0p3DaK0H0%kf2A25000%f#f -F " Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36" -%F "<!-- Mirrored from %s%s by HTTrack Website Copier/3.x [XR&CO'2014], %s -->" -%l "en, *" http://zeromanual.com/index.php/Main_Page (http://zeromanual.com/index.php/Main_Page) -O1 "C:\My Web Sites\Zero_Unofficial_Manual" +*.png +*.gif +*.jpg +*.jpeg +*.css +*.js -ad.doubleclick.net/* -mime:application/foobar )
To test the results I disabled my network adapter and opened the following file in Chrome:
file:///C:/My%20Web%20Sites/Zero_Unofficial_Manual/zeromanual.com/index.php/Main_Page.html
Then clicked around at the links and made sure the images all appeared, which they did.
Again, only issue was there was no styling. You could add a post-processing step to fix that but I don't think it is worth the effort as it looked fine without the styling. But it might be worth adding a post-processing step to strip out the link rel="stylesheet" lines as they just timeout in the background.
-Jerome
I am trying to make an offline version of the manual that one can load onto a phone/tablet/laptop/etc. but am having trouble getting everything working in harmony.
I'm having the closest experience to success on this stack (after too many "yak-shaving" experiences) but it really doesn't work without the visualeditor plugin:
https://github.com/openzim/mwoffliner (https://github.com/openzim/mwoffliner)
I do need to update the UI, I just forgot about updating it. New kid, new job, etc... makes it easy to forget about things like that.
I think I started to look at what my options were, but there was some kind of conflict between what I wanted and the version of something I had.. I'll try to look at it soon.
I hope we can clear this hurdle soon, because it seems to unlock a bunch of benefits at once. Honestly, I assume that for some cloud/virtualized hosting services, there's a software image that has this all set up, as long as one is willing to put up with some particular Linux distro.
If that doesn't work, what might?
-
As much as possible, let's try to read it from the website rather than with offline copying tools.
It's good to be referring to sources with the latest changes.
I'd certainly support a mobile-friendly front end, tho. Maybe someone could make a caching-friendly gateway.
-
Offline support is desirable, but someone needs to upgrade the server software to support that properly.
Spidering the content is achievable but the photos are too much of the download content, so you'd have to tweak the spider a lot to get a reasonable result.
I've tried, in a few different ways.
-
Im happy to announce that as of 5 min ago, the zero manual now uses SSL.
You may want to update your links from http to https, however if you dont change anything it will redirect you automatically.
-
Im happy to announce that as of 5 min ago, the zero manual now uses SSL.
You may want to update your links from http to https, however if you dont change anything it will redirect you automatically.
Thank you! I had kept putting off a notice recommending using throwaway passwords.
Chrome still gives a bit of a notice, so I ran a test via Qualys' web service which indicates that it's mostly fine, and probably with a couple of tweaks would be perfect:
https://www.ssllabs.com/ssltest/analyze.html?d=zeromanual.com&latest
-
Thanks, Mr. Dude! That's a great improvement. And I see the SSL Server Test gives your encryption an A!
-
Hey folks, does MrDude_1 still maintain this wiki? Says he hasn't been online here since 2019. Or anyone else here? I found this topic linked from the wiki, not sure who / how else to contact. I went to register on the wiki today, and received this error:
Permission error
You do not have permission to do that, for the following reason:
You are not allowed to execute the action you have requested.
From this link on the main page:
http://zeromanual.com/wiki/Special:UserLogin?type=signup&returnto=Main_Page
-
I have noticed this as well. If you all need help moderating the wiki, please let me know I could probably provide 5-10 hours per month if need be.
-
I am also unable to register on the wiki. I wouldn't be able to contribute much other than removing vandalism or maybe some light grammar edits, but yes there are still people interested.
-
I also wanted to register, but it says Permission error.
Use registration is probably turned off because of spam bot activity. It's a pity, since the manual helped me in many different questions.
-
Yeah, I had to reverse-engineer the pinout for the instrument panel on my 2022 FXE and wanted to contribute it to the wiki, but I was not able to register either.