I have 2 v 1.01 chips all the other chips are dead. Gordo has a v 1.01 chip as well but he is traveling till late fall lol.Lebowski wrote:I see you're now using the proper controller IC ? Since your video shows a blinking LED I'm assuming this
is the drive_1 LED, there's no drive_0 LED ? Can you post all the settings of all the menus ? Are you using v1.00
or v1.01 ?
I ment to post all the menu settings but I forgot and closed termal. I will run the motor and scope the gates and drivers and signals to make sure nothing is funny then I will copy all the menus and past them on here again.
I can do this my self but... In the end most the world is windows based so if we can get your chip to work with windows we are better off.Lebowski wrote:The best sequence for going into program mode is to press and hold reset, press and hold setup, release
reset, release setup. (if you press setup while its in motor mode it will flash all LED's and store the current
sensor calibration data, but only for the v1.01 chips). I'm still wondering whether the problem lies with your
computer (or better said: windows). What we can try here is to use Ubuntu Linux. If you want I can make
a bootable memory stick for you and mail it (will cost a small amount of $ to buy a 4 GB stick, or you can
mail me one). Then you would need to go into the bios of your computer and make it such that it will boot
from USB before booting from harddisk. The computer will then run Ubuntu of the stick without touching
your hard drive. I could then also put the program on which captures the real-time data of the controller
while it is running, to get data like in this post
That it forgets or scrambles all the settings, this should definately not happen. Can you check the 5V power
supply? I've noticed that if it's too low you can get this sort of thing, I use slightly higher than 5 (I use 5.2V).
Also, after you calibrate halls and backemf, and save it to EEPROM, you don't have to calibrate these again.
The chip will remember the settings when you write them to EEPROM. It does not wipe out the settings when
you enter / leave programming mode several times. You can also just change a single setting, the old calibration
data will be remembered. It basically reads the EEPROM on every startup, whether its motor or setup mode.
If you're using v1.01, it's very important you select option k of menu d, and save to EEPROM afterwards. Without
this it's not going to work (but this is mentioned in the manual)
I will test the 5v and scope it. So far it has not been a problem. As for option K in menu D uhm.... I thought it was to reset to defult settings???? I have not clicked on option K yet. I just ready the manual and I was trying to use off set calibration.... I will look at this ASAP.