dang that is a ton of info. nice job.

Am I supposed to read all of that? Jeeze.

Action wrote Why do you keep adding to your post with replies?


Just put it all under the top post lol.


But still good though +rep.

probably from other forums that do that. (They don't know what "edit" means in his country )

I am from the US. Its called chaptering. It gives the post structure. There is too much to read in a single post. Only slobs dump everything in a single pile.

Awesome post, bumping it up so more people can see.

I'm just wondering, I've downloaded the Flex code but is there a way to program it using a hex editor before i put it into a controller so that i don't have to spend all the time programming it from the controller?

I apologize if it is in the post i must have missed it.

I purposely kept the source code from the public to keep people from bastardizing the code. The point of the FLEX is that everything can be changed after the PIC is programmed so it doesnt matter. That was the entire point of FLEX, to adjust everything about the rapidfire so you did not have to have static modes.

Now, if you wanted to have the default values as something else, it is possible to open the hex file in notepad. Then with a little light reading from Microchip-dot-com you can find the area where the values are written to the EEPROM and change those in the hex file. This requires knowing how to read the memory address field, figuring out the values used by the code and what they mean, and also making sure that by changing the values in the hex line, you recalculate the CRC byte and change that also.

Or you could just set the speeds in the controller after its installed like your supposed to.

The biggest reason I wont release the source for this was to make sure that anyone who uses this code would not be able to change it and call it thier own.

That's a lot of info. Nice post!

Okay thank you for clearing that up. I understand that alot of people take the codes and call it their own, but i was going to use this for personal use and i plan to code my own rapid fire chips which would be sold. I'll just program the chip once i have it inside the controller.

I have another question. If i studied the BMU and followed the "opensource assembly code explained" that you posted in another forum. Would i be able to code basic things from scratch or would it require other tutorials or codes

pretty good job :arrow:

TTG-HyPer wrote Okay thank you for clearing that up. I understand that alot of people take the codes and call it their own, but i was going to use this for personal use and i plan to code my own rapid fire chips which would be sold. I'll just program the chip once i have it inside the controller.

I have another question. If i studied the BMU and followed the "opensource assembly code explained" that you posted in another forum. Would i be able to code basic things from scratch or would it require other tutorials or codes

you also need to study the pic12f683 data sheet and need to know about electricity.
and if you followed it all you make would mostly remain the same as bmu.Start At the data sheet i suggest trying to write it out on a note pad as this helped me when i started out. then you have something to go off and submit to acidmods so they can look over it and correct you if you did something wrong