FDC3260 - Encoder Counts Stopped Working After Firmware Update

I have a FDC3260 controller which was running OK. I've updated the firmware and now the encoder counts have stopped working.

Before flashing I saved the motor controller configuration. Ican see from the XML with a text editor I can see it was running firmware 'Roboteq v1.8d FDC3XXX 1/8/2018'. I flashed with 'FDC3XXX-Firmware-Update-v201-111419'.  Nowthe encoders seem to have stopped working. By not working I mean the count stays at 0 when the motor is turning (in open loop mode). The encoder 1 count seems to flicker between 1 and 0 when the motor runs. The encoder 2 count stays at 0. No wiring or other hardware change has been made other than the firmware update.

I have tried re-sending the configuration to the controller,  power cycling and even resetting the default configuration on the controller. Nothing I change seems to get the encoder counts to work. Is there something I am missing in the configuration which could be causing this? Perhaps the encoder pin allocation changed between v1.8d and v2.01 (very unlikely I imagine). Unfortunately, I do not have a copy of the original firmware to try re-flashing that. Are you able to send a copy of the legacy firmware 'Roboteq v1.8d FDC3XXX 1/8/2018' so I can tryre-flashing with that? I'd appreciate any support quickly if possible as our robot requires closed loop speed control to function so at the moment we are left with a non-functioning robot. I am using Roborun+ Rev 2.0. 7/31/19.

Thank you for any assistance. Please let me know if you need more information to fault find. Many thanks.

I believe I have fixed this. I found a copy of the v1.8d firmware here -
dev-centiva.com/roboteq/index.php?option...oduct_id=328&lang=en
This webpage which is specifically for the FDC3260 only lists v2.0, not v2.01. Where as the generic file download website here lists v2.01 for FDC3XXX:
www.roboteq.com/support/files-download

Is the FDC3260 incompatible with v2.01? I'd like to use 2.0 to use the temperature cutoff limit (OTL)  but I am concerned as the 2.01 change notes include "Fixed script loss". Am I at risk of the script being lost if I use v2.0?

Many thanks.

Hi Athanasios,

Thank you for the reply. Yes, apologies for the mistake in my second message, it should indeed say v2.01. I've corrected it now just to help anyone who might read this thread in the future.

I believe I did try resetting the controller to defaults yesterday and it did not seem to resolve the issue. That may have been after I had already loaded a profile from disk though. I was starting to panic a bit at the time, so can't be 100% confident of this. Should the correct method be: flash v2.01 -> power cycle (is this necessary?) -> reset defaults ->  manually configure config -> send config to controller?

The robot is required for a demonstration soon, so I don't want to take any risks by experimenting further with it right now. Once I have some time and a clear window, I will try flashing v2.01 again and resetting to default and will report back here. It is good to know that the FDC3260 is compatible with that firmware.

Many thanks,

Matt

Hi
My FDC3260 also doesn't work with encoders when i use 2.0 and 2.1 firmware.
Only works properly with firmware version 1.8
regards
Krzysztof