• Hello ES! We could use some help to get us past the finish line on building the new knowledgebase for the forum.
    Can you donate? Please see our fundraising page. Thank you!

Votol EM-100 & EM-150 controllers

I have the votol em150 controller. It's the same program for these controllers.

You need to either get cable from qsmotor or build one from a prolific pl2303 serial usb adapter cable and a 4-pin connector.

I can share the software. It is not hard to understand the program so once you have it you'll be able to use it.
I have a votol EM 100 speed controller but all the connectors are cut off and same with the wire harness on the amarda predator motorcycle I have. I have most of the wires figured out but having issues with a few of them. I know the functions of most of the wires from the speed controller but with the bikes harness having different colors connecting to the speed controller, it's a head scratcher sometimes. Would you have any idea where every wire from the controller would connect to what color wire on the bikes harness?
 
Good morning friends in EV Land!

I was chatting with QS and sent them a picture of my Port Settings page.

They mentioned this “Did you change the "PB5" in controller? Because the "high brake" missed.”

I explained that I don’t use High Brake and May have accidentally changed this setting.

I was originally asking about the temp sensor.

He responded with:

You must use High Brake or Low Brake. Because need a signal to input into controller when you are braking.

If no this signal, when you are braking, but controller output, the controller will be burned.

So should I move “PB5” back to high brake?
 

Attachments

  • IMG_1925.jpeg
    IMG_1925.jpeg
    3.2 MB · Views: 13
I'm reading the whole post, a little bit each day; I've read about twenty pages.

In "flux weakening," different colors appear. What do "left" and "right" mean?

Should I enter the same value for both sides?

In "med and hige flux weakening value," are there different values for different speeds?

I have a 1500W motor with a 35h wheel. The maximum is 1500. Should I set the maximum to 1500 for the red, green, and blue colors? For both the right and left sides?

I'm looking at the manual. It's all very confusing.
 

Attachments

  • Captura de pantalla 2026-05-27 234855_b.jpg
    Captura de pantalla 2026-05-27 234855_b.jpg
    219.2 KB · Views: 6
After reading the manual and the post extensively, I've configured these settings. I haven't adjusted the motor, pole position, or half-speed angle settings yet. Are these settings okay to start with?

I'll be using high brake, low brake, cruise control, three speeds, reverse, regenerative braking, and a sport button.

I need to make the wiring for the connection; the connectors don't match the scooter's. I'm going to start wiring the different functions.
 

Attachments

  • Captura de pantalla 2026-05-28 203953.png
    Captura de pantalla 2026-05-28 203953.png
    49.1 KB · Views: 7
  • Captura de pantalla 2026-05-28 204013.png
    Captura de pantalla 2026-05-28 204013.png
    70.7 KB · Views: 6
  • Captura de pantalla 2026-05-28 204025.png
    Captura de pantalla 2026-05-28 204025.png
    45.7 KB · Views: 5
  • Captura de pantalla 2026-05-28 204036.png
    Captura de pantalla 2026-05-28 204036.png
    51 KB · Views: 6
Hey,
I just went down a rabbit hole trying figure out why flux weakening did not kick in and I was limited to 3200rpm on my qs138 70h v3 using votol em150 2. It turns out my "weak flux" value was set way too high.

For Anyone Finding This Later — Votol EM150 + QS138 Phantom RPM Limit Fix
Symptom: Hard RPM cap around 3000–3200 RPM (~30 mph), flux weakening never engages, motor feels like it hits a wall.
Cause: The Weak Flux Cal value on the Calibration Page was set too high (e.g. 255). This is not the same as the Page 2 flux weakening RPM values.
Fix: Check your stock .ini file from SiAECOSYS/manufacturer — the correct value for the QS138 70H V3 + EM150 combo is 15. At 255 the FOC current loop saturates right at base speed and flux weakening cannot engage, creating a phantom hard RPM limit.
How to verify: On the Display/Calibration page, use the Switch Box button to get to Screen 3 (RPM, Qcurrent, Dcurrent). Qcurrent should be around 200 at high RPM. If it's erratic or pegged, the Weak Flux Cal is wrong.

I think the above is correct but any experts please feel free to correct anything. I hope this helps someone as I was stumped for a while and sorting through this thread is difficult with how spread out it is. I have no idea how my weak flux value was changed as I never touched it and I was using the ini file direct from siacosys for the qs138 70h v3. When I reloaded that ini, it had the correct weak flux value and flux weakening worked perfect. I have not done a top speed test but it breezes past 3200rpm under load now.
 
Ey,
Me metí de lleno en un lío tratando de averiguar por qué no se activaba el debilitamiento del flujo y estaba limitado a 3200 rpm en mi qs138 70h v3 usando Votol EM150 2. Resulta que mi valor de "flujo débil" estaba configurado demasiado alto.

