DOCU to the Flowcode language

For questions and comments on programming in general. And for any items that don't fit into the forums below.

Moderators: Benj, Mods

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

DOCU to the Flowcode language

Postby Rudi » Tue May 13, 2014 4:29 pm

Hi
Where i can find the Docu to the Flowcode language?
In FC 6 there is no Docu only a small CAL PDF for FC5.
The online Wiki does not know about Flowcode Function FCI_SCOPY
Where are the Declaration for the Syntax and Language?
Thank you!
best wishes
Rudi

User avatar
DavidA
Matrix Staff
Posts: 1056
Joined: Fri Apr 23, 2010 2:18 pm
Location: Matrix Multimedia Ltd
Has thanked: 58 times
Been thanked: 274 times
Contact:

Re: DOCU to the Flowcode language

Postby DavidA » Tue May 13, 2014 5:19 pm

Hello Rudi,

There is no manual for the internal c declarations for Flowcode, most of these are tied up in our protected CAL components.

What do you need them for?

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

Re: DOCU to the Flowcode language

Postby Rudi » Tue May 13, 2014 5:24 pm

DavidA wrote:Hello Rudi,

There is no manual for the internal c declarations for Flowcode, most of these are tied up in our protected CAL components.

What do you need them for?



Hi David,
and how i know this , how this must add in a C Icon ?
..
please have a look to my thread:
viewtopic.php?f=7&t=14813
...

TY.
...

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

Re: DOCU to the Flowcode language

Postby Rudi » Wed May 14, 2014 11:21 pm

DavidA wrote:Hello Rudi,

There is no manual for the internal c declarations for Flowcode, most of these are tied up in our protected CAL components.

What do you need them for?



David,

Leigh said in
viewtopic.php?f=7&t=14813&p=59798#p59785

detailed Flowcode Instruction how that can make in a C Code icon.

(Edit translater *..)

but where know the user, what Syntax is needed for the right C Code.. that is no C .. *because is Flowcode Language..

So i ask, where can i read the Flowcode Language for making by *making self *a c code in the c code icon ..in Flowcode Language...

without a manual for this important syntax info how this must write *by *user nobody can make the right c code in flowcode language in c code icon....*that *is *needed

Why this not exist?

Please!

Understand, without a manual for this important syntax info how this must write nobody can make the right c code in flowcode language in c code icon....

... i will *try *to *start *by *myself ... ..making function .. and look into C code window how Flowcode work internal and will write next Time a small Handbook with the Titel:

"MANUAL for the internal C declarations for Flowcode V6" and post this here if there no manual -

sad sad sad....

* ;-)

:-) !!! ;-) "What are you doing the full day" !!! ;-) ;-) !!! ;-) ;-)

!-> ;-) <- !

Rudi

ps

is it possible to get a wiki member?

( *so i start a try to make items step by step what i find..in c code window )

User avatar
DavidA
Matrix Staff
Posts: 1056
Joined: Fri Apr 23, 2010 2:18 pm
Location: Matrix Multimedia Ltd
Has thanked: 58 times
Been thanked: 274 times
Contact:

Re: DOCU to the Flowcode language

Postby DavidA » Fri May 16, 2014 3:07 pm

Hello Rudi,

C-code -> Flowcode variable definitions can be seen on this wiki entry here:

http://www.matrixmultimedia.com/wiki/in ... Properties

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

Re: DOCU to the Flowcode language

Postby Rudi » Fri May 16, 2014 5:22 pm

DavidA wrote:Hello Rudi,

C-code -> Flowcode variable definitions can be seen on this wiki entry here:

http://www.matrixmultimedia.com/wiki/in ... Properties



Hi David,
ty, i have see this...
i have read this from begin to end.. and back...

but...



For example, to use a Flowcode variable called DELAY in your C code, you must refer to it using FCV_DELAY

Note that all Flowcode defined variables are upper case.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is not right.


To call a Flowcode macro called TEST in your C code, you must call FCM_TEST();

Note that all Flowcode macro names are upper case.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is not right





because......
see my picture..


btw David.

this is not declare in the wiki..


So a string variable:
MyString[30]

Creates the following C code:
#define FCVsz_MYSTRING 30
MX_GLOBAL MX_CHAR FCV_MYSTRING[FCVsz_MYSTRING];

FCV_MYSTRING is the variable name and FCVsz_MYSTRING is its buffer size

hence:
// MyString = "Hello"
FCI_SCOPY("Hello",6, FCV_MYSTRING, FCVsz_MYSTRING);

This copies the 6 characters of Hello into the FCV_MYSTRING buffer, which has a maximum size of FCVsz_MYSTRING



is this FUNCTIONS secret?

i do not know why --- but is ok too.

Again ;-) resistant to encounter for open Flowcode Language.
How to C code can insert then if you can not read the Flowcode language as it needs to be done?

but that's ok.

I can see it already. Here large resistor is operating.

Very well. Without Open explanations to read I and other .. can not go on as before.

I have been "experimenting" four weeks to UART, USB, SPI ect. and no go on right...
i have make baudrate tests.. have change FLOWCODE BaudrateGenerator File... no way..

Until then has been found that there is a timing bug in a important ms ...

and at time:

DavidA wrote:Hello Rudi,

The bug is on our lists, we are not due another release however for a while and hopefully it will be fixed when the next release is due


...

a workaround is not availabel ...

