Compact Field Oriented Controller, ASI + Grin, limited run

cycborg said:
Alan B said:
Are folks using the PhaseRunner successfully with BMC geared hubmotors? A search didn't turn up any hits on that.

Thanks!
Click to expand...
I used it with a MAC for a while before switching to a 9c, so that might be relevant. Search my posts in this thread from maybe the Aug-Sept 2015 time frame. Anything in particular you wanted to know?
Click to expand...

Thanks for the response. I will take a look. Just wondering if it worked ok, haven't seen much discussion regarding the Mac/BMC operation. Some controllers have problems with these motors for some reason. I'm not quite wired up to find out. I may want to use two of these on my AWD setup. Anyone done that? My setup is 9C DD rear and BMC front. I've got a bit of work to do on the front forks before I'll be to that point.
 
MrDude_1 said:
Until you properly setup the controller for the motor, direction doesn't matter.
Click to expand...


I went back to swapping phase wires and the last one produced a nice spin in the right direction. Still can't get through auto tune, same motor not detected message.

Time to go to my local grin dealer/mechanic, I know he just set up a phase runner for a friend last week. Lucky to have a place to take it.
 
The motor tuning uses some of the settings in the sensorless starting section, the pole count and possibly Kv, make sure those values are good, and that there is enough time and current in the sensorless settings to actually move your motor, and enough battery power, etc. It would report no motor if it went through the process of trying to move it and didn't sense any changes, like the current was too low or the time was too short.
 
My Phaserunner changed its beat.

