You need the latest stable version of TSDZ2 firmware, v0.19.x.Aquakitty said:Hey all I'm pretty confused about what version works with what. Should the latest hex for TSDZ2 work with Alpha 0.19.12? I see you all are talking about higher versions, but for the life of me I can't find them. The link in the wiki goes here: https://github.com/OpenSource-EBike-firmware/SW102_LCD_Bluetooth/releases/
But if you click that repo name it says that project is deprecated. The reason I ask is I am getting a "motor not connected?" error on the SW102 (flashing it went fine) but I don't think it's my soldering.
casainho said:You need the latest stable version of TSDZ2 firmware, v0.19.x.Aquakitty said:Hey all I'm pretty confused about what version works with what. Should the latest hex for TSDZ2 work with Alpha 0.19.12? I see you all are talking about higher versions, but for the life of me I can't find them. The link in the wiki goes here: https://github.com/OpenSource-EBike-firmware/SW102_LCD_Bluetooth/releases/
But if you click that repo name it says that project is deprecated. The reason I ask is I am getting a "motor not connected?" error on the SW102 (flashing it went fine) but I don't think it's my soldering.
Would be possible if the developers of the OpenSource firmware for KT, would want to support the SW102 running our OpenSource firmware -- please ask on the KT firmware thread.NoClassic said:I currently have an SW102 display within an existing system and was hoping there was a way to get it functioning with a new KT controller upgrade that I recently purchased. Is this something that is possible given the open firmware available?
Steph said:Hello,
As mentioned in the early posts of this thread, there is a way to backup the original firmware before tinkering with the device.
The method (also described here: https://blog.includesecurity.com/2015/11/NordicSemi-ARM-SoC-Firmware-dumping-technique.html in a way that I found clearer) involves locating a load instruction and looping on it.
To save time for those interested in backing up their unit, there is a such a load instruction at address 0x6B2.
Then, the dump script should be:
base = 0
loop on 256k
- set R3 = base
- set PC = 0x6B3
- step the core
- get value of R3 and save it (this is the word value @ base)
- base += 4
(I'm not using open ODC, so I cannot reproduce the actual commands, just the pseudo-script)
Sorry if this has been covered in a previous post, I somehow missed the updates here. It will take me time to read them through and I only planned for a quick visit today.
I'm also working on this display for my project (I plan to code a controller as well as the display) so I will make sure not to miss updates anymore.
Cheers,
Stephane
Look at git log recent commits, I did enable throttle on 850C, see if the same need to be done on SW102.gatorsean said:Is there currently a problem with the SW102 firmware version 19.17 and using the throttle?
I assumed a problem with the throttle would be in the drive controller firmware, but others have it working it seems.
In the technical menu, I see the ADC values change with the throttle, but the motor does not spin. It does spin with walk assist, so the motor and controller are working. My bike is still on the build rack so I can't quite ride it yet...
Someone else mentioned it could be overvotlage cutoff. I charge to 58.8V, but the display shows 59.6V Is there a way to adjust the cutoff or the adc calibration in the display or should I look to fix it in the code?
Thanks!
casainho said:Look at git log recent commits, I did enable throttle on 850C, see if the same need to be done on SW102.gatorsean said:Is there currently a problem with the SW102 firmware version 19.17 and using the throttle?
I assumed a problem with the throttle would be in the drive controller firmware, but others have it working it seems.
In the technical menu, I see the ADC values change with the throttle, but the motor does not spin. It does spin with walk assist, so the motor and controller are working. My bike is still on the build rack so I can't quite ride it yet...
Someone else mentioned it could be overvotlage cutoff. I charge to 58.8V, but the display shows 59.6V Is there a way to adjust the cutoff or the adc calibration in the display or should I look to fix it in the code?
Thanks!
It would be very strange your motor controller to measure such wrong value of 59.6V when it is 58.8V. I also charge my 3 ebikes with 58.8V and all the 3 motor controllers measure well.
And I don't remember if the motor controller is limiting due to high voltage, if so, we need to make an error code for that situation and show to user on display.
3 options there: temperature, throttle and all disabled. Yes, must be the &3 and not &1 as was previously.gatorsean said:casainho said:Look at git log recent commits, I did enable throttle on 850C, see if the same need to be done on SW102.gatorsean said:Is there currently a problem with the SW102 firmware version 19.17 and using the throttle?
I assumed a problem with the throttle would be in the drive controller firmware, but others have it working it seems.
In the technical menu, I see the ADC values change with the throttle, but the motor does not spin. It does spin with walk assist, so the motor and controller are working. My bike is still on the build rack so I can't quite ride it yet...
Someone else mentioned it could be overvotlage cutoff. I charge to 58.8V, but the display shows 59.6V Is there a way to adjust the cutoff or the adc calibration in the display or should I look to fix it in the code?
Thanks!
It would be very strange your motor controller to measure such wrong value of 59.6V when it is 58.8V. I also charge my 3 ebikes with 58.8V and all the 3 motor controllers measure well.
And I don't remember if the motor controller is limiting due to high voltage, if so, we need to make an error code for that situation and show to user on display.
It looks like this should be the line of code to change to enable throttle? &1 is for temp, &3 is for throttle?
case 8:
// motor temperature limit function or throttle
ui8_g_usart1_tx_buffer[5] =
l2_vars.ui8_temperature_limit_feature_enabled & 3;
Follow the wiki.Nfer said:I bought the SW102 but I am not sure if there is a way to flash with the Bluetooth for the first time without open it. Is it safe? I read some post a while ago
casainho said:Follow the wiki.Nfer said:I bought the SW102 but I am not sure if there is a way to flash with the Bluetooth for the first time without open it. Is it safe? I read some post a while ago
Nfer said:casainho said:Follow the wiki.Nfer said:I bought the SW102 but I am not sure if there is a way to flash with the Bluetooth for the first time without open it. Is it safe? I read some post a while ago
I see. The wiki only describes the open method. I wish I can help you guys to develop and test the bluetooth metod but I have no clue of anything related to this stuff.
https://github.com/OpenSource-EBike-firmware/TSDZ2_wiki/wiki/Flash-the-bootloader-and-firmware-on-SW102-using-SWD
Edit: I found the no-need-to-open discussion. It is still under development
https://github.com/OpenSource-EBike-firmware/SW102_LCD_Bluetooth/issues/35
Nfer said:I tried to open the sw102 cutting the glue at sides of the keypad and I killed the down button contact. It was my fault, instructions are good. Is it possible to use the display without the down button?
geeksville said:This new release ...
windburner said:Nfer said:I tried to open the sw102 cutting the glue at sides of the keypad and I killed the down button contact. It was my fault, instructions are good. Is it possible to use the display without the down button?
The Down button is critical for the configuration process, as well as adjusting the Assist Level, so, I'd say no. Can you solder in a wire or something to bridge the break? (I know it is tight working, as I hope to never have to mess about inside my SW102 again.)