View Single Post
Old 05-21-2016, 11:52 AM   #2759 (permalink)
MPaulHolmes's Avatar
Join Date: Feb 2008
Location: Maricopa, AZ (sort of. Actually outside of town)
Posts: 3,832

Michael's Electric Beetle - '71 Volkswagen Superbeetle 500000
Thanks: 1,368
Thanked 1,202 Times in 765 Posts
LOL freebeard. Anybody can always do anything they want to with the code. But that's not very helpful for me to say.

Thingstodo, I think it's an excellent idea to get versions going here. Let's set the version you are using right now as the official "VERSION 0.1". I don't even remember what version that is though. I'm HORRIBLE at staying organized. My main problem is being busy. My wife recently ran off the road due to temporarily going blind (M.S. related symptom), so I have to do all the driving now. So, I sort of need help being organized. I don't really understand how github works very well. Let's pick thingstodo's testing files as the official starting point, and then branch from there.

Should we do a single project that's ONLY for induction, and one that's only for permanent magnet? I'm inclined toward that. At first it seemed no big deal to do all of them in a single file, but right now I'm finding that there are significant differences between induction+encoder, permanent magnet+encoder, permanent magnet + resolver type 1, permanent magnet + resolver type 2, permanent magnet + resolverEncoderHybrid (the Yasa motor uses this strange thing), ... I have 5 test motors, and all 5 of them are fundamentally different in their position sensing and/or motor type.

EDIT: I was working on testing that new board, but I think I messed it up with the toaster oven. I have no more of them, so I made a new new board that uses >= 1206 components rather than 0603, and also uses just the surface mount version of the dspic30f4011, which is a lot easier to solder and will have basically the same features as the mostly through-hole board, but the resolver to encoder circuit will be off-board.
kits and boards
  Reply With Quote