Flowcode Support Board

Hi,
I was not happy trying to find working examples this weekend. I could not get the HDMI output to work on the Raspberry pi so did a google search for an example. I am also having problems which I might be fighting a losing battle with the TCP_IP_Pi.
I found this https://www.flowcode.co.uk/wiki/index.p ... cal_Color) so far so good, when I tried to download it (W11 / Chrome) I got a load text. I saved it as Martin pointed out in a different post and it opened (FC10) but no Raspberry Pi. It was for an ST32F746Discovery??
The example had a lot of stuff on touch which the HDMI screen on a Pi would not have as far as I know, my TV hasn't. There were over 50 macro's which in my opinion is not a good example, I should think most would prefer nice simple ones that are easy to follow.
When I downloaded it on W7 / Chrome it downloaded as a file but when opened (FC10) it did not have any GLCD and looking at the build it is for a PIC 16F1937. It also had TCP_Base which is not the same as the TCP_IP_Pi at all.
Also when looking for help from the project for TCP_IP_Pi it takes me to the same page but the project is no use?

Not sure what has been going on with all this.

Regards,
Bob

I suspect you are looking at component source, not example application.
I might have time later in the week to write an HDMI example, unless anyone else gets there first

Hi,
I think it was an example, what did really puzzle me was downloading on 2 different PC's / OS and got 2 totally different things.
I think one of the problems I have with FC is that it is so multi platform that it is not possible to have an example for each device.
I wonder if there should be a separate downloads section (or folder with examples created for the toolkit you have) when you install it.
If it were a downloads section it could be toolkit specific?
Regards what I assume was an example above, 50 macro's is way too much. If it needs that many to show how a command works maybe the command is way too complex?

Regards,
Bob

Hi Bob

I'm not really sure what you downloaded. I followed your link which took me to the RPI HDMI component page which doesn't (yet) have any examples. However at the very bottom of the page there are two links to the source codes, the behind the scenes working of the components.

Maybe you grabbed one of them?

When I'm next at hardware I can probably have a look at HDMI on the RPi.

Regards

EDIT
PS
Most examples are there to show the component in use and as FC to a great extent isn't target specific, the example is normally enough of a guide to get you going, well that's assuming there is an example

Hi,
That is what I did I think which is why I think there should be a separate downloads section for examples.

It is still puzzling how the same file was totally different with 2 different OS though?

Regards,
Bob

Hi

No idea about that one..... was this after you had your beers...

As for the touch screen options, there are many RPi displays that incorporate touch, some very competitively priced and I'm almost tempted...

Regards

As for the touch screen options, there are many RPi displays that incorporate touch,

On HDMI??

And no, I had a very sensible weekend, I was trying to get the ping program working. Wish I had more beers now

Bob

Hi

Depending on model, the touchscreen is via USB or SPI and the Pi can be mounted on the rear.

Kind of thinking of maybe using it as a home controller of sorts, but I don't really care enough about the temperature in each room or lighting when I'm not actually in the room

Regards

Hi LeighM

I might have time later in the week to write an HDMI example, unless anyone else gets there first

Any chance you will have time for a Pi HDMI example sometime?

Regards,
Bob

Hi Bob,
I did have a quick look.
The Raspberry Pi HDMI component did work on hardware target, but didn't seem to simulate in Flowcode.
I used a simple Initialise and Hello World print.

As I recall, the component was originally written and tested with a Raspberry pi touch screen, hence the reference to Touch macros.
However, the linux touch drivers work via the mouse interface, so it should work equally well with a mouse.
Hope that helps.