;-(

microcontroller works fine only if timing is corect ...

I would not have found, I would read C code can not.

If I can not read the Flowcode Language,
I will put together this code to me via the C window piece by piece.
That's no secret.

I want to develop with FC as well.
I am impressed by the flow chart principle.
But I bought FC for a fast working ......

i have noted this

viewtopic.php?f=7&t=14827

kersing wrote:BoostC is licensed for use by Flowcode only. The software can not be used in stand alone mode or integrated into another product.


this is not fine... and i will clear this next time with distributor....but good..


i go back to mplap next time for the next newest projects,
because i do not know, is there a mistake in my code ... or is it a bug again..

all App Notes can read at Microchips..

In my Tests with UART i work long long Time..
make many Test and Docu to this..

I have write that possible the Cal is wrong in FC

viewtopic.php?f=54&t=14635&p=59839#p58802

also how BaudrateGenerator is possible settings by wrong parameter...

[img] download/file.php?id=14289
[/img]

Code: Select all


                 
                 
//Hardware Baud update definitions                 
#ifndef MX_HARD_BAUD_CHANGE_DEFS                 
   #define MX_HARD_BAUD_CHANGE_DEFS               
// Rudi 4.4.2014                 
   #define MX_HARD_BAUD_1200   ((MX_CLK_SPEED / 1200) / 16 ) - 1           
   #define MX_HARD_BAUD_2400   ((MX_CLK_SPEED / 2400) / 16 ) - 1           
   #define MX_HARD_BAUD_4800   ((MX_CLK_SPEED / 4800) / 16 ) - 1           
   #define MX_HARD_BAUD_9600   ((MX_CLK_SPEED / 9600) / 16 ) - 1           
   #define MX_HARD_BAUD_19200   ((MX_CLK_SPEED / 19200) / 16 ) - 1           
   #define MX_HARD_BAUD_38400   ((MX_CLK_SPEED / 38400) / 16 ) - 1           
   #define MX_HARD_BAUD_57600   ((MX_CLK_SPEED / 57600) / 16 ) - 1           
   #define MX_HARD_BAUD_115200   ((MX_CLK_SPEED / 115200) / 16 ) - 1           
                 
// Original                   
//   #define MX_HARD_BAUD_1200   (((MX_CLK_SPEED / 1200) - 16) / 64)           
//   #define MX_HARD_BAUD_2400   (((MX_CLK_SPEED / 2400) - 16) / 64)           
//   #define MX_HARD_BAUD_4800   (((MX_CLK_SPEED / 4800) - 16) / 64)           
//   #define MX_HARD_BAUD_9600   (((MX_CLK_SPEED / 9600) - 16) / 64)           
//   #define MX_HARD_BAUD_19200   (((MX_CLK_SPEED / 19200) - 16) / 64)           
//   #define MX_HARD_BAUD_38400   (((MX_CLK_SPEED / 38400) - 16) / 64)           
//   #define MX_HARD_BAUD_57600   (((MX_CLK_SPEED / 57600) - 16) / 64)           
//   #define MX_HARD_BAUD_115200   (((MX_CLK_SPEED / 115200) - 16) / 64)           
#endif                 
                 


That all stands in APP Note at Microchip..
that is a BASE Formula ...
and i am sure...

this is wrong included in FC...

and i get no response..

This!


(((MX_CLK_SPEED / 1200) - 16) / 64)
...............................^^^^^^^^^^



is it a Flowcode mistake for include the Formula..

...
or
is it a Bug
or
all two or nothing and i am wrong?

only you can say it - and without a open DOCU that is not possible to find by self whats go wrong.

this is the original Formula

http://ww1.microchip.com/downloads/en/D ... 026583.pdf

Side 9


I really like the Concept of FC ...
.really

i Have bougt AVR + PIC + dsPIC for Commerz blind! I have see your WEB and what all possible,
and bought without Testing...

After this
I only make Test Projects with 2 Chips...

PIC18F2550

PIC24FJ256GB106

with simple Base Commands..

and all two

Bug here
Bug there..

I understand this not.
This Bug's never seen in V2 ..-> V3...-> V4...-> !V5....-> V6 ??

I can not spend more Time in Tests David...i must go on to work with this...and "my Staff"..
and this is not possible because the DOCU is missing too or wrong for going on by self...

a Help File in FC6 is not include.

... it seems at the moment simply not be possible to work right like it must..

simple String Evaluation -> BUG
simple timing -> BUG
receive simple 0x00 -> BUG
and the exist DOCU ... is not right .. a wrong help
:-(

What a pity!

I am your ( FC ) biggest Fan - that must you know..
i am really your biggest Fan...

.. but I've become a bit perplexed.

I very much hope that this will change in the future.

Rudi

kersing
Valued Contributor
Valued Contributor
Posts: 1873
Joined: Wed Aug 27, 2008 10:31 pm
Location: Netherlands
Has thanked: 530 times
Been thanked: 1040 times
Contact:

Re: DOCU to the Flowcode language

Postby kersing » Sun May 18, 2014 8:37 pm

Rudi wrote:For example, to use a Flowcode variable called DELAY in your C code, you must refer to it using FCV_DELAY

Note that all Flowcode defined variables are upper case.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is not right.


Your versions seems to behave differently, in my version all variable names are upper case.

Rudi wrote:To call a Flowcode macro called TEST in your C code, you must call FCM_TEST();

Note that all Flowcode macro names are upper case.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is not right


You are right, up to version 6 the names were upper case, starting with version 6 this is no longer the case. Has been fixed in the wiki.

Rudi wrote:

So a string variable:
MyString[30]

Creates the following C code:
#define FCVsz_MYSTRING 30
MX_GLOBAL MX_CHAR FCV_MYSTRING[FCVsz_MYSTRING];

FCV_MYSTRING is the variable name and FCVsz_MYSTRING is its buffer size

hence:
// MyString = "Hello"
FCI_SCOPY("Hello",6, FCV_MYSTRING, FCVsz_MYSTRING);

This copies the 6 characters of Hello into the FCV_MYSTRING buffer, which has a maximum size of FCVsz_MYSTRING



is this FUNCTIONS secret?


It is Flowcode internal and may change at any time. So you should not use it yourself (IMHO).

Rudi wrote:Again ;-) resistant to encounter for open Flowcode Language.


Flowcode is a commercial product, not an open specification.


Rudi wrote:I have been "experimenting" four weeks to UART, USB, SPI ect. and no go on right...
i have make baudrate tests.. have change FLOWCODE BaudrateGenerator File... no way..


Using the original FCDX files from the installer the hardware baudrate is wrong, it is set to 19200 when the properties say it should be 9600. See attached fix.


Rudi wrote:Until then has been found that there is a timing bug in a important ms ...

and at time:

DavidA wrote:Hello Rudi,

The bug is on our lists, we are not due another release however for a while and hopefully it will be fixed when the next release is due


a workaround is not availabel ...

I have no issues with the Delay icon on the SURE board. (Using the original fcdx file, not the updated one from Benj) You should NOT be setting MX_CLKS_PER_INST to get Delay to work correctly.

Rudi wrote:
kersing wrote:BoostC is licensed for use by Flowcode only. The software can not be used in stand alone mode or integrated into another product.


this is not fine... and i will clear this next time with distributor....but good..


Why is this not fine? You have bought Flowcode not the underlying compilers for stand alone use. Nothing in the Flowcode documentation suggests you did.


Rudi wrote:That all stands in APP Note at Microchip..
that is a BASE Formula ...
and i am sure...


There are two formulas in Flowcode. One to set the baud rate based on the properties. This formula provides the same result as the one in the data sheet. The second set does not have the dsPIC33 and dsPIC24 fixes as you correctly found.

Rudi wrote:This Bug's never seen in V2 ..-> V3...-> V4...-> !V5....-> V6 ??


The bugs with the baud rate for UART_UpdateBaud are in V5 as well.

Attached is an update of PIC16BIT_CAL_UART.c that should fix your baud rate issues.
Attachments
PIC16BIT_CAL_UART.c
(22.98 KiB) Downloaded 176 times
These users thanked the author kersing for the post (total 2):
LeighM (Mon May 19, 2014 9:27 am) • medelec35 (Mon May 19, 2014 4:14 pm)
Rating: 10.53%
 
“Integrity is doing the right thing, even when no one is watching.”

― C.S. Lewis

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

Re: DOCU to the Flowcode language

Postby Rudi » Mon May 19, 2014 2:06 pm

kersing wrote:
Rudi wrote:For example, to use a Flowcode variable called DELAY in your C code, you must refer to it using FCV_DELAY

Note that all Flowcode defined variables are upper case.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is not right.


Your versions seems to behave differently, in my version all variable names are upper case.



I play with V6.0.6 - the 6.0.7 is not clear like user's wrote in the forum.

i will wait for the official release... if stand in Forum "Release 6.0.7"

i do not go on with experimental over "help.. update..."... again.....

The 6.0.6 is only a Release Candidate... not Release.
So stand in the Forum as Theme.

I will wait.

kersing wrote:
Rudi wrote:To call a Flowcode macro called TEST in your C code, you must call FCM_TEST();

Note that all Flowcode macro names are upper case.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is not right


You are right, up to version 6 the names were upper case, starting with version 6 this is no longer the case. Has been fixed in the wiki.




Sorry, where?

:-)

