Have to apologize 4 being total newbie in relation to writing 3-phase/bdlc code 4 56F803, and would WelCome if someone kind could give a simple piece of source that would read encoder counts and/or axis rotational angle from HP HEDS5500 encoder hooked to the encoder/quad port of the dsp56f803 ( have checked with scope that the encoder quadrature signal and index pulses come trough fine to the board pins ). Would need sample code to get motivation kick started after too long hiatus from coding. Did not find any suitable encoder reading source code examples from the SDK, such that one could surgery out easily from the SDK bdlc demos. Just a simplest of polling codes would be more than enough, if it is possible to read the counter without ISRs/additional timer routines. Could anyone please help with short demo source of how to do it, and promise will not bug again for some while. No, this is not a school related, just for personal learning to find motivation to study further to one day get a working bdlc-code working with F803 pwming a siliconix level-shifting fet driver/ hall-commutator and reading the encoder from the motor,a simple pwm out, encoder in situation where rest is handled with hw. Thks, Sade M.

Yes, SDK timer driver (Timer Services) uses actual 827 quad timer driver underneath. However, if you use SDK Timer Services, and enable the actual quad timer for usage in your application as well, SDK will perform preprocessor check and will inform you if you have conflicts (If you enable Timer Services, SDK will check to see which quad timers are not used by the user directly, and will use available resources).

Also, you have full source code for the SDK, so you can always step through the code and see what is happening underneath.

Sincerely,

Leonard N. Elevich

Motorola DSPO

-----Original Message-----
From: Nitin Madhukar Yewale [mailto:n...@wipro.com]
Sent: Friday, September 27, 2002 3:22 AM
To: m...@yahoogroups.com
Subject: [motoroladsp] Quad timers and Auxilary timers provided by SDK timer driver

Hi ,

      I am using 56F827 in my project. I have gone through the
documentation of SDK Programmer's Guide and found that SDK provides API
for Timer Services.
[Section 5.1.15]. It says SDK driver can provide 7 auxilary timers and
TOD.

      I am using 3 Quadtimers and I need 3 more timers for my
application.

      827 has 4 Quad timers and 1 TOD. Though timer driver is
providing auxilary timers but internally it might be using actual 827
timer resources.

      I would like to know the SDK timer dirver implementation. Are
they using actual 827 timer resources?

      Is it safe If I use 3 quad timers and 3 auxiliary timers for my
application or they will clash each other?

Thanks and Regards,
Nitin Yewale

_____________________________________
Note: If you do a simple "reply" with your email client, only the author of this message will receive your answer. You need to do a "reply all" if you want your answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join: m...@yahoogroups.com

To Post: m...@yahoogroups.com

To Leave: m...@yahoogroups.com

Archives: http://www.yahoogroups.com/group/motoroladsp

More Groups: http://www.dsprelated.com/groups.php3

">Yahoo! Terms of Service.

Hi , I am using 56F827 in my project. I have gone through the documentation of SDK Programmer's Guide and found that SDK provides API for Timer Services. [Section 5.1.15]. It says SDK driver can provide 7 auxilary timers and TOD. I am using 3 Quadtimers and I need 3 more timers for my application. 827 has 4 Quad timers and 1 TOD. Though timer driver is providing auxilary timers but internally it might be using actual 827 timer resources. I would like to know the SDK timer dirver implementation. Are they using actual 827 timer resources? Is it safe If I use 3 quad timers and 3 auxiliary timers for my application or they will clash each other? Thanks and Regards, Nitin Yewale

**************************Disclaimer********************************************\ ****** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ********************************************************************************\ ********