I came up with a issue on my Tunealyser. It would not test a motor. It would run the motor in the non test mode but the kv and rpm numbers were way off. I targeted the sensor cable but two others did the same thing. Changed to other motors, same result. I opened the case hoping for a broken connection, everything looks fine.
Any ideas? I ordered a new one. My current one was a very early one.

The inputs from the sensors are tied to pullups internally, which means you should get a 3.2-3.3V reading on them from the Tunalyzer. Check that you get 3.2-3.3V on each sensor wire from the Tunalyzer, not plugged into a motor. There should be the 3 sensors, a VIN (+5V), gnd, and a temp sensor. You need to check the hall sensor inputs.

LRP had motors that did not have an internal pull up and needed a special cable.

Are you sure about that? I thought the special cable was to make regular motors work with the LRP ESC.

Thanks. I can check that, but if that is the issue, I don't see that it could be repaired easily. It would be from a component failure on one of the two circuit boards. Not something I would be able to do.

You are right, LRP Sensor Conversion Cable 100mm Flow X 500902
So that still means there are motors out there w/o a pull up resistor.

Can't remember seeing a motor with any pullup resistors, but I have seen some (generally much older motors) that had hall effect sensors that only worked with 5V.

Roar specifies 5V input for the sensor board, at least in the rule book. But the sensors on the boards can be either push pull or open collector, so the analyzers use pullups on the GPIO pins just incase they are open collectors on the sensor boards. Ultimately though, this means you should get a high 3.3V from the Tunalyzer on the sensor cables when not connected to a motor.

what happens when you hook up a bad/ cook motor to the tunalyzer?

I never tried it, but I do know it will not run and show and "ERROR" sign if any of the phase leads are touching or shorted to the can.