cavi said:2: trip distance. It would be nice if it did not reset when you turned off the power. As sometimes you have to reboot mid ride....
I second that strongly... Trip Time same...
cavi said:2: trip distance. It would be nice if it did not reset when you turned off the power. As sometimes you have to reboot mid ride....
skestans said:Pedal side is which pedal is down toward the ground when turning the bike on.
Weight with offset is the torque sensor converting its reading to a weight in kg after calibration. It helps to check if you did it right: does the 5kg object register as 5kg on the display after calibration or is it off? Note that it’s not a precision scale so within a kilo or two is still good.
Weight without offset is the same but without using the calibrated values.
cavi said:1: throttle, it seems that the throttle is tied to the assist level, or it feels that way, it does not seem to give me full power. Maybe I have it set wrong?
cavi said:One other software issue that bugs me is that the trip meter resets every time you kill the power. Many times on a ride I will stop and turn off the bike and then when I restart the trip meter has reset....... Could we possibly change this for next firmware, then maybe like the BBSHD press both up and down at once and it would reset?
Looking at the code, I can´t understand why throttle does work as you guys are saying.gatorsean said:I would be happy to try and fix this and do a pull request, but I just ask for a little high level theory of how the throttle works in the code.
casainho, if you read, this, can you take a look at the problem or maybe leave a note here about how the throttle is intended to work in the code?
// throttle
apply_throttle(&ui16_m_adc_target_current, ui8_assist_enable);
The display always show that first screen independent of the TSDZ2 communication. If your display is ok and with corrected flashed firmware, it will show that screen for sure.safeaschuck said:It had previously successfully flashed to 1.0 Beta (splash screen confirmed)
I am waiting for it!! When you do it, I will test and make a new version.Benoit said:As soon as all will be done, I'll made a pull request.
casainho said:I am waiting for it!! When you do it, I will test and make a new version.Benoit said:As soon as all will be done, I'll made a pull request.
casainho said:Maybe a specific page with explanation of the sysptoms, why that happens and the solution. That page could be linked both from configurations battery cut off voltage and FAQ.vshitikov said:We should probably upload this troubleshooting in wiki so it may help other people. And also tell people not to set the battery cutoff voltage to low.
Please prepare the option bytes HEX file and full notes, as you made it with external dependencies: "First find the option bytes from the ECO cycles website" -- is possible that external website change the link or simple disappears and we should try avoid this dependency.vshitikov said:casainho said:Maybe a specific page with explanation of the sysptoms, why that happens and the solution. That page could be linked both from configurations battery cut off voltage and FAQ.vshitikov said:We should probably upload this troubleshooting in wiki so it may help other people. And also tell people not to set the battery cutoff voltage to low.
Hi Casainho,
Just updated Wiki with the troubleshooting information when controller firmware gets corrupted and how to restore it using option bytes. I could not upload pictures right away in the wiki, it requires push access to the directory. But the pictures are not necessary anyways.
cavi said:For the best hill start performance I would setup as the following:
Motor current control = torque
Assist w/o pedal = enable
Startup BOOST = disable
Startup BOOST duration = 5
Startup BOOST fade = 6.5
Motor current ramp = 10a (maximum)
Calibrate your torque sensor then enable calibrations
Motor current max = 20a
So I am not alone, in the preference to control motor current - power mode and using high cadence and low gears. The field weaking is really great for the ones that prefer high cadence!!Nfer said:I prefer to use the control power instead of torque. I am using high cadence and low gears.
Nfer said:cavi said:For the best hill start performance I would setup as the following:
Motor current control = torque
Assist w/o pedal = enable
Startup BOOST = disable
Startup BOOST duration = 5
Startup BOOST fade = 6.5
Motor current ramp = 10a (maximum)
Calibrate your torque sensor then enable calibrations
Motor current max = 20a
I used these settings and it solved the lack of the boost function. The assist w/o pedal rotation enable helps to deliver the power quicker.
I prefer to use the control power instead of torque. I am using high cadence and low gears.
Find it on the configurations wiki page.jeff.page.rides said:Where in the settings with version 1.0.0 do you change motor current control to or from the torque control or power control?
Nfer said:cavi said:For the best hill start performance I would setup as the following:
Motor current control = torque
Assist w/o pedal = enable
Startup BOOST = disable
Startup BOOST duration = 5
Startup BOOST fade = 6.5
Motor current ramp = 10a (maximum)
Calibrate your torque sensor then enable calibrations
Motor current max = 20a
I used these settings and it solved the lack of the boost function. The assist w/o pedal rotation enable helps to deliver the power quicker.
I prefer to use the control power instead of torque. I am using high cadence and low gears.
casainho said:Find it on the configurations wiki page.jeff.page.rides said:Where in the settings with version 1.0.0 do you change motor current control to or from the torque control or power control?
jeff.page.rides said:casainho said:Find it on the configurations wiki page.jeff.page.rides said:Where in the settings with version 1.0.0 do you change motor current control to or from the torque control or power control?
I found it on the wiki page see below, but when I go into the motor configuration screen I don't have the option to choose.
Motor control / Motor ctrl torque If set to "torque", the motor current (torque) will be equal to: measured pedal torque * assist level factor. If set to "power", the motor current will be equal to: measured pedal power * assist level factor (the measured pedal power is equal to: pedal torque * pedal cadence).
mallesepp said:jeff.page.rides said:casainho said:Find it on the configurations wiki page.jeff.page.rides said:Where in the settings with version 1.0.0 do you change motor current control to or from the torque control or power control?
I found it on the wiki page see below, but when I go into the motor configuration screen I don't have the option to choose.
Motor control / Motor ctrl torque If set to "torque", the motor current (torque) will be equal to: measured pedal torque * assist level factor. If set to "power", the motor current will be equal to: measured pedal power * assist level factor (the measured pedal power is equal to: pedal torque * pedal cadence).
Then you have installed 1.0.0 X Alpha. Casainho only implemented torque control from 1.0.0 beta and final.
casainho said:I am waiting for it!! When you do it, I will test and make a new version.Benoit said:As soon as all will be done, I'll made a pull request.
Benoit said:casainho said:I am waiting for it!! When you do it, I will test and make a new version.Benoit said:As soon as all will be done, I'll made a pull request.
Auto reset is now working but, there is a case it won't work because of how time is saved. As it is reset to 0 every day (RTC_IRQHandler function in rtc.c file), in some cases auto reset won't occur.
Example : if last trip update occurs at 14h and auto reset feature is set to 24 hours. The next day it then should be reset at 14h.
But as RTC counter is reset to 0 every time counter exceed 86399 (SECONDS_IN_DAY variable), the day after at 14h, I won't be able to know that actually 1 day has passed and I'll compare 14h to 14h so 0 second and so no reset.
So auto reset above 24h can't work.
Is there any reason RTC counter is reset everyday ? As it is stored in two 16 bits integers, that's 2^32 seconds = more than 136 years.
Managing date would be difficult I think, but we don't need it. We could just store amount of seconds passed since time has been set and let it increment every second.
Since I recall, I used the sample code from ST for RTC. You are free to change if needed.Benoit said:casainho said:I am waiting for it!! When you do it, I will test and make a new version.Benoit said:As soon as all will be done, I'll made a pull request.
Auto reset is now working but, there is a case it won't work because of how time is saved. As it is reset to 0 every day (RTC_IRQHandler function in rtc.c file), in some cases auto reset won't occur.
Example : if last trip update occurs at 14h and auto reset feature is set to 24 hours. The next day it then should be reset at 14h.
But as RTC counter is reset to 0 every time counter exceed 86399 (SECONDS_IN_DAY variable), the day after at 14h, I won't be able to know that actually 1 day has passed and I'll compare 14h to 14h so 0 second and so no reset.
So auto reset above 24h can't work.
Is there any reason RTC counter is reset everyday ? As it is stored in two 16 bits integers, that's 2^32 seconds = more than 136 years.
Managing date would be difficult I think, but we don't need it. We could just store amount of seconds passed since time has been set and let it increment every second.
For now, manual reset is only available in a new menu "Trip memories" in the configuration screen, like all other settings.cavi said:did you add a button to do a manual reset on the screen or do I have to go into the deep settings?