just in Time,



To call a Flowcode macro called TEST in your C code, you must call FCM_TEST();

Note that for Flowcode versions up to Flowcode 6, all Flowcode macro names are upper case.
...........................................................^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


it seems to behave differently wiki's .., in this version

http://www.matrixmultimedia.com/wiki/in ... Properties

all is written like i found before i wrote...

btw:

what is mean with "upper case"..
i understand, if the Macro is name "Test1"
the Macro Name in Code must named "upper case" -> "Test1" -> "TEST1"

case sensitive -> i understand then, it must write like it is "Test1" -> "Test1"
..
I think this must declare in wiki as "case sensitive.".....


kersing wrote:
Rudi wrote:

So a string variable:
MyString[30]

Creates the following C code:
#define FCVsz_MYSTRING 30
MX_GLOBAL MX_CHAR FCV_MYSTRING[FCVsz_MYSTRING];

FCV_MYSTRING is the variable name and FCVsz_MYSTRING is its buffer size

hence:
// MyString = "Hello"
FCI_SCOPY("Hello",6, FCV_MYSTRING, FCVsz_MYSTRING);

This copies the 6 characters of Hello into the FCV_MYSTRING buffer, which has a maximum size of FCVsz_MYSTRING



is this FUNCTIONS secret?


It is Flowcode internal and may change at any time. So you should not use it yourself (IMHO).




Ok...but how i can then work with this in C Code if i not know how this must be handle?

In Wiki stand a Part of them how the "internal C" of Flowcode ( Variable Name, Macro Name ... ) must be handle..

why not

How i can set a ´Stringlist by adding a C Code Icon and use "Flowcode Internal C" ...
like this :

hence:
// MyString = "Hello"
FCI_SCOPY("Hello",6, FCV_MYSTRING, FCVsz_MYSTRING);


