can you guys help me make a flow chart of my VI? Yes, in generel we can do this! Why should we here? For this special case we cannot help you since you forgot to attach a subVI "converter.vi". (Next time please use ZIP to put all needed files into just one download!) General comments on your VI: - Why do you have 30+ cases in your case structure - and the only difference is a simple numeric constant? Why do you duplicate the code in your VI so many times? Use either a ring for the selection of the numeric constant - or an array lookup table! - Why do you need to convert hours, mins and seconds all on their own? Why don't you create an array of LED clusters? - Why do you use such an "interesting" background color for (each part) your block diagram? It's hurting the eye when I have to look at a light-purple screen!

[Stem162]

Thankyou in advance

[GerdW]

Hi Stem,

can you guys help me make a flow chart of my VI?

Yes, in generel we can do this!

Why should we here?

For this special case we cannot help you since you forgot to attach a subVI "converter.vi". (Next time please use ZIP to put all needed files into just one download!)

General comments on your VI:

- Why do you have 30+ cases in your case structure - and the only difference is a simple numeric constant? Why do you duplicate the code in your VI so many times? Use either a ring for the selection of the numeric constant - or an array lookup table!

- Why do you need to convert hours, mins and seconds all on their own? Why don't you create an array of LED clusters?

- Why do you use such an "interesting" background color for (each part) your block diagram? It's hurting the eye when I have to look at a light-purple screen!

[Stem162]

We are making an international clock, the thing is i want to have a flowchart  of my vi. The converter sub vi is now included in the zip file. Thankyou! 

[GerdW]

Hi Stem,

The converter sub vi is now included in the zip file.

Yes, thanks.

But you didn't do any of my previous suggestions (including changing that ugly background color.)

the thing is i want to have a flowchart  of my vi.

Then you need to draw it. Use a tool of your choice!

You need sybols for a loop, a comparison, and a data conversion. That's it!

(As it's your VI you surely know how the DATAFLOW is working in the VI…)

[Stem162]

but im having a hard time make a flowchart of my vi i dont know what to do and where to start 😞 

[crossrulz]

Just break down each section of your code and make a block for it on your flow chart.  Sections I see are getting the current time, adjusting the time, getting hours, minutes and seconds, and finally configure the display.  It would be a lot simpler if you followed GerdW's advice in simplifying your code first.

[billko]

---

@crossrulz wrote:

Just break down each section of your code and make a block for it on your flow chart.  Sections I see are getting the current time, adjusting the time, getting hours, minutes and seconds, and finally configure the display.  It would be a lot simpler if you followed GerdW's advice in simplifying your code first.

---

Isn't this kind of backwards?  Kind of like creating a mechanical drawing from the part?

[Yamaeda]

WhiteStarUML can e.g. be used to draw Flow charts, if that's the question.

/Y

[crossrulz]

---

@billko wrote:

---

@crossrulz wrote:

Just break down each section of your code and make a block for it on your flow chart.  Sections I see are getting the current time, adjusting the time, getting hours, minutes and seconds, and finally configure the display.  It would be a lot simpler if you followed GerdW's advice in simplifying your code first.

---

Isn't this kind of backwards?  Kind of like creating a mechanical drawing from the part?

---

Yes it is.  But that is the situation the OP is in.

But after some sleep, the better advice would be to draw up a flow chart to show what the program SHOULD do and then update the program based on that.

[Bob_Schor]

A Corollary to the often ignored Programming Maxim of "Write the Documentation First" is "Develop a FlowChart (or at least a firm idea in your mind of how the Program should flow) First".

Bob Schor