Thinking of a new gadget...

[GoldOxide_imp]

Possible low risk Feature Request?

* Record highest [engine] temperature detected during ride. Debounce the reading say for about 10 to 30 seconds to ensure it is valid.
* In terms of air ambient temperature, warn rider when approaching freezing point (e.g. increased risk of black ice situations).

 

[Csory_imp]

Black ice warning is no problem. Will add it to the firmware.
Highest oil temp reading is doable, but will have to think about how and where to display. On bikes without coolant temp (CB1100...) the space reserved for coolant temp could be used. Currently there is an "oil too hot" warning already implemented.

 

[GoldOxide_imp]

Black ice warning is no problem. Will add it to the firmware.
Highest oil temp reading is doable, but will have to think about how and where to display. On bikes without coolant temp (CB1100...) the space reserved for coolant temp could be used. Currently there is an "oil too hot" warning already implemented.

Ah, "oil too hot" ... did not know.

Would that temperature value be communicated in a User's Manual?

 

[Csory_imp]

GO: "Oil hot" alarm menans that the top line of the display is replaced with an alternating "OIL!" warning and the actual oil temperature value being displayed. It is now hard-coded to come up at ~128C or ~260F, but working on adding user-adjustable threshold to the menu. Same applies to coolant temperature alert (>110C or 230F), with oil having priority (if both are too hot, oil warning will be displayed).
Please go easy on me with this... Attached the first, very "preliminary" version of the installation/owners manual. I'd like to hear your oppinion regarding the language (is it easy to follow?) and the content. Will keep working on it and add pictures (or replace crappy ones). Let me know if you have any comments/suggestions/recommendations.

BikeGadget.pdf (Size: 934.61 KB / Downloads: 12)

 

[Cormanus]

Fantastic, Csory. :worship:

 

[peterbaron]

Holy cow, now we'll have CB helicopter = nice job

 

[Bazbro_imp]

A really great job, Csory - if only ALL manuals were of this comprehensive quality.

 

[GoldOxide_imp]

GO: "Oil hot" alarm menans that the top line of the display is replaced with an alternating "OIL!" warning and the actual oil temperature value being displayed. It is now hard-coded to come up at ~128C or ~260F, but working on adding user-adjustable threshold to the menu. Same applies to coolant temperature alert (>110C or 230F), with oil having priority (if both are too hot, oil warning will be displayed).
Please go easy on me with this... Attached the first, very "preliminary" version of the installation/owners manual. I'd like to hear your oppinion regarding the language (is it easy to follow?) and the content. Will keep working on it and add pictures (or replace crappy ones). Let me know if you have any comments/suggestions/recommendations.

BikeGadget.pdf (Size: 934.61 KB / Downloads: 12)

I took a brief, but complete look at the document and it is a great start with strong bones. I will take a second and deeper pass. Very good Art!

Question:

Will system configuration parameters be stored in non-volatile memory, or RAM? That is, will the configuration parameters survive a battery disconnect?

 

[GoldOxide_imp]

I think I got the answer to my question from your Owner's Manual draft document.

 

[Cormanus]

Given that it's recommended the module be wired into a circuit linked to the ignition, I'm guessing the configuration will be stored in non-volatile memory.

How did I do?

 

[Csory_imp]

I think I got the answer to my question from your Owner's Manual draft document.

Should've made it more clear in the manual. Will add it now. Configuration data is stored in non-volatile memory (EEPROM) of the brain module, no need to re-enter or re-calibrate unless explicitly specified so with a new firmware version. (As long as the ROM memory map remains the same there is no need to re-configure the device, not even when updating firmware.)

Given that it's recommended the module be wired into a circuit linked to the ignition, I'm guessing the configuration will be stored in non-volatile memory.

How did I do?

You came to the correct conclusion, for the correct reason Configuration data is indeed stored in non-volatile memory, since the unit is not powered unless the ignition is switched on (=one could even cut the wires and it would still maintain configuration data indefinitely).

 

[max]

Very comprehensive indeed, it may be of benefit to some riders to have a very brief explanation of the features and how to access them possibly with a picture or series of small pictures early on in the manual.
more detail can then be had in subsequent pages at length but initially you just want to find the little bit of information you want to update personal very volatile memory.

 

[Csory_imp]

Very comprehensive indeed, it may be of benefit to some riders to have a very brief explanation of the features and how to access them possibly with a picture or series of small pictures early on in the manual.
more detail can then be had in subsequent pages at length but initially you just want to find the little bit of information you want to update personal very volatile memory.

Max, thank you for your comment. I'm already working on a revised edition with summary "flowcharts" at the beginning of "normal operation" and "setting up" sections as a quick overview. Will have it posted once finished.

 

[Csory_imp]

Uploaded a new version of the BikeGadget MkII Installation and User Manual. Please review and let me know if this one is better


Mods: is there a way to remove the old file so that it would not take up space?

 

[Cormanus]

Csory, if you follow the link at the top of the page to your UserCP, there's an option in the left-hand column that says "Manage Attachments". You can delete it from there if you want.

 

[Csory_imp]

Thanks, Cormanus! Just checked that if I replace the file behind this second (two posts above, from OneDrive) link of mine, the link remains alive, while the file gets replaced. This is very convenient. Already made a minor correction to it.

 

[Cormanus]

Phew! I'm pleased I haven't had time to read the revision yet.

 

[Csory_imp]

You're right, my comment was downright confusing. Will not post new versions unless some large-scale change warrants it, and will somehow make the changes easily visible (say, print them in orange). This time it was only the correction of a single misplaced illustration. New version number reflects this (1.01f vs 1.01 where "f" stands for "fixed"). And as always, thank you all very much for your time, patience and comments!

 

[Cormanus]

I didn't find it confusing, Csory. Being able to see where the text has been revised would be helpful if you're looking for feedback on revisions. Are you preparing it in a program that can track changes? I'm sure you could output that to a .pdf showing the revisions.

 

[Csory_imp]

The file is in Apple's "Pages". It can track changes, not sure though if that would appear in PDF (or would be easy to follow). Will check.

Major changes:

- This new version contains an entirely new section at the end ("Installation Example"), to show a sample installation on the '17 CB1100 EX.

- Also added two "flowcharts" as an overview at the beginning of the "Standard operation" and "Adjustments" sections.

- Screenshots are now replaced with drawings - not sure if these look better though.

- The BikeGadget has new adjustments for cold engine / hot oil / hot coolant thresholds, these are explained in the setup section.

- New "Technical data" section added with specifications.

- Lots of minor changes in device functionality and clarifications in the text, based on your previous feedback.

Todo:

- One image is missing in the "What's in the Box" section, with the display and brain module.

- "Updating the firmware" section is only a skeleton now - will have to be vastly expanded.