This would be fine, if the user can handle this too...

So i think - if i not know how the Internals C is done... do not need to know how a Flowcode Variable must be named in C code ....if not allowed to know how i can make function too...
but...

It Is OK!

I will pic it from C Window all and make my own Handbook.

Btw:

Where are you know this?
..
..
And why this is not writen in Wiki?

A open "API" for Developer would be verry verry helpfully!

but..

is ok


kersing wrote:
Rudi wrote:Again ;-) resistant to encounter for open Flowcode Language.


Flowcode is a commercial product, not an open specification.



;-) .. I know -

MS VS too, but i get the API

Embarcado too, but i get the API and more too...
..


i have buy the Prof as Commercial Version and Chippacks in AVR, PIC & dsPIC ( over 700 EUR ) without before i Test...

This was a verry wrong doing!

Next Time i will ask too,

"Can i get a Beta Version - i will play with this and post all what i find wrong...perhabs i will buy this later time..."



I feel me as a Beta Tester that had Pay 700 EUR for can Play with this a liitle !

count the bugs that i have found in the three mounths only in 2 chips...!...only in simply beginner projects...
i do not start technicals / productive projects with FC6 ... next time.. i will go on back traditionell writting code..
But this is not the Theme of this Thread. This i will clear with my Distributor.
Perhabs i give FC6 back...I had a think about a Volume Licenze for my Concern internal and external 1200 staff.
But at Time i have stop this thinking. FC6 is not ready stability to go just in Time... and this is not only says from me...


...Work on the v6 application has currently stalled as our main C++ engineer Jonny has now left Matrix and the new engineer Martin is now away on holiday. As soon as he is back we will be able to proceed with bug fixes and stability improvements. One of Martins main tasks is to improve stability and to reduce the number of bugs. We know this is frustrating for users so please bear with us.




All must followed at the Forum exactly for clear a possible Bug.
I can not spend more Time for Test - i must work with this ...

I have make a Experiment with this FC6, and have say, i will spend 3 Month for learn and know all - that can help other in our concern and make inhouse learn, without a open DOCU this simply not possible clear in all ..
but ok... your comment is welcome,

..but ..

if i buy a 1000 Volume Licence for my Staff, and include FC6 in my Business for Work with this in Future ...and all will spend 1 hour all day in Forum for get his/her Project running ( all works with not the same Chips.. ) .. i can close my business.
so - i have stop this thinking just in Time about a 1000 Volume License!

Just in Time - I get help from you - not from MM Staff.

This is pitty!

but ok!


kersing wrote:
Rudi wrote:I have been "experimenting" four weeks to UART, USB, SPI ect. and no go on right...
i have make baudrate tests.. have change FLOWCODE BaudrateGenerator File... no way..


Using the original FCDX files from the installer the hardware baudrate is wrong, it is set to 19200 when the properties say it should be 9600. See attached fix.



TY - i will try yours...


kersing wrote:
Rudi wrote:Until then has been found that there is a timing bug in a important ms ...

and at time:

DavidA wrote:Hello Rudi,

The bug is on our lists, we are not due another release however for a while and hopefully it will be fixed when the next release is due


a workaround is not availabel ...


I have no issues with the Delay icon on the SURE board. (Using the original fcdx file, not the updated one from Benj) You should NOT be setting MX_CLKS_PER_INST to get Delay to work correctly.



TY - i will try yours...


kersing wrote:
Rudi wrote:
kersing wrote:BoostC is licensed for use by Flowcode only. The software can not be used in stand alone mode or integrated into another product.


this is not fine... and i will clear this next time with distributor....but good..


Why is this not fine? You have bought Flowcode not the underlying compilers for stand alone use. Nothing in the Flowcode documentation suggests you did.




Ok - i have correspondenz with BoostC Staff last time...
a answere from the BoostC Staff - "Paval" has all Information what i need to do ..
we are in contact. and will thinking over own IDE without Simulation...

kersing wrote:
Rudi wrote:That all stands in APP Note at Microchip..
that is a BASE Formula ...
and i am sure...


There are two formulas in Flowcode. One to set the baud rate based on the properties. This formula provides the same result as the one in the data sheet. The second set does not have the dsPIC33 and dsPIC24 fixes as you correctly found.



..this is new....TY...




//Hardware Baud update definitions
#ifndef MX_HARD_BAUD_CHANGE_DEFS
#define MX_HARD_BAUD_CHANGE_DEFS
#if defined(__dsPIC33E__) || defined(__dsPIC33F__) || defined(__PIC24E__) || defined(__PIC24F__) || defined(__PIC24H__)
#define MX_HARD_BAUD_1200 (((MX_CLK_SPEED / 1200) - 16) / 32)
#define MX_HARD_BAUD_2400 (((MX_CLK_SPEED / 2400) - 16) / 32)
#define MX_HARD_BAUD_4800 (((MX_CLK_SPEED / 4800) - 16) / 32)
#define MX_HARD_BAUD_9600 (((MX_CLK_SPEED / 9600) - 16) / 32)
#define MX_HARD_BAUD_19200 (((MX_CLK_SPEED / 19200) - 16) / 32)
#define MX_HARD_BAUD_38400 (((MX_CLK_SPEED / 38400) - 16) / 32)
#define MX_HARD_BAUD_57600 (((MX_CLK_SPEED / 57600) - 16) / 32)
#define MX_HARD_BAUD_115200 (((MX_CLK_SPEED / 115200) - 16) / 32)

