 Re: Fast baud rate setting |
| For what it's worth, I seem to get best results, and no issues, by ensuring the side stand is up, the bike in neutral, and delay start until the instruments have well and truly finished the initiation cycle before pressing the start button.
Yes! That's essential! Often the bike will run like shit if you don't wait for the full initiation cycle. |
| |
| Re: Fast baud rate setting |
| After replacing the log box and you still experiencing the problem, my gut feeling is that this is not the problem and it could be the either the ECU or the harness? The SDS data line could be getting corrupted when you ride/rev the bike which would cause the data to stop logging? The best way to solve these problems is through a process of elimination. I would be surprised if it was the battery and we have replaced the log box so the remaining items to check if possible would be
1) Harness, check for continuity from white molex plug through to ECU plug pins, look for intermittent wire short or break
2) ECU - If you know someone with the same bike you could borrow the ECU and test that side of things? |
| |
| Re: Fast baud rate setting |
| Got the replacement Log Box, thanks.
Unfortunately, the same issues with failed logs. I checked continuity on all plugs and leads as far as I could, but found nothing.
I initially still had the F1 light coming on ocasionaly, sometimes on engine start, or at what seemed to be a certain throttle opening. This almost seems to have resolved itself, after the F1 light began to extinguish at random whilst riding, go figure!
Now the logging is more reliable, only failing 50% of the time, looks to be directly related to the F1 illumination, seems bizarre!
For what it's worth, I seem to get best results, and no issues, by ensuring the side stand is up, the bike in neutral, and delay start until the instruments have well and truly finished the initiation cycle before pressing the start button. It may be a stupid question, but is it possible the battery lacks the grunt and the Log Box drops off line because of a voltage drop? The battery test ok, but is the OEM and getting old. |
| |
| Re: Fast baud rate setting |
| Ok, thanks for the detailed information on the problem, it does seem like there is a problem with the datalogging circuits on the Log Box, i will contact you via email with the details for you to ship the log box back to use for repair/replacement. |
| |
| Re: Fast baud rate setting |
| More fiddling with cofig netted the same results, swapped sd card for a 4gb class 4, re formatted to FAT, and Log box became un recognised by Win 7. seems Log box only works with the old 2gb card (config file present same on both). I do note that there a NO LIGHTS on the LOG BOX any more whilst in logging mode (both cards). Also note that all "successful " logs with old card are less than 200kb in size, regardless of time spent logging, so I'm assuming that it has been failing shortly after start since new....Flash and Data modes both appear to work (when I get the baud rate set to "fast") and test ok. Tested both SD cards under win 7 by copy / read / delete in file manager. Primary failure appears to be somewhere in the SD card reader of Log Box as I have managed to eliminate just about everything else. On the co incidental F1 issue, I did a visual inspection and lubrication (with CRC) of the throttle body assy, and noted a gritty feel when manually exercising the butterfly's, that could induce a locking at partial opening. It appears the servo is in early stage failure, as the F1 light is no longer continuously on, but has become intermittent again, more off than on at the moment though thankfully but think I'll need to source a 2nd hand throttle body assy fairly soon to fix this one. Not exactly the kind of fun I expected to have with Log Box, but keen to get working properly |
| |
| Re: Fast baud rate setting |
| It is a process of elimination with issues like this. It seems like an intermittent problem, so probably not software related, It may be a problem with the micro SD card, would you have a spare micro sd card available to test with?
Another option is to send the Log Box back to us for testing? |
| |
| Re: Fast baud rate setting |
| result of repeat run...exactly the same, 1st leg logged but 2nd and 3rd did not (zero byte files created) |
| |
| Re: Fast baud rate setting |
| yes,tried a couple of different temperature settings, but reverted back to stock setting coz thought that may have been an issue. No discernible change noted. Will re check all connections and try logging again tomorrow if only to see if the problem is repeatable or purely random. |
| |
| Re: Fast baud rate setting |
| Have you changed the configuration for when the log box starts to log? Just trying to work out all of the relevant information. |
| |
| Re: Fast baud rate setting |
| Quick update...
Just returned from a logging ride, with an engine stop for fuel. 1st half of the ride was a successful log, but the second was another 0 byte log.(discovered on return home)
Both parts of the run were for the same time and distance etc, and nothing was changed during the stop, only the ignition was turned off for 20 min.
?????? wtf is going on, beginning to feel I've kicked over a can of worms. |
| |
| Re: Fast baud rate setting |
AU B King K8
I've found that if I load the new stock bin, tick fast baud, and unify maps, exit and save "modified" bin (no other changes to bin), the modified settings are saved in (with) the "new" bin. IE the boxes are ticked already.
I also D/L'd and installed the latest Firmware , with no apparent change (it is a new logbox after all).
The bizarre thing is the issue only cropped up after a big windows and WRT update session...I.ve also re installed com port and other drivers trying to cover all alternatives, after discovering a post referring to com port baud rate setting being an issue (set at 9600)). Engine data and flash both work with all these settings made, as dose the interface test (in eng data mode only) and serial num check (in flash mode only), but experiencing difficulty in getting any loging data in log mode now (was perfect b4 updates!!!!I have made a successful flash of the "modified" stock bin, but experienced a moment of panic when the engine would not start, engine temp guage went max and no starter action, gear position altered to become a dash with no neutral light. I exercised the gear lever, and went back to neutral, switched off, then on again and had normal gauge indications and engine start again. Also had F1 (c28) code since updates, which I have attempted to re set with ECUed without success. yet to do physical inspection and electrical checks per Maint Manual, but have confirmed interface cable connections are secure and correct. Windows did throw a check drive data integrity fault one time pluging in the log box usb cable, but no errors or changes made. I hope you are as confounded by this as I am, cos it's driving me nuts figuring out what I'm doing wrong, or if something is broken      |
| |
| Re: Fast baud rate setting |
| Can you please give me some more details on which particular bin file you are experiencing the issue with? |
| |
| Fast baud rate setting |
| Fast baud rate setting, do not "stick", is there any way to make the selection permanent? I can not find how to save this setting anywhere....
Also, Engine data mode will ONLY run when fast baud setting ticked, is this normal? (both in WRT and ECUed) |
| |
| |
| View Topic on the Woolich Racing Forums |