Table of contents

• Introduction
• Configuration & programming
• Control command source
• Input specifications
• Supported peripherals
• Peripheral input sources
• Application configuration examples
• Pinout tables

Introduction

Having completed the core function of the controller, basic motor control, we need to now manually control the motor characteristics via various input types and sources.

On this page, we present best practices for connecting and programming your peripheral inputs. Our controller’s analog and digital signal input specifications are from our product sheets. Our currently supported generic peripheral types and our recommended controller input pin. Lastly, several product configuration examples.

Warnings

The following colour blocks may be used to draw your attention to things requiring more attention, caution, a warning, or helpful tips.

ATTENTION – Indicates a step or procedure required before proceeding to the next step or page.

CAUTION – Indicates a potentially hazardous situation which may result in minor injury or product damage.

WARNING – Indicates a Hazardous situation which if not avoided will result in serious injury/death to person(s) or damage to product and/or equipment.

TIP – Indicates a helpful Tip to make things easier and faster.

Configuration & programming

Peripherals can be broken down into control peripheral sources, and auxliary peripheral sources:

Control peripheral sources:

1. Throttle
2. Pedal sensor
3. Torque sensor

Auxiliary peripheral sources:

1. Hall sensors
2. Brake input
3. Display
4. Battery management system
5. Motor temperature sensor
6. Switches
7. Network

When setting up peripherals, the best practice is to pre-plan your wiring and to connect and do basic peripheral configuration in BACDoor™ in the order presented above. Taking care to avoid the need to rewire, see the table in Peripheral input sources below. That is, install one peripheral and set it up before moving to the next peripheral. Starting with the throttle, then moving to pedal sensors, and then torque sensor, etc. as applicable, skipping any peripheral that you are not using.

For example, if you have a bottom bracket pedal/torque sensor, brakes, and a motor with a thermistor, you would connect and program them in this order:

1. Torque sensor
2. Brake input
3. Motor temperature sensor

This is to reduce the possibility of one peripheral that is connected but maybe not yet configured interfering with the setup of another peripheral. For example, if the brakes are connected but not set up, and you are trying to set up your throttle, but it is seemingly not functioning, it may be because the brake signal may have cut out the motor. Thus, the best practice is to connect and program one peripheral at a time, after sketching out the wiring diagram to determine proper input/output pin usage and ensuring no overlap of signals.

Control command source

Selecting Control command source determines which inputs to monitor and how to apply them, and to determine the command setpoint. Control command source configuration options include:

• 0 / Serial stream is used when commanding the controller remotely over a local network, e.g., CAN. See Remote Motor Control for more information.
• 1 / Throttle
• 2 / Pedal sensor
• 3 / BB torque sensor
  • (deprecated, was merged into 2 / Pedal sensor)
• 4 / Throttle OR pedal sensor
• 5 / TMM4 torque sensor

Input specifications

Please see below each controller’s analog and digital signal input voltage specifications. See:

• Table 1 for eMobility controllers (BAC355, BAC555, BAC855).
• Table 2 for High power controllers (BAC2000, BAC4000, BAC8000).
• Table 3 for 2BTube

TIP – Brake 1/Analog input 2 and Brake 2/Analog input 3 are hybrid inputs. They are analog inputs but can be used as digital switches with High/Low trigger thresholds set in software.

WARNING – The communication ports are not surge protected like the other input ports. Voltage above digital Vmax will damage if not wipe out the communication board on the controller. Caution must be taken to prevent accidental short circuits to the communication ports, especially from battery positive.

Table 1 – eMobility controller input specifications

Table 2 – High power controller input specifications

Table 3 – 2BTube controller input specifications

Supported peripheral input types

Here is a list of peripherals, supported peripheral types and the preferred or required controller input pin.

Throttle:

• Hall 0-5V signal
  • Any Analog input. Typically Throttle/Analog input 1 or ABMS/Analog input 4.
• Resistive 0-5V signal
  • Any Analog input. Typically Throttle/Analog input 1 or ABMS/Analog input 4.

