Go to Post A quote from the Southern California Regional Visitors guide: "If you are having problems the FIRST thing to do is ask your neighbor for help" - ChrisH [more]
Home
Go Back   Chief Delphi > Technical > Motors
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #16   Spotlight this post!  
Unread 19-02-2013, 14:11
techhelpbb's Avatar
techhelpbb techhelpbb is offline
Registered User
FRC #0011 (MORT - Team 11)
Team Role: Mentor
 
Join Date: Nov 2010
Rookie Year: 1997
Location: New Jersey
Posts: 1,624
techhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond repute
Re: Motor Drivers

Quote:
Originally Posted by apalrd View Post
The propeller has basically no peripherals. While that gives you a lot of flexibility in code, there are some things that should stay peripherals.

I work professionally with a MPC5600 series processor, which has a lot of peripherals. The eTPU (Time Processing Unit), eMIOS (Modular Input Output System), and DMA (Direct Memory Access) alone on the chip I am currently working with would take around 192 propeller cogs to get something close in functionality, and the TPUs also additional peripherals to synthesize clocks (e.g. angle clock/angle timestamp) and manage timestamps/clocks that would have to be replicated somehow. This dosen't include SPI, QADC or the actual PowerPC itself. While you could likely move some of the algorithms into the cogs that deal with the IO, you would basically need over 200 cogs to get the low and some mid-level software done, and we haven't even touched comm, OS, or high-level application code.

A good C compiler is basically a requirement for an embedded platform these days, especially with autocoding tools which generate C code from models.
I can't speak for the cog count you've assigned to these functions but realistically if you really need purpose built peripherals there are many choices to achieve that result. For example I had no trouble at all gluing a Xilinx CoolRunner CPLD or Spartan 3 to the Propeller and I have a rough prototype using the XCore. More importantly I could change the glue to multiply the number of CPLD/FPGA connected to one or many cogs or Propeller chips. (Interestingly the prototype for the Propeller was made in an FPGA).

Realistically speaking if we can compare the Parallax Propeller 1 to the cRIO which includes the FPGA it's only fair to consider the inclusion of similar hardware.

Also there are OS for the Parallax Propeller.

I can't argue that you should back-hand your way to the sort of integrated functions you enjoy on your microcontroller / microprocessor of choice if you don't have some other reason to do it. Surely if those peripherals are your highest priority you'd be foolish to try to round the square peg to fit that hole. Especially if those peripherals are some kind of proprietary IP.

Still I can drive a FIRST robot on a single Parallax Propeller and it would be sort of like the performance of a bunch of the old IFI control systems.

Last edited by techhelpbb : 19-02-2013 at 14:15.
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 22:31.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi