Re: Dec Heavy Duty Tr Error after updating firmware
¿ªÔÆÌåÓýSlight technical correction, the change in the PIC code for 3.1 was the PWM ¡°level¡± that was allowed.? Prior to 3.1 that level was set to 1000 (43%).??? Version 3.1 increased that PWM value to 2000 (86%). The value for 100% PWM is 2300. ? That allowed a much higher value of torque in a potential stall condition and resolved the problem that a certain (very) sarcastic Ozzie reported. ? David ? From: [email protected] <[email protected]> On Behalf Of Brendan via groups.io
Sent: 30 December 2024 22:20 To: [email protected] Subject: Re: [Gemini-II_io] Dec Heavy Duty Tr Error after updating firmware ? Domenic?Lvl6 was released as a package that implicitly stated that the dspic33 servo controllers needed firmware upgrade as part of lvl6.? This is due to lvl 6 integrating upgrade in the servo firmware and using them for operation. ? All that said lvl6.0 ver included lvl3.0 dspic33 firmware all working together to improve Ra/DEC motor stall detection methodology to also assist worm mesh and balancing.?? But there were some "heavy duty Tr" and "Ra Stall" complaints (that motor wasn't generating as much power before "stall" was detected", compared to Lvl5). ? So and that was relaxed with Lvl6 ver 3.1 dspic33? firmware which was released very soon after. ? Basically this allowed greater encoder step count differences before indicating "Ra stall".?? This issue in ver 3.0 dspic33 firmware effected only a few users not all but it is recommended all users update to ver 3.01 dspic33 firmware in both Ra and DEC. ? If you are in Australia.....I can easily update your system to latest Lvl 6, HC and dspic33 firmware to latest level lvl 3.1 (have done many units including my own).? But of course prior to and after need to ensure all Gemini systems functions are operating properly: Ra rate; ST4; Serial; USB; LAN; HC; ASCOM etc?? Its easy for me I have all the test equipment and a number of programmers (I'm in Melbourne). ? cheers ? ? -- Brendan |
David C. Partridge