Matrix user forums

Whilst you can go to Build>View C-Code, it may not be what you need. That's what I've been using so far. I can use that code to create C-code blocks and replace various macros with actual C code, and that gives me the ability to insert my own debugging code (for example, insert LED blinkers at plac...

In v10, source codes were kindly made available in the WiKi. It is well worth the upgrade in my opinion. https://www.flowcode.co.uk/wiki/index.p ... AL)_(Misc) Thanks for the info. I was hopeful, but unfortunately it's not C source code. I'm trying to see why the LCD_i2c function "FCD_0c591_lcd_I2C...

Flowcode v10 is different as it has no trial, so no time limit. So long as you have got one of the free target devices shown here and the required toolchains from here you will be good to go My Flowcode v10 runs in trial mode, it just doesn't work with any PICs I have on hand, including the 18F27K4...

As I'm sure you know, v10 and all components are free for non commercial use so it is certainly worth considering. When they first announced v10 a long time ago I downloaded it and registered for the free trial. But work got in the way and I never got time to try it out, so now I can't investigate ...

What version of FC are you using? I ask as my FC v7.3.0.7 shows a very different properties dialogue layout to yours. Oops, you're right, my screenshot was taken after testing with FC8 on a colleague's machine. My actual setup is FC7 v7.3.0.6, and here is the FC7 screenshot of the LCD component: Sc...

Hi - I recently revived a mature FC7 (7.3.0.5) project. It was originally developed on FC7 and has worked well for years. The project originally used 16F886 or 18F2320 chips interchangeably. It still compiles under FC7 and works with those chips. However, I now need to move to 18F27K40 chips for thi...

Yes, the updates resolved my problem.

Thanks for keeping the older versions of Flowcode fixed and operational...

OK, I guess I missed it first time through, but just saw the post about FC7 updates: Flowcode 7 - Updates Since 7.3 Flowcode.exe - Main Executable bug: Constant Strings were causing compilation errors when used as a macro parameter I'll download that update and try it out, and will post back my resu...

Hi - I recently revived a mature FC7 (7.3.0.5) project originally developed under Windows 10 32-bit. The original compiler version was XC8 1.41. It had previously compiled with no problems. Since the original development I have moved on to Windows 10 64-bit and XC8 version 2.31. The original project...

Very nice explanation, thank you, Benj. I can now see why simply exporting and importing the macros didn't work, there are a few more steps involved. I hadn't looked into Flowcode events previously because I didn't really see any apparent benefits to real-world development aside from manipulating si...

Thank, Benj, the test file works as expected. I tested both hardware and simulation and didn't have to change anything to get both to work correctly with your file. But when I exported the macros and imported them into my own program, it didn't work. I see that your program has a decision that has a...

Sometimes delay parameters need to be tweaked for operation on hardware vs. simulation. For example, I have a button that needs to detect a long press vs. a short press. It appears that simulation ignores debounce delays, thus affecting the time spent in loops checking switches. Is there a technique...

Ah, sweet success! You are absolutely right, clearing the preset EEprom values makes all of my test files function as they should.

And a workaround is a simple macro to re-populate the EEprom to initial values on first run after programming.

Thanks, Benj, much appreciated...

Regarding the EEPROM problem, please can you try this updated CAL file to see if this helps to solve the problem. It's working correctly on a 16F18877 device so hopefully it will also fix the problem on your device. Thanks Benj. But...it still refuses to function on the actual MPLABXpress hardware....

OK, I found that if I modify the revised "Microchip MPLABXpress.fcdx" file I can get the program to compile. I changed these lines: <defines code="__PROG_CONFIG(0x1, 0x3F8C);\n__PROG_CONFIG(0x2, 0x37FD);\n__PROG_CONFIG(0x3, 0x3D8D);\n__PROG_CONFIG(0x4, 0x1FFF);\n__PROG_CONFIG(0x5, 0x3FFF);\n\n" /> <...

I'm still trying to figure out why the files provided above cause compilation to fail.... Looking at the c file generated by using the MPLABxpress project option, which WON'T compile, I see this: unsigned char FCP_NULL = 0; __PROG_CONFIG(0x1, 0x3F8C); __PROG_CONFIG(0x2, 0x37FD); __PROG_CONFIG(0x3, 0...

More info: when I change the Project Options target to 16F18855 and set the config bits to the settings generated by the MPLABxpress target setting (see attached screenshot), the project compiles successfully but still will not run successfully after dragging the .hex file to the MPLABxpress virtual...

Hmmm... Although the previous PIC_CAL_EEPROM.c file compiled ok, the new one fails to compile on my xc8 installation using the example program I provided: http://www.matrixtsl.com Launching the compiler... C:\Program Files\Flowcode 7\compilers\pic\bin\xc8.exe --chip=16F18855 "eeprom_test.c" --MSGDIS...

Hi - I'm using the MPBLABxpress (16F18855) EEprom component provided in this thread: https://www.matrixtsl.com/mmforums/viewtopic.php?f=64&t=19036&p=82573&hilit=mplabxpress#p82573 This device simulates fine in Flowcode and compiles in xc8, but when performing a "Compile to Chip" the hex file appears...

OK, figured it out. Turns out the ADC components that were imported from the FC6 program had the ADC conversion speeds set at FOSC/2, which simulates correctly in Flowcode but fails as described above on actual hardware (18F2620 w/ 20 MHz xtal). Even when I replaced the FC6 components with FC7 compo...

Strange...I was prepping my project to upload as requested and it was so big (lots of macros) I decided to strip down the size...that became a hassle so I decided to just start clean with a new project using the same ADC macros, using the same hardware. Lo and behold, the new project works as expect...

I feel like there's a simple explanation for this, but I'm getting dizzy trying to find it... I have an 18F2620 with 3 ADCs. With Flowcode 7 simulation, all three ADCs read correctly from 0 volts to 5 volts using "getVoltage()" and from 0 to 1023 using "getInt()". And when I simulate the hardware us...

Bravo. Works perfectly. Thank you.

Hi - I've been working with the MPLAB Xpress board. Very cheap for what you get, love the integration with Flowcode. "Compile to Chip" works great, is better than getting out the ICD3 to program the PIC. Looks like there's been some good interaction with Microchip on this. However, I just added an E...

OK, thanks for the info. I am impressed by the FC7 / Xpress board integration, just was wondering if there is more to come in terms of chip support. I'm sure it's a never-ending job for you guys to keep up with all the hardware options.