Extended BLDC-TOOL with Watt Control Mode, PPM Cruise Control, individual Throttle-Curve and Android App

Same with me :wink: That’s making things way easier :smiley:

Hi,

as demanded here are some screenshots of the installation process as well as of the failure:

And here the detailed report:

Process: BLDC_Tool [98369] Path: /Applications/BLDC-Tool_2.53.app/Contents/MacOS/BLDC_Tool Identifier: com.yourcompany.BLDC-Tool Version: ??? Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: BLDC_Tool [98369] User ID: 501

Date/Time: 2017-02-07 16:17:00.212 +0100 OS Version: Mac OS X 10.12.3 (16D32) Report Version: 12 Anonymous UUID: DC71223D-BAD1-CB7B-4986-20839E01A453

Sleep/Wake UUID: D17EF8F6-36D4-4518-AC4F-C380674C5030

Time Awake Since Boot: 230000 seconds Time Since Wake: 21000 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: DYLD, [0x1] Library missing

Application Specific Information: dyld: launch, loading dependent libraries

Dyld Error Message: Library not loaded: @rpath/QtPrintSupport.framework/Versions/5/QtPrintSupport Referenced from: /Applications/BLDC-Tool_2.53.app/Contents/MacOS/BLDC_Tool Reason: image not found

Binary Images: 0x108958000 - 0x108ab3ff7 +com.yourcompany.BLDC-Tool (???) /Applications/BLDC-Tool_2.53.app/Contents/MacOS/BLDC_Tool 0x11707e000 - 0x1170bb267 dyld (421.2) <947FC440-80F9-32F7-A773-6FC418FE1AB7> /usr/lib/dyld

Model: MacBookPro12,1, BootROM MBP121.0167.B21, 2 processors, Intel Core i5, 2,7 GHz, 8 GB, SMC 2.28f7 Graphics: Intel Iris Graphics 6100, Intel Iris Graphics 6100, Built-In Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54424C41522D4E5544 Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54424C41522D4E5544 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.21.171.68.1a5) Bluetooth: Version 5.0.3f1, 3 services, 27 devices, 1 incoming serial ports Network Service: USB 10/100/1000 LAN, Ethernet, en5 Serial ATA Device: APPLE SSD SM0256G, 251 GB USB Device: USB 3.0 Bus USB Device: USB 10/100/1000 LAN USB Device: Bluetooth USB Host Controller Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1

I think it could be that the OS isn’t supported yet, because that’s the normal problem I encounter with software even I have no beta OS running on my Mac.

Maybe the Log will help you @The_Dude.

Greetings -Daniel

OK - which OS X is installed on your system?

MacOS Sierra

OK, I’m still with El Capitan (10.11). Don’t now when I will upgrade, but after that I will rebuild the app and send a notification.

I guess the reason is that the librarys like QtPrintSupport are missing. These libraries exist on your machine but not on others. So they need to be added in the pkg. I had to do the same for windows.

Updated my former post. Seems I was right with the OS :smiley:

Hmm … not that trivial for me, the aforementioned path does not exist on my Mac.

I tried with OS X Yosemite (10.10.5), it doesn’t work neither. :confused:

Must be some missing libraries, I will try to elaborate on that - Ackmaniac offered his support. I suppose, you have not installed Qt?

I mentioned that it would be easy to use the Windows Application on a mac with winebottler… I’m sorry but I can’t get my VESC COM Port into the modded BLDC tool, even though I mapped the COM port from the mac into winebottler. Sorry to inform you but it seems much harder than I thought. Since I’m not a developer or programmer that’s where my limits are. Maybe someone around here knows more about this problem?!

@The_Dude I just try to get my hands on qt to just try what happens if it is installed on my mac. Will reply shortly after I tried.

Hi,

I just installed QT and have no clue if I have to do any more things afterwards. :smiley: I tried to start the modded app but still no success.

Hey man! thanks for the tips. I just updated the suggested settings, will test tomorrow morning and I report back.

I increased start up boost from 0.01 to 0.02, it says increase ir carefully, does it add more current from stand still only? or it keeps adding until you reach certain speed?

I used brew to install. What did you use? Which version of Qt? Anyway, I will try to get it working but it seems to me that it’s not trivial. Qt is somehow hardcoding a library path which does not exist on my Mac … we’ll see.

