Hi Jordi, thanks, very intersting information. I wondered why some recipes worked, others not. Now, I know. -Recipes which are working: if they are known and inserted into recipes by hand, as written on page 44. -Recipes "not exist" after power OFF/ON: recipes which are created in runtime with variable name. Recipes that can't be inserted by hand (as on page 44) because they are unkown. They are working as long as power is on, but after power off, they are lost (even they still exist on flash). -this sounds like the RecipeManager is loosing recipe definitions. I think, recipe manager fills the table with created recipes as shown below, the yellow marked recipes. After power OFF all the entries are lost. The big question is, how to help recipemanager to remember the list? Because the recipe names are individual and I don't know them before. Do you have any hint? By the way, the next chapter "USB" is very interesting for me, too:) Thanks a lot for that edited 14:20pm Did a test: With 'GetRecipeNames' I check what recipes are created and known. The result is: These recipes are knwon with name. At this stage, the recipes can be used without issues. Now, a restart (no power OFF/ON) of ctrlX: Recipe "test6" is lost Taking a look on ctrlX flash where recipes are located many more are there (all with extension ".ProgrammDaten.prg": When opening the file where I list the programs, to sort a programnumber to a programname, a list used in my Visu, the file has following entries: Complete different to what can be read out with recipe manager and GetRecipeNames. A complete mismatch. The recipe definition looks that way: The recipe "ProgrammDaten" is working because it is fix in definition. But all others are unknown and created during runtime. My opinion, there is a big bug with recipe manager. Recipe manager must not loose recipes! Otherwise this function is nonsense! And this bug was not with v1.20 and before. I use it that way since more than half a year without that issue.
... View more
