Page 1 of 1

FLOW CODE V6.4 7 SEGMENT 4DIGIT BUG ?

Posted: Sun Mar 09, 2014 4:41 pm
by sonic11
welcome

Refer the following problem
I Realizar a counter with 4 digits in flow v6 code works normal flow simulation code v6 but physical installation does not work, nor in Isis

Re: FLOW CODE V6.4 7 SEGMENT 4DIGIT BUG ?

Posted: Sun Mar 09, 2014 8:38 pm
by medelec35
Can you explain what is different with your hardware when comparing to simulation.
Also a full circuit diagram and a datasheet of 7seg display will help.
If I get time I will put a flowchart together and test a common cathode Quad 7seg display.
Are you using a common anode quad 7seg?

Re: FLOW CODE V6.4 7 SEGMENT 4DIGIT BUG ?

Posted: Sun Mar 09, 2014 10:39 pm
by sonic11
hello Medelec

I rewrote the code flow V5.4 and the program works ok with a Displays common anode, the same program written in v6.4 does not work a display common anode or common cathode

There is no question of wrong installation, the display turns chaotic prints not digits

Wiring diagram can be found in the file (counter Isis Proteus tab)

Re: FLOW CODE V6.4 7 SEGMENT 4DIGIT BUG ?

Posted: Mon Mar 10, 2014 5:51 pm
by Benj
Hello,

I have had a look through your program and it would appear it's the IOC interrupt that's causing the problems as this will fire on any change to the input or output on the upper 4 PortB pins.

I have hopefully fixed the issue for you here,
COUNTER MOD_v6.fcfx
(10.31 KiB) Downloaded 326 times

Re: FLOW CODE V6.4 7 SEGMENT 4DIGIT BUG ?

Posted: Mon Mar 10, 2014 9:15 pm
by sonic11
hello

in this situation what to do, how to use interrupt on port B?
In V5.4 works perfectly, so it is a bug? if yes how to solve?
I am interested to use interrupt on prot B

Re: FLOW CODE V6.4 7 SEGMENT 4DIGIT BUG ?

Posted: Tue Mar 11, 2014 11:30 am
by Benj
Hello,

In Flowcode v5 we would have used a port and a mask to allow us to write to the PortB register using a single instruction.

In v6 we have taken a different approach and used pins to make things more universally simple to work with and configurable, however this will likely end up with two writes to PortB, one for each pin that changes state. This then breaks the state machine you had so I re-wrote the program in a way where the state machine will always work reliably.