Beli said:Now I had a look at your resent changes and my question now: what is the idea behind your "torque smoothing"?
The idea is explained here: https://endless-sphere.com/forums/viewtopic.php?f=30&t=115535
Beli said:Now I had a look at your resent changes and my question now: what is the idea behind your "torque smoothing"?
mspider65 said:The idea is explained here: https://endless-sphere.com/forums/viewtopic.php?f=30&t=115535
Beli said:I integrated the latest changes in my version and gave it a trial today (with activated torque smoothing).
I didn't notice significant differences - at least it is running smooth with no problems so far (so as intended).
Deadrabbit said:thanks a lot again for your work. I've ordered five peaces of the board.
Deadrabbit said:Deadrabbit said:thanks a lot again for your work. I've ordered five peaces of the board.
Pcbway send me pictures of the board.
In my point of view, i think there are some headers unsoldered.
Could someone with the knowledge check the pictures?
Thanks!
Yesendlessolli said:Where would I find the "Data Graph View" data shown in the App (after swiping up)?
In the phone app private storage but the data cannot be exported.Where is that stored on the phone / can I export that somehow?
Brownout detector was triggered
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4244
load:0x40078000,len:12740
ho 0 tail 12 room 4
load:0x40080400,len:3744
entry 0x40080620
I (46) cpu_start: Pro cpu up.
I (46) cpu_start: Application information:
I (46) cpu_start: Project name: TSDZ2-ESP32-Main
I (48) cpu_start: App version: 1.2.1
I (53) cpu_start: Compile time: Mar 7 2022 12:30:56
I (59) cpu_start: ELF file SHA256: 231775a46e0091bb...
I (65) cpu_start: ESP-IDF: v4.1-dirty
I (70) cpu_start: Starting app cpu, entry point is 0x400813d8
I (61) cpu_start: App cpu up.
I (81) heap_init: Initializing. RAM available for dynamic allocation:
I (87) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (93) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (99) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (105) heap_init: At 3FFBDB5C len 00000004 (0 KiB): DRAM
I (111) heap_init: At 3FFCE5A0 len 00011A60 (70 KiB): DRAM
I (118) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (124) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (130) heap_init: At 4009CA68 len 00003598 (13 KiB): IRAM
I (136) cpu_start: Pro cpu start user code
I (155) spi_flash: detected chip: gd
I (155) spi_flash: flash io: qio
I (156) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (163) tsdz_main: NVS init ...
I (1343) tsdz_main: Read cfg ...
I (1343) tsdz_nvs: NVS KEY = 7
I (1343) tsdz_main: UART init ...
I (1343) tsdz_main: BT init ...
I (1343) BTDM_INIT: BT controller compile version [219866f]
I (1353) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
W (1363) phy_init: failed to load RF calibration data (0x1102), falling back to full calibration
endlessolli said:I can't believe why there is no further response to @mspider65 update of his firmware & App.
Just to reiterate:
Update is NO Problem!
(It was just stupid me who entered the wrong BT pin when connecting.... Hint: Default is: 123456 - it is even stated during the update process)
Thanks again to @mspider65 for creating this firmware & App and share his continous improvements.
(I like esp. the new App setting structure with the torque sensor having its on sub-menue)
andyb said:I was wondering, if I wish to try a different firmware (eg mbrusa's) at some point in the future, would I have to remove the board.
mspider65 said:andyb said:I was wondering, if I wish to try a different firmware (eg mbrusa's) at some point in the future, would I have to remove the board.
yes, you should remove the board.
To leave it you would need a special firmware that acts as a pass through on the connection between the controller and the display.
Admiralrofl said:Hey everyone, Im really interested in this approach for the tsdz2, especially with a possbility of throttle and temp sensing. I wanted to see if it would be possible to run a no display setup with all of this, But I don't see anyone having tried nor anything in the wiki.
andyb said:It works brilliantly until I change gears and at that point it kind of stops working the connection with the phone drops out as well and then either provides no power or power in fits and starts. I then leave it for a while (a few minutes) and it works again then breaks again (when I change gear).
andyb said:Also does anyone know the wheel sizes I should use, VLCD6, I have used 230 (which should be 29" and so eMtb) but it gives me cadence mode, I will have a play with this and feed back if noone can help.
andyb said:Thanks, would shorting the tx and rx connections appropriately work, I could use a connector on the end of the current one.
mspider65 said:andyb said:It works brilliantly until I change gears and at that point it kind of stops working the connection with the phone drops out as well and then either provides no power or power in fits and starts. I then leave it for a while (a few minutes) and it works again then breaks again (when I change gear).
I don't see how gear shift can affect the ESP32 board operation.
Check the connections and the power supply, there must be some problem there.
I don't either, i can only think that the change in torque is having some effect, it's not the actual gear change as the ESP wouldn't know I have changed gear, I will check it but as it is working then not working i'm unsure what it could be.
andyb said:Also does anyone know the wheel sizes I should use, VLCD6, I have used 230 (which should be 29" and so eMtb) but it gives me cadence mode, I will have a play with this and feed back if noone can help.
The wheel circumference must be configured with the Android app.
The wheel diameter on the display is instead used to set the default assistance mode at start-up.
Read the Wiki.
Yes, but I have been changing the wheel size on the LCD not the App and 230cm 29" doesn't give me eMtb, which is what has confused me.
andyb said:Thanks, would shorting the tx and rx connections appropriately work, I could use a connector on the end of the current one.
If you restore the connection of the TX/RX cables as before installing the board, obviously everything works as before.