F.A.S.T. hex File Wanted

[mmais68569]

All right I have been trying to convert the FAST file into a hex file & having ZERO luck. Does anyone have the hex file for the FAST that can send it to me??
If not I guess the 20 FAST that I bought will have to be trashed.

Mike

[gdyrdave]

I couldn't bear to see you trash them. Give them to me if you don't want them. However here is what I have. It is also in the library section under firmware.

Dave

[n8huntsman]

http://www.doityourselfchristmas.com...IC_programming
It's almost mandatory in this hobby to learn to do this. Watch Wayne's videos above. If you have 20 fast tubes you're going to want to tweak some of the parameters or they'll all fall together so the above hex file isn't going to be good to put on all 20 tubes.

[imbluenote]

http://www.doityourselfchristmas.com...IC_programming
It's almost mandatory in this hobby to learn to do this. Watch Wayne's videos above. If you have 20 fast tubes you're going to want to tweak some of the parameters or they'll all fall together so the above hex file isn't going to be good to put on all 20 tubes.

+1...

I had a problem with it initially too. Have you complied other files and have similar problems or is it just the fast that you are having a problem with

[mmais68569]

Just the FAST it says it has written to the PIC & Verify but when I put it in the FAST nothing happens. I know my assemble is good as I tried one of last years PIC in the new build & it works. Last years PIC was programmed in the COOP.

Mike

[budude]

Not sure which method you are using to program the PICs - have you tried (or are you using) the PICKit SW? I personally prefer that myself. What I would suggest is popping in a known good FAST PIC and reading it out to a file - that will give you a 100% known good file. Pop in new PIC and write the PIC with that saved file and see if it works. That will prove you can write good PIC code. It might help to do a screen cap of the SW just before you write to show how it's configured. Just be sure to re-import the file if you perform a PIC erase since the erase writes a blank and then reads in the PIC leaving you with a blank table to write your PIC.

[P. Short]

Not sure which method you are using to program the PICs - have you tried (or are you using) the PICKit SW? I personally prefer that myself. What I would suggest is popping in a known good FAST PIC and reading it out to a file - that will give you a 100% known good file. Pop in new PIC and write the PIC with that saved file and see if it works. That will prove you can write good PIC code. It might help to do a screen cap of the SW just before you write to show how it's configured. Just be sure to re-import the file if you perform a PIC erase since the erase writes a blank and then reads in the PIC leaving you with a blank table to write your PIC.

I'm not sure that I would recommend this right now. There is too great a chance of accidentally erasing the good PIC if there is some sort of cockpit error involving the programmer (or a problem with the programmer itself if it's one of the cheapies from Ebay or the like).

[budude]

I'm not sure that I would recommend this right now. There is too great a chance of accidentally erasing the good PIC if there is some sort of cockpit error involving the programmer (or a problem with the programmer itself if it's one of the cheapies from Ebay or the like).

My assumption is that he has more than one working PIC - perhaps a bad assumption - but if not it should be OK... It's a good method as long as you take your time.

[mmais68569]

Yes I have more then one good PIC. I am using a brand new Pickit3 which I have been able to program a Lynx Express PIC but it was on the control board using an ICSP pin had no problem

Mike