From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
10-10-2013 04:37 AM
Are you able you program your PIC?
10-10-2013 04:51 AM
Try this one.
Yes i've programed loads of micochip ICs with labview, altho don't have the equipment before me right now so can't test myself. (And all the chips i've programed have had external power).
10-11-2013 02:58 AM
Ya it was fine yesterday but today it says invalid power voltage mysteriously.
Here is the complete string
cmd /c ICD3CMD /P18F26K22 /V5/M /Y /F"D:\pic26k22_tp2000_2003\PIC26K22_TP2000_2003.hex"
10-11-2013 03:29 AM
@Ranjeet_Singh wrote:
Ya it was fine yesterday but today it says invalid power voltage mysteriously.
Here is the complete string
cmd /c ICD3CMD /P18F26K22 /V5/M /Y /F"D:\pic26k22_tp2000_2003\PIC26K22_TP2000_2003.hex"
Guessing you need a space between /V5 and /M. so:
cmd /c ICD3CMD /P18F26K22 /V5 /M /Y /F"D:\pic26k22_tp2000_2003\PIC26K22_TP2000_2003.hex"
10-11-2013 03:44 AM - edited 10-11-2013 03:51 AM
Hi its working but something strange has happened. Attached image file for reference.
But if you see the ICD user interface first it connects and says running self test and all. Then after pressing button it should program and erase. But here what is happening is each time I run the VI it is doing all the things again.
Any solution for that?
10-11-2013 03:58 AM
After programming its not verifying. Here is the string.
cmd /c ICD3CMD /P18F26K22 /V5 /E /M /F"D:\Autocop PROJECTS\MPLAB\pic26k22_tp2000_2003\PIC26K22_TP2000_2003.hex"
Now only other problem persists.
10-11-2013 04:24 AM
@Ranjeet_Singh wrote:
Hi its working but something strange has happened. Attached image file for reference.
But if you see the ICD user interface first it connects and says running self test and all. Then after pressing button it should program and erase. But here what is happening is each time I run the VI it is doing all the things again.
Any solution for that?
The ICD3CMD will connect to the ICD3 each time it's run, that's just the way it's set up. Not much you can do about that, altho the time spent connecting is minimal and shouldn't really matter even if you have to program loads of chips.
as to why the verification failed i can't say.
@Ranjeet_Singh wrote:
After programming its not verifying. Here is the string.
cmd /c ICD3CMD /P18F26K22 /V5 /E /M /F"D:\Autocop PROJECTS\MPLAB\pic26k22_tp2000_2003\PIC26K22_TP2000_2003.hex"
Now only other problem persists.
if you want it to verify after programing you need the /Y argument.
10-11-2013 04:35 AM - edited 10-11-2013 04:35 AM
No Ralok what I mean to say is as soon we start ICD3. it connects. This is I also can do. When user presses the program it will erase then program or directly program but how to pass this arguments later after user presses the button.
Mean suppose user wants to program 10 chips then first time it will all the job but in the next time it should not connect but only argument we need to pass is E,M and F hex file path. Hope you got my point but.
How to pass this argument next time. Here is what I tried
10-11-2013 06:12 AM
Forget my last post. Just tell me how to erase only when user will press button from front panel.
10-11-2013 06:47 AM
erase only would be "cmd /c ICD3CMD /P18F26K22 /V5 /E"