#else
#define MX_HARD_BAUD_1200 (((MX_CLK_SPEED / 1200) - 16) / 64)
#define MX_HARD_BAUD_2400 (((MX_CLK_SPEED / 2400) - 16) / 64)
#define MX_HARD_BAUD_4800 (((MX_CLK_SPEED / 4800) - 16) / 64)
#define MX_HARD_BAUD_9600 (((MX_CLK_SPEED / 9600) - 16) / 64)
#define MX_HARD_BAUD_19200 (((MX_CLK_SPEED / 19200) - 16) / 64)
#define MX_HARD_BAUD_38400 (((MX_CLK_SPEED / 38400) - 16) / 64)
#define MX_HARD_BAUD_57600 (((MX_CLK_SPEED / 57600) - 16) / 64)
#define MX_HARD_BAUD_115200 (((MX_CLK_SPEED / 115200) - 16) / 64)
#endif
#endif



Jac - if i not Test the Chippack with a PIC24.. and find and write this... the bug will be next Verision too...
so -

only a question:

If i can not help me self in Internal C Flowcode Language...how will this find in future in other Modules?

But ok - i have accepted - MM Stuff will not make Internals C open.

Is ok.

But i stop with my Experiment with FC6 now too.

Perhabs the MM Concern will thinking about next Time over a "Base Internals C How To."..

...
if so, let me know and i go on again.


kersing wrote:
Rudi wrote:This Bug's never seen in V2 ..-> V3...-> V4...-> !V5....-> V6 ??


The bugs with the baud rate for UART_UpdateBaud are in V5 as well.

Attached is an update of PIC16BIT_CAL_UART.c that should fix your baud rate issues.



TY - i give yours a Try...


Best wishes
Rudi

User avatar
DavidA
Matrix Staff
Posts: 1056
Joined: Fri Apr 23, 2010 2:18 pm
Location: Matrix Multimedia Ltd
Has thanked: 58 times
Been thanked: 274 times
Contact:

Re: DOCU to the Flowcode language

Postby DavidA » Mon May 19, 2014 4:09 pm

Hello,

There is a 6.0.7 full release available go to Help >> Check for Updates to get the release.

Here are the String CAL definitions:

String CAL

char FCI_GETCHAR(char* sStr1, char iStr1_len, char iPos);

char FCI_GETLENGTH(char* sStr1, char iStr1_len);

char FCI_MIDSTRING(char* sSrc, char iSrc_len, char* sDst, char iDst_len, char iStart, char iCount);

char FCI_LEFTSTRING(char* sSrc, char iSrc_len, char* sDst, char iDst_len, char iCount);

char FCI_RIGHTSTRING(char* sSrc, char iSrc_len, char* sDst, char iDst_len, char iCount);

char FCI_CONCATENATE(char* sSrc1, char iSrc1_len, char* sSrc2, char iSrc2_len, char* sDst, char iDst_len);

char FCI_TOSTRING(int iSrc1, char* sDst, char iDst_len);

void FCI_TOLOWER(char* sSrc, char iSrc_len, char* sDst, char iDst_len);

void FCI_TOUPPER(char* sSrc, char iSrc_len, char* sDst, char iDst_len);

char FCI_COMPARE(char* sSrc1, char iSrc1_len, char* sSrc2, char iSrc2_len, char iNoCase);

char FCI_FLOAT_TO_STRING(float Number, char Precision, char* String, char MSZ_String);

char FCI_NUMBER_TO_HEX(short Number, char* String, char MSZ_String);

long FCI_STRING_TO_INT(char* String, char MSZ_String);

float FCI_STRING_TO_FLOAT(char* String, char MSZ_String);

char FCI_STRREV(char* sSrc, char iSrc_len, char* sDst, char iDst_len);

char FCI_STRMOV(char* sSrc, char iSrc_len, char* sDst, char iDst_len);

char* FCI_SHEAD(char* sSrc1, char iSrc1_len, char* sSrc2, char iSrc2_len, char* sDst, char iDst_len);

char* FCI_SCOPY(char* sSrc, char iSrc_len, char* sDst, char iDst_len);

We have discussed in the past opening up the CAL documentation, the decision was not to release this to the public initially. If it is something users want then we can revisit the discussion.

As for the potential timing bug, i cannot comment at the moment, 'Ben' our component guy is on holiday for a couple of weeks, i can only postulate as to what the problem maybe.
These users thanked the author DavidA for the post:
Rudi (Mon May 19, 2014 8:20 pm)
Rating: 5.26%
 

User avatar
LeighM
Matrix Staff
Posts: 1888
Joined: Tue Jan 17, 2012 10:07 am
Has thanked: 445 times
Been thanked: 640 times
Contact:

Re: DOCU to the Flowcode language

Postby LeighM » Mon May 19, 2014 4:11 pm

Hi Rudi,

I have attached a simple Flowcode program to show you how to use C within a Flowcode macro.
If you compile to C, you can view the resulting C code to confirm the interface.

Using C is documented, it’s just any internal functions that aren’t, as these may change.

Also, Jonny wrote a good article, probably more than you need, but it can be found here…
http://matrixmultimedia.com/blog/?p=146

Regards,
Leigh
Attachments
C_CODE_IN_MACRO.fcfx
(4.47 KiB) Downloaded 95 times
These users thanked the author LeighM for the post:
Rudi (Mon May 19, 2014 8:19 pm)
Rating: 5.26%
 

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

Re: DOCU to the Flowcode language

Postby Rudi » Mon May 19, 2014 8:10 pm

