fiduciary

Author Topic: CFX no swings, no LED (Solved)  (Read 751 times)

0 Members and 1 Guest are viewing this topic.

Offline scott

  • Force User
  • ***
  • Posts: 126
  • Oh, I donít think so.
Re: CFX no swings, no LED (Solved)
« Reply #30 on: February 08, 2020, 12:14:23 PM »
I just removed the cap and the same behavior persists. Clash is good, no swing sounds.

Offline scott

  • Force User
  • ***
  • Posts: 126
  • Oh, I donít think so.
Re: CFX no swings, no LED (Solved)
« Reply #31 on: February 08, 2020, 03:33:29 PM »
Finally gave up...swapped the board out of my build with the same wiring and same config (albeit, I left the FW alone given the posts about USB port ESD) and all is perfect.

Now just need to get this wonky board fixed.

Offline Space_Tardigrade

  • No Force
  • *
  • Posts: 7
  • Um...Hello?
Re: CFX no swings, no LED (Solved)
« Reply #32 on: February 08, 2020, 04:49:14 PM »
I just attempted removing the capacitor as well, and no luck. Still no swings. I havenít been able to check the gyro log as I donít think that version of the RICE editor is available for Mac yet.

Havenít heard back from Chewbacca yet on the forum, so Iíll probably drop him an email to inquire about repairs.

Offline AngelOmega

  • No Force
  • *
  • Posts: 9
  • Um...Hello?
Re: CFX no swings, no LED (Solved)
« Reply #33 on: February 08, 2020, 06:34:02 PM »
Yes I had to contact Chewbacca directly through email. He responded very quickly once I did.

Offline sacubitril

  • No Force
  • *
  • Posts: 2
  • Um...Hello?
Re: CFX no swings, no LED (Solved)
« Reply #34 on: February 10, 2020, 06:25:36 PM »
I have a new CFX neopixel install that also has the same behavior as described by others. No swing sounds or smoothswing but normal hum and clash.  I upgraded the FW to 10.004E with default fonts and config files for 10.004D hoping it was software related.  The truncated boot log from RICE shows:

SPECS:Sectors 15523840 (7680MB)
 SD Clock (CSD) 25000000 Hz
 SD Clock 50000000 Hz
 Type SD
 SD Version 3.
 High Speed
 Card Installed
 Initialized
 Plecter Labs Crystal Focus
 v10.004E-05/02/2020
 Init Motion Sensor
 Reset Motion Sensor
 XG boot ended: OK (waited 1ms)
 M boot ended: OK (waited 1ms)
 WHO_AM_I_M = 3D - WHO_AM_I_XG = 68
 Success
 Motion sensor Debug:
 CTRL_REG1_G = 10111000
 CTRL_REG2_G = 0
 CTRL_REG2_G (second time) = 0
 CTRL_REG3_G = 0
 CTRL_REG4 = 111000


I also measure 8.71V at the capacitor with my DMM which looks to be in the expected range.

Reading other posts, people have:

1.Looked at gyro info with custom FW from erv to see if gyro displays appropriate motion.
2.Replaced the 25V 1uF 0603 capacitor with SMB footprint or remove it entirely.
3.Sent it in for gyro replacement.

Would it be helpful to replicate what others have done in the interest of shared knowledge? I want to buy another sound modules for an install but don't want to have the same issues if there is something I can do to prevent it like extra ESD equipment I should purchase.

 

Online erv

  • Plecter Labs Inc. "Keeper of the Buttered Toast"
  • Manufacturer
  • Master Force User
  • *
  • Posts: 4606
  • Formerly known as Irvin PLECTER
    • Plecter Labs - Props Electronics
Re: CFX no swings, no LED (Solved)
« Reply #35 on: February 11, 2020, 12:42:48 AM »
after digging several situation and testimonials from customer, it's probably ESD that damages the gyro charge pump leading to either silent or crazy gyro. You can try to remove the gyro cap (pointed where it's currently written 14V, where 8-10v should rather be seen).
My conclusion is that people discharge ESD in the capacitor or in the switches when manipulating (killing the act or aux pad internal pullup resistor).
The fw has been ruled out as it writes properly in the sensor registers and init goes perfect, even reading back from the sensor work, just the internal MEMS is damaged.

Offline AngelOmega

  • No Force
  • *
  • Posts: 9
  • Um...Hello?
Re: CFX no swings, no LED (Solved)
« Reply #36 on: February 13, 2020, 10:38:11 AM »
So Iíve heard back from Chewbacca, and the issue was in fact caused by a damaged motion sensor. I think it is safe to call this issue solved now, as it seems we have all reached the same conclusion that the motion sensor was damaged by ESD.