@ackmaniac I have a friend with the same setup as me, 2 VESC, 2 6355 190KV motors, 100mm wheels, 10S4P with Samsung 25R, but instead of 16/36T he has 13T/36T pulley kit.

Whenever the battery charge is between 90-100%, if he applies brakes on high speed, regen sends amps to the battery until it overcharges more than 57V and throws an overvoltage fault code:

Fault : FAULT_CODE_OVER_VOLTAGE Current : -14.2 Current filtered : -14.3 Voltage : 57.35 Duty : 0.27 RPM : 21833.1 Tacho : 453339 Cycles running : 10841 TIM duty : 3498 TIM val samp : 1748 TIM current samp : 8175 TIM top : 12854 Comm step : 5 Temperature : 48.62

Fault : FAULT_CODE_OVER_VOLTAGE Current : -20.3 Current filtered : -15.9 Voltage : 57.41 Duty : 0.20 RPM : 17775.2 Tacho : 464138 Cycles running : 4798 TIM duty : 3221 TIM val samp : 1610 TIM current samp : 9744 TIM top : 16268 Comm step : 2 Temperature : 46.49

Fault : FAULT_CODE_OVER_VOLTAGE Current : -11.4 Current filtered : -11.5 Voltage : 57.45 Duty : 0.23 RPM : 17776.1 Tacho : 486449 Cycles running : 6651 TIM duty : 3358 TIM val samp : 1677 TIM current samp : 8969 TIM top : 14583 Comm step : 3 Temperature : 47.65

Fault : FAULT_CODE_OVER_VOLTAGE Current : -23.3 Current filtered : -16.5 Voltage : 57.63 Duty : 0.14 RPM : 14073.5 Tacho : 505408 Cycles running : 4414 TIM duty : 2848 TIM val samp : 1426 TIM current samp : 11865 TIM top : 20877 Comm step : 2 Temperature : 48.48

Fault : FAULT_CODE_OVER_VOLTAGE Current : -34.5 Current filtered : -22.3 Voltage : 57.68 Duty : 0.10 RPM : 11553.5 Tacho : 522941 Cycles running : 3915 TIM duty : 2513 TIM val samp : 1264 TIM current samp : 13767 TIM top : 25007 Comm step : 1 Temperature : 51.99

and VESC reboots itself, I’m guessing if the battery is fully charged at 42V there’s no place for the regen current to go, so system crashes, he looses all remote control and brakes, really scary to ride this way.

I the battery is below 90% the board rides perfect and braking works flawlessly

We tried:

  1. Reducing the Batt Min (regen) from -8.00 to -5.00A (same problem, overcharge, less braking)
  2. Reducing the batt Min (regen) to -2.00A (no cutting out, but almost no brakes)
  3. Increasing Maximum Input Voltage from 57V to 58V (same problem, overcharge, voltage spike now 58.7V instead of 57.6V)

I’m pretty sure it must have something to do with the pulley kit 13T/36T as it spins the motor a lot more and charges will too much current.

I guess he has another BMS or you have no BMS and he has one. Sounds to me that his BMS shuts down and the VESC doesn’t know where to put that power.

As @Ackmaniac said, probably the BMS is detecting an overcharge of the battery The easy way to figure it out is bypass the charge and use it only for charging

Both boards, mine and his, have the Battery Supports 10S 60A BMS. VESC doesn’t know where to put that regen power

@Pedrodemio if BMS would be detecting a battery overcharge then why would the VESC detect a overcharge and store the fault?, if VESC cutsoff 5 times there would be 5 overcharge stored faults.

Would this have anything to do with the fact I have 100mm wheels, 13T/36T pulley ratio?

Same braking speed, very big wheel diameter, very small motor pulley, a lot of rpms on the motor pulley side during braking, a lot of current being produced by the motor and flowing back to the battery = VESC cutsoff and reboots.

When the BMS detects a overcharge it shuts off. So where should the VESC send the power now? If you would have 12S battery it might can reach the 57V if you have very very bad batterys. But with a 10S you should not face that issue. So i think it’s the BMS. And if the Motor spins faster with the lower motor gear it also produces a higher current. But still it shouldn’t be a issue for a 10S Battery. Just try to bypass the BMS and i think the problem will be solved.