DavidA wrote:Hello,

There is a 6.0.7 full release available go to Help >> Check for Updates to get the release.


Hi David,
thank you! Please .. You must in Future decision this as a Theme in Forum.
In Forum stand the Thread "Release Candidate 6.0.6

Not, that all in this is released in a There is a 6.0.7 full release available how you wrote..

It is ** insecure.
Is that .. a further release candidate
is now a revision of the Release Candidate 6.0.7
but where was then Candidate 6.0.7? ..

This ** bewilders the user, David,
There is also no revision list.
There is also no list, officially known as thread, which has been cleaned and what not.
...
;-( this is the only what i am not like at FC / and the Staff ;-)...
never is talking together.. ... a update in !! version 6.0.7 !! is !! RELEASED !! ,,,
but in Forum is discussed a Release Candidate !!! 6.0.6 !! ...
..
mhm...

but ok...

i will make this at evenning. I hope i will not regret it, because this 6.0.6 have the "patches" now from benj, martin, jac and yours and is still work ( only the timing and little knowed bugs.. ect. )

i will install for first time at Laptop.. ok. Thank you for your Service!


DavidA wrote:

Here are the String CAL definitions:

String CAL

char FCI_GETCHAR(char* sStr1, char iStr1_len, char iPos);

char FCI_GETLENGTH(char* sStr1, char iStr1_len);

char FCI_MIDSTRING(char* sSrc, char iSrc_len, char* sDst, char iDst_len, char iStart, char iCount);

char FCI_LEFTSTRING(char* sSrc, char iSrc_len, char* sDst, char iDst_len, char iCount);

char FCI_RIGHTSTRING(char* sSrc, char iSrc_len, char* sDst, char iDst_len, char iCount);

char FCI_CONCATENATE(char* sSrc1, char iSrc1_len, char* sSrc2, char iSrc2_len, char* sDst, char iDst_len);

char FCI_TOSTRING(int iSrc1, char* sDst, char iDst_len);

void FCI_TOLOWER(char* sSrc, char iSrc_len, char* sDst, char iDst_len);

void FCI_TOUPPER(char* sSrc, char iSrc_len, char* sDst, char iDst_len);

char FCI_COMPARE(char* sSrc1, char iSrc1_len, char* sSrc2, char iSrc2_len, char iNoCase);

char FCI_FLOAT_TO_STRING(float Number, char Precision, char* String, char MSZ_String);

char FCI_NUMBER_TO_HEX(short Number, char* String, char MSZ_String);

long FCI_STRING_TO_INT(char* String, char MSZ_String);

float FCI_STRING_TO_FLOAT(char* String, char MSZ_String);

char FCI_STRREV(char* sSrc, char iSrc_len, char* sDst, char iDst_len);

char FCI_STRMOV(char* sSrc, char iSrc_len, char* sDst, char iDst_len);

char* FCI_SHEAD(char* sSrc1, char iSrc1_len, char* sSrc2, char iSrc2_len, char* sDst, char iDst_len);

char* FCI_SCOPY(char* sSrc, char iSrc_len, char* sDst, char iDst_len);




Ty but..
I know this CAL David..
but the "declare" for better understanding will be,
what is mean with "sSrc".."sDst"..
ok i can think about.. s=string..Src=Source...s=String..Dst= Destination
but this not allways clear to all user..

char FCI_GETCHAR(char* sStr1, char iStr1_len, char iPos);
..
only example!...

what is mean with the iPos ?
the IDX ..start with 0
the Letter Pos.. start with 1
...

a docu to this .. a really update DOCU from V5 to V6 was very fine...
and the offline Help in Flowcode V6 again too.

Many Futures are in FC6 new, but only small Helps can read only online...and after ask in Forum..

One Thinking will be fine for the First Moment..
In Wiki the function "Print to Pdf".. so user can make a Handbook every time...
..

David, please understand ... not allways is it allowed in concern from Productive PC // LAptop go to Internet. There a strict rules in R & D departments.. in our "business group" example, is not allowed to use handy ect too...
so how i can get help for read .. if i need...
.. this is a point, if MM Stuff discussed in Future, to decision for a offline help ... will be fine

David,, .. in shool example, in "Final examinations".. "Tests" i hope i declare the right words.. is not allowed to go on online...
but is allowed to use Helpfiles...


DavidA wrote:
We have discussed in the past opening up the CAL documentation, the decision was not to release this to the public initially. If it is something users want then we can revisit the discussion.


Ok - i have noted - that if something users "need" a info - that this can revisit the discussion perhabs to get this Info..
ok david..

i do not want, that FC must be opening like a Book... no ..this is the "Trade secret Of MM " this i accept David - this is normaly..
i only want "more" declare in Help Files.. example this CAL Docu... ..or ...

a HINT...

example:.

If i put a INTERUPT ICON in Flowchart.. ok?..
then i think . at this position the INterrupt will be "active"...
i have test with an "crazy" example.. USBINT0... i know.. if i do this the USB Serial will deactivate with this.. and will not running..
i test only the "doing of FC6"...
so i do not delete the INTERRUPt ICON..
i edit this "Customize CODE C"..
with simple // all.
so i have mean "as a normaly flowchart user"
the INTERRUPT ICON is "deaktive"
i hope you undestand me..
so i am surprise, that the code is not start my USB Serial ...after // all in C Customize Code in Interrupt ICON..
..

Flowcode makes more Code in C WIndow .. as the C Code in INTERUPT ICON is listed..

