Quote:
|
Originally Posted by Winged Globe
Wait... what?? Looking at the example for FRC controllers, it just looks like all the code thrown into a flow-chart interface (a graphical tool used in real computer science classes I've seen to teach the core logic/reasoning/organizing ANYONE needs in order to program). This isn't just script code like "turn left for blah seconds"--there seems to be a direct correlation between what the flow-chart displays and what the actual code will be (if count Bit 7 ON yes--> SET rc_dig_out16 ON, etc. etc.). It looks like you can comment directly into the flow-chart boxes to describe what is going on, too.
This means that the only difference between the flow-chart and actual code may be purely formating in nature, in which case, how does this have no correlation to the real world? Heck, it doesn't even look like pseudo-code; you have to use real variable names, real subroutine names, real function calls! And once a new programmer feels comfortable with the logic, *CLICK* and they see the real code! And it looks almost exactly like what they did with the flow-chart! "Wow! Maybe this programming stuff isn't so bad! I can do this..."
I can understand the nerd attachment to CLI's and aversion of all things graphical, but if the examples show the actual product delivered (and if FIRST/Kevin Watson brings the scripts back in addition to this interface, by all means, but that isn't this specific program), this is the most code-like graphical interface I've seen. I'm almost afraid that some newbie programmers will still be puzzled by it, as it isn't as graphical and perhaps as intuitive as Lego's interface or even Robolab. I really don't see what the big pout is all about. This seems to head in the right direction to get new programmers into the fold, while allowing novice programmers to transition and advanced programmers to keep hacking at their leisure.
|
'Winged Globe' has made a discovery about CoreChart and its direct correlation to assembler code. He is one of the few programmers who actually understands this. Most assume that because it is a flowchart program then it must be embedded code. CoreChart does NOT sacrifice any flexibility or access in programming at all but only makes the SAME programming graphical to avoid syntax errors.
The result is a Graphical Assembler which is used for Professional programming while being much easier to learn and start. Here at eLabtronics CoreChart has been used to create an intercooler spray controller program which predicts if the intercooler on a turbo engine will overheat and sprays water to stop this from happening. The real time system has 1/10,000 second cycle speed and is able to read 2 thermistors, 2 pots and 1 duty cyle signal from the injectors ( to 1% ) on a PIC16F84 running at 4MHz. Audizone in USA has given rave reviews on this product.
Similar products include a 29 unit array of DC-DC converters programmed in CoreChart for solar energy conversion used in the World Solar race. Thousands of students in High School are learning to use CoreChart. Some have gone on to do industry projects programmed in CoreChart sponsored by electronics companies.
We are currently working with some FIRST robotics teams mentor ( electronics company and college students ) to use CoreChart. We hope to continue with some of these FIRST robotics teams on CoreChart industry projects. The rational behind this is to enhance the employability of the FIRST robotics students.
Quote from an engineer at City University in London, England:
"There is a good feeling that embedded and robotics projects are
re-kindling students' interests. However, Assembly and C is quite a
challenge - even for professionals.
This is why I think Core Chart will succeed - its intuitive, simple to
understand whilst powerful as it is a full Assembler and affordable."
CoreChart is Assembler with graphical access. Most programmers do not look at CoreChart as closely as 'Winged Globe' and unfortunately they have assumed that CoreChart is another 'scripting' tool.