FBL2360 Encoder1 connection is not working

Help please!

I purchased FBL2360 directly from Roboteq and going through setup process
Motors: 4 Pole 125 Watts brushless
Encoder: US Digital E4T 300 CPR

Problem 1: Encoder 2 working but Encoder 1 does not (when I swap Encoder works, so it's not defective encoder issue. (A&B Connected to pin 24, 12 and all pulse, analog is disabled)
Problem 2: Sinusoidal with Hall & Encoder mode does not work (motor just vibrate badly and won't turn at all.
Problem 3: Sinusoidal with Hall mode somewhat works but it twitches randomly.

Can someone help me with this please (I'm trying to setup as Sinusoidal with Hall & Encoder mode, so I can have absolute position control

Thank you,

Niko,

Most recent firmware is used 4-2016 version.
Encoder 2 works (Counting) though, even with 300 CPR setting. but encoder 1 is not counting (stays at -1 to 1 despite motor rotate and hall counting).
I'll try with PPR 75 and will post result, would you also look into Sinusoidal with Hall & Encoder problem?

Thank you,

Niko,

I tried PPR 75 and same result (stays at counting -1,1)

niko wrote: All of the above mentioned features do work. Just tested them.

Please send an e-mail to This email address is being protected from spambots. You need JavaScript enabled to view it., in order to arrange a remote session and have a look at your issues.

See my last started topic as I'm having the same problem.

Niko took care of this problem for now and Roboteq may need to investigate further on following issues.

I'm posting this for others who may experience same problem.
My project: Closed Loop Position Relative control setup
Controller: FBL2360
Voltage: 24 Volt (2*12 Volt AGM battery in serial)
Motor: 4 pole brushless motor with hall encoder
Encoder: US Digital E4P 300 CPR (Confusing or contradicting with Roboteq's, US digital indicate this as 1200 PPR vs Roboteq's 75 PPR and need clarification)

My hardware is V2.3
Blake provided me with firmware V17-101316 (Not official firmware yet), and Niko helped me with working setup and I'm grateful for Roboteq's timely support.

Although it's working, but issues are remaining and as follows,
1: On sinusoidal mode, closed loop position relative mode, hall is used for sinusoidal angle sensor & encoder is used for feedback--motor won't spin once in a while (random), turning it by hand will start to spin. (not good for reliable position control, hope they come out with solution soon).
for now, Trapezoidal switching mode might save headache (it works).
2: Manual stated sinusoidal mode with Hall+Encoder will provide absolute positioning, but this mode is not working yet (motor not moving).

I'm happy now for at least I can utilize 2 encoders for closed loop control, though it's not absolute position control (once power down it needed to be set home position manually)

Updated Note: 10/16/16
In Sinusoidal mode: motor jump in low RPM (Sudden shake with vibrate strongly momentarily (I tried with different motors and same result on both channel), so I changed with Trapezoidal mode (smoother result with no jump issues).
Additionally, Velocity setting (Position Turns Min to Max) value is changing by itself upon power cycle. (no matter what value I put into such as 10,20,30, it changes back to 66.66 all the time.---another new problem and I think I noticed this on MDC2360 & SDC2130 brushed controller too, once in a while.

Hope this will provide technical solution from Roboteq & provide help to others to prepare what to expect and work around.

Thank you Roboteq! This gives me another reason for me to continue with Roboteq products.

Hi Martinkim,

@ Problem 2
I am trying to drive a bldc motor with hall and encoder (5000 lines/rev = 20000 cnt/rev) with a MBL 1660 and have the same problem in Sinusoidal mode with Sinusoidal Angle sensor: 'Hall +Encoder'.
I use it in Open loop and I don't want the motor to rotate a bit in both directions to find his rotor position at power up. So Sinusoidal Angle sensor: 'Encoder' is not an option.

Is there anybody who has this working?
Or does this function not working at all due to a bug???

Regards
Wil