For PWM I hook up to the v+, gnd, and rc-p/fc-p/fc-r on the controller using stock included harnesses
For SPI I hook up to the three SPI ports built into the controller using stock included harnesses
Here is the debug for the PWM connection (skip autodetection checked or unchecked): ---------------------------------- Device s/n: 01239f8b8584d442ee, MCU s/n: 38363020015734591b002000 Firmware ver.: 2.63 b0, board ver.:3.6 error:2 assert_line: 0 assert_file: COM errors: 3 Encoder[ROLL] type: AS5048A,B (PWM) read errors: 7175 Encoder[PITCH] type: AS5048A,B (PWM) read errors: 7178 Encoder[YAW] type: AS5048A,B (PWM) read errors: 7175 DRIVERS STATE: OTW=0, DRV_FAULT=1 TIME SLOTS FREE (us): 1:516, 2:522, 3:206, 4:460, 5:273, 6:266, 7:524, 8:278, 9:525, 10:529, TEMPERATURE (C): MCU=34, IMU=25, F.IMU=33, DRIVERS=0, ROLL_M=0, PITCH_M=0, YAW_M=0, I2C errors: 1; by device: 0x68=1; -----------------------------------
The debug trace for SPI with skip autodetection checked is the same.
The debug trace for SPI with skip autodetection checked does not show read errors or any problems.
On the monitoring tab: In all cases (PWM, SPI, skip autodetection checked or unchecked) the ENC_RAW_R, ENC_RAW_P, and ENC_RAW_Y show value of 0. Various other monitors show reasonable values.
Since at least one other person is seeing this I suspect its not simply a rare defect. I need to get this resolved or Ill have to return the controller and find another solution.
Hello, "For PWM I hook up to the v+, gnd, and rc-p/fc-p/fc-r on the controller using stock included harnesses" - this connection type is suitable only with regular or Tiny boards.
Hello, Ok. I found similar motor from Iflight with built-in encoder, and discovered there AS5048L This is clone of AS5048A chip is compatible with our boards. But sequence of pins in the connector is different from sequence of pins in our controller. This photo with description will help you connect the encoder correctly: http://ybex.com/d/q3uhyb1tzgsda23jecy4hlfk7pbdyb244g6zxthv.html
i had the same connection problem and i solved changeing the pin sequence. But now I have another issue ... with version 2.60 or higher, I can't do the calibration of the encoders, why? It only works with the 2.56 b7 but with this I don't have access to MavLink! Thanks to who will help me!
I've also uploaded a photo of a cable I made. Please note - these pin sequences are not symmetrical - you have to make sure you attach the proper end to each device. In my photo, you'll see that I've marked one connector - it's the connector that must be connected to the Alexmos connector.
Hey jstroup1986 , do you still have photos of this connection? I am having the same issue myself with the AS5048A encoders with the Extended Long Version BGC board. It's hard to see since there are no photos anymore, but is your pinout for the clone AS5048L or the original AS5048A? My particular 5048 module has AS5048A pinted on the component, but it is from a Chinese supplier.