Its blinking in a 6x and 7x rhythum, now. :(

What annoyes me a bit, apart from the constantly blinking Phaserunner, is that Grin Tech didn't provide usefull answers (if any) to my questions here in the thread, or send by email.
Justin never answered to the email I send him two weeks ago.

Whats going on with you guys?

I never experianced this lackluster customer support from Grin Tech befor and frankly, wouldn't have bought the Phaserunner (for all its awesomeness) if I had.
 
After reading your post I checked mine and it's blinking 6"s and 7's too.

I'll be bringing it to my guy locally here on Thursday to get set up, I know it's a great controller as I just rode a buddies bike that got set up last week and it's pretty sweet.

pretty clearly labeled as not for novices, take me down a peg or two,
 
Alan B said:
If you plug (the laptop) in can you get more info about the faults?
Click to expand...

Nope.
I still haven't installed it in a trike and when occasionally running tests with some hub motors, the Phaserunner is connected to PhaseWarmUp on my Mac.
The PhaseWarmUp software doesn't report any persistent faults.

The only 'usefull' answer by email from Grin Tech about the blinking so far was:
'There are some LED patterns that represent "warnings" that can be ignored. The bac500 manual doesn't necessarily apply to the PhaseRunner unfortunately in this circumstance.'

No explanation what error code the blinking might actually represent, no reply to my question how to get rid of it, or an answer to my question (with attached xml setup file) if the temporary bricking of the Phaserunner (when PhaseWarmUp crashed while writing to the Phaserunner) did anything wrong to it.

Apart from being mildly annoyed about the whole thing, I'm actually more worried something serious happend at Grin that demands their full attention.
I rather like to hear they sat stoned on a nice beach and chilled out for a while...
 
got my bike back with controller working and able to test ride now, still some wire shortening to do. throttle is nice and smooth, regen is very strong but no variable yet, and led's are still blinking, I noticed on buddies bike led is blinking too,

I didn't get a great answer as to why autotune didn't work for me on my mac setup but did for him on his pc setup
 
Hello, my phase runner is cutting out when I go over bumps in the road with a fault 9, instantaneous phase over current error.

Any advice on what to try with this one?

I am using an eZee fast winding hub motor, sensorless. CA3 with power control throttle and a power limit around 700W.
 
Same things to check for any other problem that happens on bumps/vibrations:

connectors

contacts

crimps

wires

insulation

Something is loose somewhere, or shorting somewhere.
 
TRRRR said:
Hello, my phase runner is cutting out when I go over bumps in the road with a fault 9, instantaneous phase over current error.

Any advice on what to try with this one?

I am using an eZee fast winding hub motor, sensorless. CA3 with power control throttle and a power limit around 700W.
Click to expand...
This was happening to me when I started using the PR with my MAC (I've since switched to a 9c). My hypothesis is that this and other problems were related to the freewheeling clutch suddenly engaging with a spinning wheel, causing a torque and current spike. I eliminated these problems by using a very small value for Ki. See this post for details.
 
Setting up a PhaseRunner (BAC800) with a BMC V4TT with double phase wires. It is supposed to be well matched Kv wise to a 9C 6x10.

AutoTune moves, generates tones, then throws errors about a phase not connected, I did get it to run partially once and got Rs 67, Ls 175 by swapping motor leads, and it was testing in reverse, so not spinning 26" wheel with thorn proof tube and tire (fairly heavy). Doesn't want to repeat that for some reason. The phase it complains about is not consistent.

Motor runs fine on throttle, unloaded. Spins the correct direction with the phase colors matched. More than a touch of throttle and it accelerates hard to full speed as expected. Perhaps tomorrow I can dig out the tach and get a good Kv.

It also errors out on the hall sensors, black and red wires are correct, a couple of the sensor wires are swapped. So unless BMC uses a different hall sensor color code they should be ok.

Running a 52V pack for testing, trying various scenarios.

Using 80 pole pairs, 6 rpm/volt, around 56 volts of battery.

Which of the parameters affect the auto-tune? Not sure which of the many would be worth varying.

Using the new Ebikes.ca software, only used Bacdoor 1.4 to load the new xml file. This is an early BAC800 from Grin, probably a very early unit. But the calibration of the BattV didn't seem to change.

Do I need to go back and fiddle with the Bacdoor software, or is using the new suite supposed to be sufficient?

Thanks.
 
NUDmFeF-C6Osq1Tg1v0fbfcMYAVWW5TUNqBSeQN9L_dhsjVuR6vIi74pYzdK63Z1vS97j7msWZwKFMYAD3CPdYRVPLSfnlXTKY9QTJOf6yh6PcciSMO9JZj6jHi_xKlQwCMGICgMLkbQ5jSJMsrjPxoCg-pZAq5K6SViCaDTqmNWdM1NIDltpG_NKjyqDDWfwc9Xmo-ztd8czeMmyVHsreyn8F5mC47wqT4j7MU8bR-3hS2iWuq6H8q1V5d04iNq1D8BqCASujjDjyf3PUvW8gTSWnB9VhtNDwWBb_J61baqS38zWIAzUza3fw4GRRAJ1w_tQ9tcbzEWGUWpJlTVzRIs7YvNWkEkYkStPiy68ddZSeG9YE0TUHicaIKwx04oiL7K59j4ELFjzr9uw-RqYiRg0zTDVbwEDXJS0oEqVIjbIDgEfnDCE7simsDhigfKeTKtPXleRaflbPj1o-3hAF9tYxCIfPCFmQpkiTxPr9HZJFltumHu6XQvShE9k4iqTXKgwm8pdyInXkPmA0bgG-gEDQkajGXsMbzZ6uMMxtw31N7TaUIsU62F0q4K8N4vX8_foAxTHGK2A4m8wV1mK8aeB8jth5YM=w888-h500-no


I dug out my tach and measured RPM and voltage and calculated Kv at 4.8, instead of the estimated 6, so I entered that into the PhaseRunner Suite 0.9.4 (the about menu dialog says 0.9.2 but the filename says 0.9.4) software and saved it to the controller. It still errored out on Autotune.

I fired up the Bacdoor 1.4 software again and looked around, didn't see anything that looked wrong or that I was willing to try changing, so I went back to the PhaseRunner Suite and tried Autotune many times. It tripped out in different places each time, complaining of no motor, disconnected phase wires, etc. But occasionally it would go further, and finally it went all the way through. I changed nothing, other than leaving the hall cable plugged in despite it throwing errors.

BMC 4TT motor in 26" wheel
80 pole pairs (16 pp times 5:1 gearing)
Rs 68
Ls 194
Kv 5.53
Halls OK, 16.996 degrees

I let it set everything else back to defaults, which is mostly what I was using anyway. It chose sensored start, sensorless run which is good.

The motor runs smoothly unloaded, aside from a clicking noise that appears to be motor related. This is a new BMC that I bought a couple years ago for this project and never used. It is mounted in a new steel fork which has not yet been mated to the frame.

So the software works very well, aside from tripping out on AutoTune most of the time.
 
Postby TRRRR » Tue Aug 09, 2016 11:05 pm
Hello, my phase runner is cutting out when I go over bumps in the road with a fault 9, instantaneous phase over current error.

Any advice on what to try with this one?

I am using an eZee fast winding hub motor, sensorless. CA3 with power control throttle and a power limit around 700W.
Click to expand...

After advice from grin tech I adjusted the "PLL Bandwidth" parameter in the edit parameters list. Increased it from 0.38 to 0.9 and set current bandwidth to 3000 rads. This seems to solve the problems of shuddering and phase over current faults for me.
 
iser said:
Alan B said:
16 times 5:1 gearing, recommended in Grin's table, pole pairs per wheel rotation.
Click to expand...
Try Pole pairs=16 & Gear rating=5.
Click to expand...
He did; that gives 80 pole pairs. ;)
Alan B said:
80 pole pairs (16 pp times 5:1 gearing)
Click to expand...
 
amberwolf said:
iser said:
Alan B said:
16 times 5:1 gearing, recommended in Grin's table, pole pairs per wheel rotation.
Click to expand...
Try Pole pairs=16 & Gear rating=5.
Click to expand...
He did; that gives 80 pole pairs. ;)
Alan B said:
80 pole pairs (16 pp times 5:1 gearing)
Click to expand...
Click to expand...

