Need help with compiling error

[Maoam]

I have been working on a Eblocks 2 BL0114 program. When using debug, the project works completely fine but when I compile to the physical combo board, the LCD does not display anything even after it said file sent when compiling. Weird thing is that the compile worked fine this morning but after making changes and edits throughout the day, nothing appears on the LCD even though it says file sent when compiling. I even tried to deleted most of the subroutines and use only a LCD_start and printstring but still nothing.

[medelec35]

Sorry, we are unable to help if projects not working as expected as it's not added to your post.
The files to add are .fcfx, .msg.txt, and if FC11 .fcxlog.txt

You will also need to use the v10 or v11 post icons available when using the Full editor.

[Maoam]

Hi, sorry about the icons. Here is my file.

Flowcode detection system.fcfx

Detection system

(30.74 KiB) Downloaded 13 times

[mnfisher]

Try adding a C-Code block with the following lines at the start of 'Main'

OSCCON1 = 0x60;
OSCCON3 = 0x00; // No tuning
OSCFRQ = 0x06; // 0x06 = 32 MHz

Martin

[Maoam]

Yes I will try that tomorrow when I go to my step dads as the setup is at his. Just wondering do you think there are any thing about the flowchart logic that could cause issues.
Another thing, I heard that making too many changes/edits could corrupt the file and cause the compile to not work properly. Do you think that may be the case.

[mnfisher]

You should be able to edit the file as required - this shouldn't cause compilation issues. Like most things in computing - backups are good! Save your work occasionally (or turn on 'autosave') to prevent heartbreak too.

The logic is a little odd - each macro Main, Start, A3 etc have the bulk of the code in an infinite loop - so will never return. For example in main - if a2 is high then Start is called (and never returns) - and if a3 is high then plate_count is called. This may be the intended action (loop in main until either a2 or a3 is pressed - and then perform the chosen action forever?)
If these are 'user' inputs (buttons rather than a digital signal) then using a button component to filter out 'bounce' is a good idea too.
Having specific timings before a signal ('Press ...', delay 1s, read pin might cause issues - what if the user is a little 'slow' reacting?

Martin

[Maoam]

Thanks for the info. With the logic being kinda of flawed would that be a factor for the compile to not operate properly on the LCD. Or would it just a be flaw to the user experience.

[mnfisher]

Just the user experience. Hopefully the oscillator settings will get the display (and the MCU) running...

Martin

[medelec35]

Hello.
As you are using the 16F18877, it is set up to work at 32MHz internal osc with no additional c code.
The issue looks like its with your hardware port selection.
If you look at page 10 of the Eblocks2 datasheet it shows the connections for the display is on port 2.

BL0114 Connections.png (42.56 KiB) Viewed 69 times

You have port 2 (what LCD is connected to) of BL0114 set to D.
If you connect port 2 (same side as the pot) to port D of the BL0011 then port 1 of BL0114 is not physically connected to anything, its left hanging in mid air!
On you project you have set it to Port A .
To connect Port 1 to A and Port 2 to D is impossible.

You need to change Port 2 of BL0114 to port B which is the intended port.
Then recompile.