View Single Post
Old 10-08-2015, 11:16 PM   #2157 (permalink)
e*clipse
Permanent Apprentice
 
Join Date: Jul 2010
Location: norcal oosae
Posts: 523
Thanks: 351
Thanked 297 Times in 213 Posts
Ok, file sent.

Ok, now this brings up another issue, kind of an "open source" issue, if you will.
I know this has been dealt with very well by the folks involved with Ubuntu.

How do we do this so Paul can keep blazing ahead with the sensorless and PI parts of the code, without having problems if someone adds a "blinky light" routine?

Should certain parts be "frozen"? Which parts?

Quote:
I very much like your organizational ideas, btw. I need to be able to tear things down and try a bunch of stuff with a working copy though. Although quite a bit of stuff isn't changing, so I think it will be pretty practical for you to work on what you are talking about, and I use a copy based on something that has been reorganized.
For now, I'll look into that interrupt and how a resolver can tie into it. No coding, just learning.

BTW, here are some interesting statistics based on the latest build:
This is for the dsPIC30F4011:
Program memory used: 31431 bytes (64%)
Data Memory used: 1830 bytes (89%)
Maximum dynamic memory: 218 bytes

- E*clipse
  Reply With Quote
The Following 2 Users Say Thank You to e*clipse For This Useful Post:
MPaulHolmes (10-08-2015), thingstodo (10-08-2015)