Pedal sensor:

• Single Hall, digital pedal cadence
  • PFS/Digital input 2
• Single output dual Hall, digital pedal cadence
  • PFS/Digital input 2
• Single Hall reverse, digital pedal cadence
  • PFS/Digital input 2
• Quadrature speed, digital pedal cadence
  • PFS/Digital input 2 (Sine) & Cruise/Digital input 1 (Cosine)
• Quadrature torque with digital pedal cadence
  • Torque signal to any Analog input (Throttle/Analog input 1 only for v5.xxx), PFS/Digital input 2 (Sine) & Cruise/Digital input 1 (Cosine)
• Single Hall torque sensor
  • Torque signal to any Analog input (only Throttle/Analog input 1 for v5.xxx), cadence to PFS/Digital input 2
• Single Hall reverse torque sensor
  • Torque signal to any Analog input (only Throttle/Analog input 1 for v5.xxx), cadence to PFS/Digital input 2

Axle torque sensor:

• 0-5V Signal
  • Any Analog input

Brake:

• Hall 0-5V signal
  • Brake 1/Analog input 2, Brake 2/Analog input 3, PFS/Digital input 2 or Cruise/Digital input 1
• Resistive 0-5V signal
  • Brake 1/Analog input 2 or Brake 2/Analog input 3

Display:

• Network
  • Port 1 TTL-Rx and TTL-Tx
  • or Port 2 CAN-L/LIN/TTL2-Rx and CAN-H/LIN/TTL2-Tx as applicable (depends on controllers specific communication protocol: CAN-BT, TTL-TTL, etc.)
    • Depends on the controller’s specific communication protocol (CAN-BT, TTL-TTL, etc.), on the firmware version, and display protocol and version.

Battery management system, BMS:

• Analog State of Charge, SOC, (0-10V)
  • Only ABMS/Analog input 4
• Network
  • Port 1: TTL-Rx and TTL-Tx
  • or Port 2: CAN-L/TTL2-Rx and CAN-H/TTL2-Tx as applicable
    • Depends on the controller’s specific communication protocol (CAN-BT, TTL-TTL, etc.)
• Note: Other battery management models available in the software. Example: Voltage model

Motor temperature sensor:

• Thermistor type 0-5V signal
  • Brake 2/Analog input 3 preferred or any analogue input

Wheel speed:

• Digital signal
  • Hall A, to measure either the Hall or back electromotive force (back EMF)
  • Cruise/Digital input 1 or Brake 2/Analog input 3 for external or internal speed sensors

Switches (walk mode, alternate power, alternate speed):

• Digital signal or ON/OFF switch
  • Any Digital input

Peripheral input sources

Application configuration examples

Here are some input configuration examples:

Example 1: Throttle, brakes (single source for motor cutoff and regen) and pedal cadence sensor

• Throttle to Throttle/Analog input 1
• Brakes to Brake 1/Analog input 2
• Pedal cadence to PFS/Digital input 2

Example 2: Throttle, brakes, single Hall torque sensor, motor temperature and external wheel speed sensor

• Throttle to ABMS/Analog input 4
• Brake to Brake 1/Analog input 2
• Single Hall torque sensor cadence to PFS/Digital input 2 and Torque to Throttle/Analog input 1
• Motor temperature to Brake 2/Analog input 3
• Wheel speed to Cruise/Digital input 1

Pinout tables

eMobility controllers

High power controllers

Table 6: High power 6-pin Molex MX150 connector pinout

Table 7: High power 16-pin Molex MX150 connector pinout

2BTube controller (evaluation kit pin-out)

Table 8: 2BTube, Cusmade 0906 (signal-A), 6-pin female sensor signal pinout

Table 9: 2BTube, Cusmade 0905 (signal-A), 5-pin female display signal pinout

Table 10: 2BTube, Cusmade 1206, 6-pin male Battery pinout

Table 11: 2BTube, Cusmade 1009, 9-pin female motor pinout