I think this is a design-bug in upper computer software of phaserunner;
For controller OS, it does not care about Gear Rating, but the pole pairs is a important parameter;
Wrong pole pairs will leads to inaccurate Hall offset when use MDM tools to identify BLDC parameters.
 
Hi all, was after some help troubleshooting my Phaserunner + CAv3 on a MAC 8t geared hubmotor with a 14s Panasonic GA Sharkpack.

I commuted 30km yesterday with the controller working flawlessly (running from 500w to 1000w to bursts of 2000w). On the way home the controller started to play up; I could only feed it <500w before it would cut out and reset. However after limping home for a bit, it mysteriously came back to full working power at the end of the trip and I could rip up my hill using all 2000w.

Commuting in this morning I got 10kms of perfect behavior before everything died. Any application of throttle resulted in either a CA restart, or a small power surge and then no response (display still stayed powered and showed throttle graph correctly). Plugging throttle into Phaserunner had same behavior (1/4 turn then dead) Battery is brand new, fully charged & was displaying 56v.

I'll recheck my phase/halls tonight. But otherwise I assume I'm looking at a low voltage cutout somewhere? Any tips on where to start diagnosing?

(When this thing was working it was a blast to commute on :D Only having to run one wire to the controller formt he CA is fantastic.)
 
johnxsi said:
Hi all, was after some help troubleshooting my Phaserunner + CAv3 on a MAC 8t geared hubmotor with a 14s Panasonic GA Sharkpack.

I commuted 30km yesterday with the controller working flawlessly (running from 500w to 1000w to bursts of 2000w). On the way home the controller started to play up; I could only feed it <500w before it would cut out and reset. However after limping home for a bit, it mysteriously came back to full working power at the end of the trip and I could rip up my hill using all 2000w.

Commuting in this morning I got 10kms of perfect behavior before everything died. Any application of throttle resulted in either a CA restart, or a small power surge and then no response (display still stayed powered and showed throttle graph correctly). Plugging throttle into Phaserunner had same behavior (1/4 turn then dead) Battery is brand new, fully charged & was displaying 56v.

I'll recheck my phase/halls tonight. But otherwise I assume I'm looking at a low voltage cutout somewhere? Any tips on where to start diagnosing?

(When this thing was working it was a blast to commute on :D Only having to run one wire to the controller formt he CA is fantastic.)
Click to expand...

sounds like you're having low voltage battery issues... I would double check everything is ok with your battery.
 
Battery is good.

Plugged Phaserunner into PC and got "instantaneous phase over current" fault.

EDIT: Solved. Phase wires were rubbing against the cover, eventually shorting, which explains why I had the gradual degradation until dead. (Hopefully an easy fix.) Once I'm back up and running I'll be back to sing praises of the Phaserunner + CAv3 combo :D
 
Thanks for adding to the knowledge-base for this controller. My company just ordered two of these to experiment with, and these shared experiences make a tremendous contribution to making Justin's great products even more useful. In these times of non-existent customer support (present company excluded!), Grin and ES contributors are a brightly shining light in the darkness. We who are about to learn salute you!
 
You must log in or register to reply here.

Similar threads

G
Phaserunner replace PMAC controller?
Replies
0
Views
481
goatman
G
thorlancaster328
Designing the ultimate (400A+) motor controller - what features should it have?
Replies
11
Views
1,824
SammyMc
S
A
50KW controller with field weakening
Replies
10
Views
1,384
Lebowski
Lebowski
owhite
    • Like
  • Locked
building the BESC - 100V, 400A motor controller [NOT RECOMMENDED]
2 3 4 5
Replies
120
Views
20,192
owhite
owhite
markz
Hacking Controller LVC
Replies
5
Views
2,375
jordanjozsef
J
Back
Top