Took me a while to get my two PICkit 3s working. I documented my experience here - a "boiled-down" list of everything I found of value on this page.
http://woodworkerb.com/pickit-3-and-flowcode-6/
Search found 14 matches
- Sun Dec 13, 2015 11:48 pm
- Forum: Flowcode V6
- Topic: Flowcode 6 Pickit3
- Replies: 18
- Views: 27535
- Mon Dec 07, 2015 11:17 pm
- Forum: Flowcode V6
- Topic: String Handling Questions
- Replies: 10
- Views: 7118
Re: String Handling Questions
The documentation is not incorrect but allows different interpretations. Gotta be honest, not sure how to even process that bit of information. So, it is null terminated unless it's not. (for clarity of anyone reading this, by "zero" you mean "null" (0x00) since 'zero' can be confused with an ASCII...
- Mon Dec 07, 2015 5:18 pm
- Forum: Flowcode V6
- Topic: String Handling Questions
- Replies: 10
- Views: 7118
Re: String Handling Questions
Thank you also! I started confused about one thing, now I'm confused about two things. 1) OP was on "Why am I getting three different outputs from string concatenation"? For which I'm still confused, but it is no longer relevant. 2) is a STRING null terminated (and the documentation is correct) or i...
- Mon Dec 07, 2015 5:20 am
- Forum: Flowcode V6
- Topic: String Handling Questions
- Replies: 10
- Views: 7118
Re: String Handling Questions
I am not a fan of the flowcode documentation, but I did read this: One important difference is in Flowcode strings are null-terminated. This means the first zero-value byte that is encountered in the string marks the end of the string. http://www.matrixtsl.com/wiki/index.php?title=Variable_Types Now...
- Sun Dec 06, 2015 6:41 pm
- Forum: Flowcode V6
- Topic: String Handling Questions
- Replies: 10
- Views: 7118
Re: String Handling Questions
Hello medelec35, Thanks for the feedback! An update: I do realize what I posted only worked with a 6 character string, I was just baffled by the results of string concatenation. I went with an even simpler solution: a) Loop 1 - figure where first comma goes: Loop thru the string until you find EOS (...
- Sun Dec 06, 2015 7:59 am
- Forum: Flowcode V6
- Topic: String Handling Questions
- Replies: 10
- Views: 7118
String Handling Questions
Variable StringHolder = " 123456 " (it's a real string, not a number). I check if the string is Length$ greater than 3, then I want to add a comma, so "123456" should become "123,456". Simple. NotSoMuch I get three different results from three variations of the identical formula: Prints1.jpg Prints2...
- Fri Dec 04, 2015 7:26 pm
- Forum: Flowcode V6
- Topic: SOLVED: Problem sending character to LCD via UART/Serial
- Replies: 8
- Views: 5148
Re: SOLVED: Problem sending character to LCD via UART/Serial
Okay, turns out the problem was indeed the "Extended CPU Enable"
After switching to "disabled", the code worked as expected.
THANKS FOR THE SUGGESTION!
- Wed Dec 02, 2015 10:56 pm
- Forum: Flowcode V6
- Topic: SOLVED: Problem sending character to LCD via UART/Serial
- Replies: 8
- Views: 5148
Re: Problem sending character to LCD via UART/Serial
Here you go. I can't help but feel it's got something to do with variable typecasting, but since it's only my 3rd day with Flowcode . . . who knows!?!
Should I download and apply "Flowcode 6 - latest components, bug fixes and improvements"?
Should I download and apply "Flowcode 6 - latest components, bug fixes and improvements"?
- Wed Dec 02, 2015 4:23 pm
- Forum: Flowcode V6
- Topic: SOLVED: Problem sending character to LCD via UART/Serial
- Replies: 8
- Views: 5148
Re: Problem sending character to LCD via UART/Serial
I know the clock and baud are right. I have run lots of tests. The only change is now trying to send a string (array) one byte-at-a-time. When I pass "0x41" an "A" is displayed (confirming baud is right), but passing StringVar[4] does not work, even though it appears to pass a valid ASCII code to th...
- Wed Dec 02, 2015 6:09 am
- Forum: Flowcode V6
- Topic: SOLVED: Problem sending character to LCD via UART/Serial
- Replies: 8
- Views: 5148
SOLVED: Problem sending character to LCD via UART/Serial
Target: PIC18F4580 Programmer: PICKIT3 OS: Windows 10 home 64 bit FlowCode 6.1.2.0 (11.05.2015) Send a 0x41 to the screen and it puts an "A" exactly as expected. Send a member of the string array, and display prints junk Tracing variable as passed to the serial send routine, it looks exactly as I wo...
- Mon Nov 30, 2015 7:14 pm
- Forum: Flowcode V6
- Topic: Component Problem
- Replies: 6
- Views: 3959
Re: Component Problem
I did not know what I was really looking for. The CAL_UART code will do just fine. I can write the supporting buffer code.
It still seems uncool, however that some of this cool functionality is excluded.
I'm just sayin.
It still seems uncool, however that some of this cool functionality is excluded.
I'm just sayin.
- Mon Nov 30, 2015 7:12 pm
- Forum: Flowcode V6
- Topic: SOLVED: Error code 1: unknown identifier 'FCM . . .
- Replies: 3
- Views: 3370
Re: SOLVED: Error code 1: unknown identifier 'FCM . . .
Here is the (self created) problem and solution. The key was when I said "preparation to make a component". While experimenting, I set the macros as " Embedded Macros " in the Interface Manager. After watching a few more YouTube videos, I tried switching the macros to " Downloadable Macro " and ever...
- Mon Nov 30, 2015 4:41 am
- Forum: Flowcode V6
- Topic: SOLVED: Error code 1: unknown identifier 'FCM . . .
- Replies: 3
- Views: 3370
SOLVED: Error code 1: unknown identifier 'FCM . . .
Okay, I've battled a lot of stuff getting this to work. Target: PIC18F4580 Programmer: PICKIT3 OS: Windows 10 home 64 bit FlowCode 6.1.2.0 (11.05.2015) I got the PICKIT3 to work. I solved the Low Voltage Programming problem, I cracked the OSSCON setting requirement. I tested some code to write 16 co...
- Mon Nov 30, 2015 2:02 am
- Forum: Flowcode V6
- Topic: Component Problem
- Replies: 6
- Views: 3959
Re: Component Problem
Please tell me this is still not true. I had no idea the hobby/student version was "neutered". I agreed to no commercial use, but I was not clear there was reduced functionality. How do you folks address this obvious oversight on the part of your promotional materials. p.s. it is not OK to point to ...