Para quienes encuentren esto más tarde: Solución para el límite de RPM fantasma de Votol EM150 + QS138
Síntoma: Límite de RPM fijo alrededor de 3000–3200 RPM (~30 mph), el debilitamiento del flujo nunca se activa, el motor parece chocar contra una pared.
Causa: El valor de Weak Flux Cal en la página de calibración se configuró demasiado alto (por ejemplo, 255). Esto no es lo mismo que los valores de RPM de debilitamiento de flujo de la página 2.
Solución: Compruebe su archivo .ini de fábrica de SiAECOSYS/fabricante; el valor correcto para la combinación QS138 70H V3 + EM150 es 15. A 255, el bucle de corriente FOC se satura justo a la velocidad base y el debilitamiento de flujo no puede activarse, creando un límite de RPM fijo fantasma.
Cómo verificar: En la página de Visualización/Calibración, use el botón de la Caja de interruptores para acceder a la Pantalla 3 (RPM, Qcorriente, Dcorriente). Qcorriente debería ser de aproximadamente 200 a altas RPM. Si es errática o se mantiene fija, la calibración de flujo débil es incorrecta.

Creo que lo anterior es correcto, pero cualquier experto puede corregirme si lo necesita. Espero que esto le sirva a alguien, ya que estuve un tiempo atascado y es difícil encontrar la solución en este hilo por lo disperso que está. No tengo ni idea de cómo se modificó mi valor de flujo débil, ya que nunca lo toqué y estaba usando el archivo ini directamente de siacosys para el qs138 70h v3. Cuando volví a cargar ese archivo ini, tenía el valor de flujo débil correcto y el debilitamiento del flujo funcionó a la perfección. No he hecho una prueba de velocidad máxima, pero ahora supera fácilmente las 3200 rpm bajo carga.
Hi Bro i am looking to understand better about TC1,TC2 and TC3
 
I made the missing cables and installed the controller. I'm testing it.

I can't get the cruise control to work.

On page three, I selected "cruise." In port settings, I set it to "auto cruise." The cruise control didn't work.

Do you know what the problem could be?

I looked in the thread, but I didn't find the solution.
 
สวัสดีทุกคนผมมี VoTOL 150 ขอให้เพียงเล็กน้อยในปี 2021 และเป็นเวลานานก็เก่ามากผมจะอัปเดตอย่างสม่ำเสมอตัวไหนจากไฟล์ใน Mediafire ตามปกติ? ยังมีอีกคนหนึ่งเป็น em-150(CAN_BOOT)_HALL_30 หรืออีกตัวเป็น HALL_94?
ผมใช้คอนโทรลเลอร์ร่วมกับอุปกรณ

คุณช่วยส่งซอฟต์แวร์/เฟิร์มแวร์มาที่อีเมลของฉันirsyadulanam@gmail.com ได้ไหม
ผมขอด้วยได้ไหมครับ aunz.asimo@gmail.com ขอบคุณครับ
 
สวัสดีทุกคน ผมมี VoTOL 150 รุ่นเก่าหน่อย น่าจะปี 2021 และเฟิร์มแวร์ก็เก่ามาก ผมควรจะอัปเดตเฟิร์มแวร์ตัวไหนจากไฟล์ใน Mediafire ดีครับ? มีเฟิร์มแวร์สองตัว ตัวหนึ่งเป็น em-150(CAN_BOOT)_HALL_30 หรืออีกตัวเป็น HALL_94?
ผมใช้คอนโทรลเลอร์ร่วมกับอุปกรณ์ QS138 V3 ครับ
ขอบคุณมาก
ผมขอ file .bin 150รุ่นเก่าของคุณหน่อยได้ไหมครับช่วยส่งให้ทางอีเมลก็ได้ครับ aunz.asimo@gmail.com ขอบคุณครับ
 
I've got something here for riders with mid-engine, chain-driven motorcycles.

“Combinative” is a very interesting and totally overlooked option. Let me put it this way: it tightens the chain before the full power kicks in. A setting of 30 worked very well on my “60 km/h 4 kW moped”; at 40, I noticed a delay during load changes while riding, so now I’m running it at 35. The chain is also much smoother when pulling away from a standstill.

“Combinative” affects the speed at which the chain is tensioned. “Start Torque” is also part of this—it’s the force with which the chain is tensioned. Even a setting of 1 was too much for me from a standstill, so I’ve gone back to 0. I think my chain drive is just too smooth-running; it doesn’t need increased tension. Perhaps a higher tension would be helpful for load changes on heavier vehicles while riding.

These two options are meant to help eliminate the play in the sprockets and chain before full power kicks in. Setting both to 0 is really only appropriate for wheel hub motors, where there’s no play.

Interestingly, even the manufacturer of my conversion kit had overlooked this option and left it set to 0.

There’s also the soft start function, but I find it terrible even at the lowest setting. It creates a strange delay, as if you were pulling a box with a rubber band. Especially with a passenger on an incline on an unpaved road: at first, hardly anything happens, and then the bike suddenly surges forward.

As you can see, I have a high “rate of rise,” and yet there's no hitting of the chain when accelerating at full throttle.

1783434011458.png
 
Back
Top