Matrix user forums

Sieht aus wie Sie das Problem sortiert haben dann? Gute.

Flowcode v4 leider fehlen ein paar Warnungen in diesem Bereich. Wir haben viele dieser Fragen in Flowcode v5 ​​fest mit einem strengeren Parser. Dies sollte Flagge up Fehler wie diese in die Zukunft.

Jonny

Hallo. Wenn ich das Lesen dieses Recht bin, dann funktioniert das nicht: byte value; EEprom_Write(value); Aber das bedeutet: int value; EEprom_Write(value); Das ist sehr seltsam, wie der C-Compiler, um den Zielparameter, der ein 'int' gegossen sollten. Was ist es, nicht gut funktioniert, da beide so...

Sorry, habe ich kein Verständnis für die (Google übersetzt) ​​Frage. Es ist kein Problem, ein Byte, um diese Funktion zu senden - es wird 16 Bit auf 16-Bit-PIC schreiben, mit den Top 8 Bits Nullen. Ich glaube nicht, dass es einen Anruf zu einem einzelnen 8-Bit-Wert auf einem pic-16 schreiben. Ich ho...

Hallo. Wenn das Ziel ist ein 8-bit-PIC dann den eeprom schreiben schreibt 8-Bit-Bytes. Wenn das Ziel ist ein 16-Bit-Bild wird es 16-Bit-Wörter zu schreiben.

Cheers,

Jonny

Yes, sorry, 128. its probably cos the 7 is next to the 8 on my keyboard.

Hi Echase. Firstly, yes, no problems with int arrays, though you may be limited by whatever chip you are using (hardware is way over my head though ion a pic8 this will be 127 element array). Secondly, is what you are doing an averaging program? If so you can save any large calculations by using a m...

No problems. As far as a technical manual goes I don't think we have any plans for such at the moment but it would certainly be nice to have - I'm developing Flowcode v5 at the moment and it would certainly be helpful for me!

Good luck with your program,

Jonny

Hi Mark. Sorry, Ive just re-read your post - still bleary eyed this morning. Another possibility if you are struggling for size (using an int array) and your 'X' value is always the same is to store a value of 0-2 in a byte array then do: X = (array[index] - 1) * speed Where 'array' is a byte array ...

Hi Mark. You should be able to create an array of integers in any Flowcode version by selecting the integer radio icon and typing in the size of the array you want: vars.png You will not be able to change existing variables that are arrays from byte to int, but should be able to create one from scra...

Hi Martin. If it helps, this wont be an issue in v5 due to greater signed/unsigned control but for now a small mod to the program would fix this. We suspect the issue is that the random() call on the PC is being pushed into a signed 32-bit value. This is then cast to a float (as all v4 simulated val...

OK. Hopefully we could work it so it worked fine for both. I cant guarantee this will make it in at all, but we can only do our best.

Hi Martin. Do yo mean copy from one macro to another internal to a single flowchart, or between two open copies of Flowcode? (Or both?) We are currently trying to make transferring of calculations and other icons (as what works for one should work for them all) easier and to have an 'auto-create' fe...

OK, sorry I couldn't be more help. It sounds like you are doing pretty much the only thing you can do at present so I'm afraid you might have to make do with that at present. It would be nice to be able to provide a formula based on time and Flowcode variables that would simulate output during simul...

Yeah, this is true. In stages: (value < 0): returns 1 if value -ve, 0 if it is not -(value < 0): This becomes -1 if -ve, 0 if not 1 | -(value < 0): This unconditionally sets the bottom bit, so is -1 if -ve, 1 if not If we then multiply this by our original value, we will 'flip' the sign of -ve value...

Glad the article was a help to you! Yes, keep us posted with the projects you are on, we are always interested to hear about these things!

Hi there. In Flowcode v5 we are hoping to rework the components to simplify mods and get a tighter working between simulation and execution. For the user to be able to programatically tweak the inputs during simulation is a nice idea, I think. Until then (and even then) I would recommend trying to a...

PS:

'Whereas result = value * (1 | -(value < 0)) is presumably C code.'

This expression will work fine in both C and Flowcode expressions.

Hi. (NOT value) + 1 is the same as -value, so thats all fine. You would have to look at the ASM as to which is more efficient. Branches in the code tend to be the main issue on pipelined processors, though I haven't much HW or low level knowledge of the devices you are using. On many platforms, (val...

Hi there. In Flowcode v5 we have plans to support unsigned 16 and 32 bit values. It would also be nice to have abs() and sgn() functions and I'll put this on the suggestion list. Until then, the single line: result = value * (1 | -(value < 0)) Will do the job of abs() in a single calculation line. I...

Hello. In v5 there will be much more checking and association with icons both before and during code generation, so even if problems like this do slip through, it should be easy enough to find them as Flowcode will (hopefully) know which icon(s) caused the error. Until then yeah, I think its a good ...

Hi there. We have a list of features that we are working towards but we occasionally tweak this as new possibilities become available. My worry would be if we posted a list it would be taken as 'definitive' and if features on there didn't make the final version there could be complaints. Anyway, per...

Hi there. I'll be implementing this, and it is something we have given a bit of thought to. Yes, option 3 would certainly be my preference, if only one was chosen. What I would like to do is have an 'Initialise to...' field in the variable manager that it should be good practice to use. This would e...

Happens to me all the time... Not the kind of thing you do twice though!

Good luck with your program, cellular automations are always really nice when theyre done.

Hi there. I have had a look at your program - is it intentional that the arrays are arrays of bytes? (Sorry if this has been discussed further up the post) This might be your problem, as the bottom byte will be F8 of 1FF8. Try changing game_of_life_prev[] to an array of ints (and probably _next[] to...

Hi Niro. Currently in Flowcode v4 there is an issue where local variables on the right of an '=' do not display as C-code variables properly. This is purely a visual issue to do with the tooltips and shouldn't affect the C compilation or how your program works. If you are unsure this is the case, co...