After spending some time away from my workbench thinking about why I was unable to complete Autotune, I couldn't help but think there must still be a wiring error. So, after I checked my physical wiring (which was as I had intended), I cross-checked the wiring diagrams that Justin has provided on this forum, and I noticed another inconsistency.
In the PDF file I attached in my prior message, the 80kOhm pull-up resistor is shown connected to Pin 5 of the large MX150 connector, but in the wiring photo Justin posted earlier in another message (See below.), this pull-up resistor is clearly connected to Pin 4. This mis-wiring may also explain why the throttle voltage signal was low.
The wiring diagram in the PDF file shows the TTL TX and pull-up resistor shifted erroneously one position to the right, to Pins 4-5 instead of 3-4.
I went ahead and moved the pull-up resistor circuit from Pin 5 to Pin 4 and attempted to use the Grin Phase Runner Software again and got stuck being unable to Autotune. I then fired up BACDoor 1.5.4, and again I could not get a response when attempting a static Autotune to get resistance and inductance.
Then, I uninstalled BACDoor 1.5.4 and installed BACDoor 1.5.0 the version linked here:
With BACDoor 1.5.0 I was able to Autotune both static and dynamic parameters (sensored and sensor-less), reading 20mOhm and 28uH for my motor.
Where Robbie writes that I should now be able to spin the motor using an attached throttle, I got no response from the motor.
I then went back to Grin's Phase Runner Software and was able to get through the static Autotune (although the motor made more noise and for a shorter duration than when I did this through BACDoor), but the software disconnected from the controller, complaining of a power loss or USB disconnect, when I attempted the dynamic Autotune, and kicked me out of the Autotune "wizard".
To make sure the controller had the correct values I went back to BACDoor 1.5.0 and checked all the parameters from the beginning per Robbie's list on Page 2 of this thread. When I tried to Autotune again, I at first got no response. But, after disconnecting, connecting, and doing a read/write from the controller, BACDoor let me do a static then dynamic Autotune.
I suspect my inability to get a throttle response may have something to do with how the controller expects to read throttle input. I'm wiring my controller per the photo below, using the eBrake input circuit. Do I need to tell the controller my throttle signal is coming from this circuit and not the normal throttle circuit? I could find no way to specify this in BACDoor 1.5.0. Robbie's BACDoor tutorial was written before Justin posted his wiring diagram for the BAC2000. Are there are other parameters in later versions of BACDoor to recognize this wiring?
A minor nuisance is that the software (both BACDoor and Grin's Phase Runner Software) is glitch-y and at various times cannot communicate with the controller during Autotune. But, performing a dummy write or restarting the program clears the glitch.
Lastly, I now have tried four different application versions to program my controller:
Grin Phase Runner Software
I was able to get furthest in the setup process with BACDoor 1.5.0, perhaps because it was the version Robbie used when writing his tutorial.
At this point I've gone through Peripheral Selection tabs and Peripheral Configuration for Throttle, Brake, and Basic Motor (sensored), but I cannot get a throttle signal to spin the motor. My wiring is the same as Justin's in the photo below but with the addition of Hall sensor leads.
Have I missed something, and what version of BACDoor should I be using?