That have i not know! Because - that is not declare in Help ICON INterrupt
..
i must delete the ICON, if i will "deaktivate" this ...

so my next future request will be "a check box at icons" for active/passive in Flowcharts so user can test more possibles without deletings ICONS and then again make new with all parameters....
with this checkbox option as False.. FC can simualtan "delete" all what FC maked if ICON append.. --as True.. The ICON is activ..

i hope you understand my cross thinking.. i am with yours!!
i really like FC!

---
---

The other Try with siumulation - Martin helped me in this very fine - with updating simple labels at panel in simulation...
... David ;-)... where i can read this doing ... " label1: :text "

viewtopic.php?f=54&t=14600&p=59953#p59918

;-)...

FC has many many "hidden and secret functions ..".. ;-) :-) ;-)


..


btw.

this you posted.. is under ../Flowcode 6/CAL

in the File "CAL - Documetation.pdf" with Theme "Flowcode V5 CAL (Code Abstraction Layer) Docuention

i think this is the same like in FC5 and not up2date with FC6.. because it stand "Flowcode V5 CAL (Code Abstraction Layer) Docuention" not FC6...

DavidA wrote:As for the potential timing bug, i cannot comment at the moment, 'Ben' our component guy is on holiday for a couple of weeks, i can only postulate as to what the problem maybe.


This is ok David - i will make pause to this. is realy ok. i test others Projects without strictly timings.. .. in this time..

But understand me please,
i make this procedure "Test your Software" on my personally way,
i read shortly at the web and want to go on like a normaly user..
( ok - I could have asked if I can be provided for testing purposes for certain CHIPS FC for disposal ..
I ... did not mean to - I support you with proof of their purchase. I do this because i like this - this is my mean.. )

i saw the conzept and my mean is unbroken, your concept is great and have much much more potential like it is at time -

i am sure - this can be a new "standard" "must to have " in shool, in concern and so on. i will this bring in our concern too... loveley i will do this... i like FC concept.. ok .. simulation is not "my world" but this is a nice future, why not... and this can realtime show in business meetings how the "Project" will work . so i make a Future Request for "standalone Simulation".. for sending by email example to a business partner.. so the business partner can see what he/her get .. ( you know PowerPoint... in this can work to a Chart... and then it can be compiled to a Standalone.. likewise ..) ....
ok..

Best wishes!
Rudi
Last edited by Rudi on Mon May 19, 2014 8:27 pm, edited 2 times in total.

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

Re: DOCU to the Flowcode language

Postby Rudi » Mon May 19, 2014 8:19 pm

LeighM wrote:Hi Rudi,

I have attached a simple Flowcode program to show you how to use C within a Flowcode macro.
If you compile to C, you can view the resulting C code to confirm the interface.

Using C is documented, it’s just any internal functions that aren’t, as these may change.

Also, Jonny wrote a good article, probably more than you need, but it can be found here…
http://matrixmultimedia.com/blog/?p=146

Regards,
Leigh



Exactly Leigh!

You're the greatest! ..sorry .. after Benj ;-)...

;-)


This is one of a needle in a haystack!

Many many many thanks!

More I do not want that.

Here everything is explained simple and you can get started.
Exactly such examples must be shown in the help.
Everything else, the user must do it yourself.
That's normal.


Many many many thanks!

Exact the same way i make my
AT Command Stringlist from extern File!
This can be changed every Time ..if changed the AT Commands by a String Command ..
example
..
AT+COMMAND1 was changed in AT+COMMAND_ONE
so only a Text File must changed, not all in the FCFX..
and for Copy to a String Variable.. all is clear..

Same in Menu File for LCD Print in more as one Language.....
if language english.. then english file will loades "Welcome"..
if language german.. then german file will loades "Willkommen"
if france.. and so on..

only this was need will be load and Chip Space can be saved..
btw...

Best wishes!
Rudi
;-)

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

Re: DOCU to the Flowcode language

Postby Rudi » Tue May 20, 2014 12:06 am

DavidA wrote:Hello,

There is a 6.0.7 full release available go to Help >> Check for Updates to get the release.



