MDC2250 PWM problems and other issues

Hello, I have a MDC2250 that is not seeing the PIn1 input.
I have a 2 channel Futaba receiver connected and it sees channel 2, but not channel 1. In the pulse in dialog box, see attached, channel two is 1530 which is about centered, but channel 1 is 0. Also, the motor connected will not work on the pwm. Both sliders work fine driving both motors in either direction.
I also get this annoying message every few minutes or so telling me that the controller has been lost.
Help, please!!

Please try the attached firmware that fixes a problem found with some pulse capture conditions.

Pls test carefully as this is unreleased firmware.

Well that took care of the PWM issues and controlling the motors with the radio controller but I still get the message every minute or so saying the controller has been lost. I have to unplug the controller, restart roborun+, before I can do anything else. Ideas???
Thanks for the DFU zip roboteq.

it is unusual that you would have such an unstable usb communication. Try a shorter cable if you have one.

When you loose communication, then you should be able to restore by unplugging the cable from the PC and replugging.

The attached version of the PC utility does a better job at maintaining the comunication. Let us know if you see a difference

It is unusual that you would lose communication so frequently.

Try using a shorter USB cable

If communication is lost, you should be able to recover just by unplugging/wait/replugging the USB cable.

Otherwise, try the version attached.

I tried using the serial interface instead of the usb. The The roborun+ software reports every few seconds it has lost the controller. Once it loses comms, I have to power every thing down and restart just to establish a link again.
I applied the above firmware update and the latest build of roborun+.
I think I may have found a correlation; I have a motor connected with a feedback potentiometer attached. When I select the motor control in the configuration menu to run in feed back mode as opposed to open loop, it seems it\'s then when it loses communication connection.
It seems the roborun software and MDC2250 have some serious issues.
Ideas????

Update:

I look at the computer setting under the device manager. It reported a STM DFU device being reported as having an error. There was a big yellow question mark over the icon in the system list indicating such. I told it to update the driver and the software could not find the driver. I kept wanting to look it up automatically on the internet and since this machine is not connected to the net, that was a bust. I did tell it to look in the windows\\system32\\drivers\\ directory for the proper \"inf\" file. Once it saw it, the usb driver loaded seamlessly.

I had other issues with the closed loop control, but by setting the I and D to 0, they starting behaving as it should.

Thanks thus far.