:-( :-( :-(
1. This is no Release... this is a Patch..

that make my Professional to a

Home Version
-----------------------------

.

Re Activate again not bring back the Professional!

...

what do you think you actually doing?
:-(

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

Re: DOCU to the Flowcode language

Postby Rudi » Fri May 23, 2014 1:20 am

kersing wrote:
Rudi wrote:
Rudi wrote:That all stands in APP Note at Microchip..
that is a BASE Formula ...
and i am sure...


There are two formulas in Flowcode. One to set the baud rate based on the properties. This formula provides the same result as the one in the data sheet. The second set does not have the dsPIC33 and dsPIC24 fixes as you correctly found.

Rudi wrote:This Bug's never seen in V2 ..-> V3...-> V4...-> !V5....-> V6 ??


The bugs with the baud rate for UART_UpdateBaud are in V5 as well.

Attached is an update of PIC16BIT_CAL_UART.c that should fix your baud rate issues.


Hi Jac, ty again
Jac, this 16bit CAL you added, this is not the same in 6.0.7.0 and will fix the baud rate issues that i am found?
Yours is the newest, i am right?

i will update the 6.0.7.0 16bit Cal Uart with your, right?
i will rename the 6.0.7.0 cal as bak and yours as actually?

i will test this next time and will post the change to my founds..

Best Thank!
Rudi
;-)




//Hardware Baud update definitions
#ifndef MX_HARD_BAUD_CHANGE_DEFS
#define MX_HARD_BAUD_CHANGE_DEFS
#if defined(__dsPIC33E__) || defined(__dsPIC33F__) || defined(__PIC24E__) || defined(__PIC24F__) || defined(__PIC24H__)
#define MX_HARD_BAUD_1200 (((MX_CLK_SPEED / 1200) - 16) / 32)
#define MX_HARD_BAUD_2400 (((MX_CLK_SPEED / 2400) - 16) / 32)
#define MX_HARD_BAUD_4800 (((MX_CLK_SPEED / 4800) - 16) / 32)
#define MX_HARD_BAUD_9600 (((MX_CLK_SPEED / 9600) - 16) / 32)
#define MX_HARD_BAUD_19200 (((MX_CLK_SPEED / 19200) - 16) / 32)
#define MX_HARD_BAUD_38400 (((MX_CLK_SPEED / 38400) - 16) / 32)
#define MX_HARD_BAUD_57600 (((MX_CLK_SPEED / 57600) - 16) / 32)
#define MX_HARD_BAUD_115200 (((MX_CLK_SPEED / 115200) - 16) / 32)

#else
#define MX_HARD_BAUD_1200 (((MX_CLK_SPEED / 1200) - 16) / 64)
#define MX_HARD_BAUD_2400 (((MX_CLK_SPEED / 2400) - 16) / 64)
#define MX_HARD_BAUD_4800 (((MX_CLK_SPEED / 4800) - 16) / 64)
#define MX_HARD_BAUD_9600 (((MX_CLK_SPEED / 9600) - 16) / 64)
#define MX_HARD_BAUD_19200 (((MX_CLK_SPEED / 19200) - 16) / 64)
#define MX_HARD_BAUD_38400 (((MX_CLK_SPEED / 38400) - 16) / 64)
#define MX_HARD_BAUD_57600 (((MX_CLK_SPEED / 57600) - 16) / 64)
#define MX_HARD_BAUD_115200 (((MX_CLK_SPEED / 115200) - 16) / 64)
#endif
#endif


kersing
Valued Contributor
Valued Contributor
Posts: 1873
Joined: Wed Aug 27, 2008 10:31 pm
Location: Netherlands
Has thanked: 530 times
Been thanked: 1040 times
Contact:

Re: DOCU to the Flowcode language

Postby kersing » Fri May 23, 2014 11:12 am

Hi Rudi,

My file is an updated version of the 6.0.7.0 one, so it is newer and you need to replace the 6.0.7.0 one with my file to fix the baud rate issue.

Best regards,

Jac
These users thanked the author kersing for the post (total 2):
LeighM (Fri May 23, 2014 11:15 am) • Rudi (Fri May 23, 2014 12:13 pm)
Rating: 10.53%
 
“Integrity is doing the right thing, even when no one is watching.”

― C.S. Lewis

User avatar
LeighM
Matrix Staff
Posts: 1888
Joined: Tue Jan 17, 2012 10:07 am
Has thanked: 445 times
Been thanked: 640 times
Contact:

Re: DOCU to the Flowcode language

Postby LeighM » Fri May 23, 2014 11:17 am

btw. Jac, your update to the CAL is now in our repo, so will go out with the next release (should be early June)
Leigh
These users thanked the author LeighM for the post (total 3):
kersing (Fri May 23, 2014 11:21 am) • Rudi (Fri May 23, 2014 12:14 pm) • medelec35 (Fri May 23, 2014 4:03 pm)
Rating: 15.79%
 

User avatar
Rudi
Posts: 666
Joined: Mon Feb 10, 2014 4:59 am
Has thanked: 494 times
Been thanked: 188 times

Re: DOCU to the Flowcode language

Postby Rudi » Fri May 23, 2014 3:54 pm

LeighM wrote:btw. Jac, your update to the CAL is now in our repo, so will go out with the next release (should be early June)
Leigh


Hi Leigh,

is there a official List in found issues and gone issues or updated Icons..
i ask example:
Benj has make in Circular Buffer fine extra "FlushBuffer"

viewtopic.php?f=7&t=14616#p58468

at 27.03.2014 ;-).....this is not append in FC 6.0.7.0 ( 28.03.2014 ) so I ask do you make this not automatically allways refreshen in next Release ?

Because then it helps if all fine Tips and Infos in Forum allways list "Central" too ? :-)

The History of "refreshen" or updated or "workaround" or patches are not allways clear to have allways "all" up2date ..

perhaps in a own Thread?

I hope i have undestand declare fine in english.

Sorry for this .. this is usually not the right Folder for this thread.. but you have wrote here too ;-) ;-) ;-) ....

Best wishes!
Rudi
;-)

ps..
6.0.7.0 .. Released Patch delete / installs new!
So first Time the upated icon "CircularPuffer" wit nice Flush Function.. will be replaced by 6.0.7.0 with the "older" ICON from 6.0.7.0 ... ..and Flush Function will be get lost...

User avatar
LeighM
Matrix Staff
Posts: 1888
Joined: Tue Jan 17, 2012 10:07 am
Has thanked: 445 times
Been thanked: 640 times
Contact:

Re: DOCU to the Flowcode language

Postby LeighM » Fri May 23, 2014 4:20 pm

Hi Rudi
Looks like Ben's change went into our repository 5:30pm 27.03.2014,
so if you cannot see the change in your installation, it might have just missed the 6.0.7 build
(I which case you can update your local components directory with the newer version)
Best regards,
Leigh
These users thanked the author LeighM for the post:
Rudi (Fri May 23, 2014 4:31 pm)
Rating: 5.26%