Outstanding Update for Do-more!

[Mike Nash]

Wow! (Now I get to see if it will work under Win XP too.)

My current project may get to try out some of these new features!

Download complete, entering explore mode...

[franji1]

(Now I get to see if it will work under Win XP too.)

You realize that we want to add more and more features that require more and more bandwidth of your PC.

Sometimes, you just need to let go and move on.   

[Mike Nash]

(Now I get to see if it will work under Win XP too.)

You realize that we want to add more and more features that require more and more bandwidth of your PC.

Sometimes, you just need to let go and move on.   

I know, but... ports, old hardware/software to be supported, trackpad that doesn't autonomously reprogram PLCs by itself, fondness for familiarity, non-transferable licenses, etc.

Not to mention operating systems changing overnight (thanks to updates) and breaking stuff. And if you don't let it, you can no longer access stuff. Slippery slope.

[Mike Nash]

Anyway, it at least looks to be working in XP with a BRX.

About the ASCII Default Display Format in the User Data Type - I can select this for any of the word or byte data types - but how do I go about getting a string into it? I probably ought to know this already, but it's less painful to just ask. I do realize it is not really a string, but it looks like it could be useful for naming an array entry (Recipe7.Name = "Fried Chicken Suckers").

[franji1]

but it looks like it could be useful for naming an array entry (Recipe7.Name = "Fried Chicken Suckers").

Sadly, no.  A STRING is a structure, along with User Data Types.  But Do-more does not support nested structures.

What you are seeing is a way to format a numeric DWORD or WORD or BYTE's DEFAULT DISPLAY format.  Normally, it's 2's complement decimal integer.  But you may want to look at in HEXADECIMAL or even OCTAL.  We also have ASCII/SWAPPED ASCII.  So, if you had a DWORD that is 4 BYTEs long, you could look at it as ASCII if that came from the source that way (think of a Modbus Holding Register that contained text, e.g. 0x44434241 would be "ABCD" ASCII or "DCBA" SWAPPED ASCII (I may have those backwards)).

I guess you could technically stick a bunch of DWORD members in a structure to make up a name (e.g. 4 DWORDs called .Name1, .Name2, .Name3, .Name4 for up to 16 character name), but that really isn't a "string" or even particularly useful.

One way around this would be to have two data-blocks - a block called RecipeName, and another block called Recipe, and the ID/Index of the two blocks correspond to each other, so RecipeName7 would be "Fried Chicken Suckers", but Recipe7.CookTime Recipe7.CookTemp would be two fields in the Recipe7 structure of the Recipe block.

[Mike Nash]

I figured the string was a no go. I did get there using .NameA .NameB, etc.

I figured wrongly I couldn't use numbers such as .Name1 - glad to see I was wrong on that.

I thought the COPY was going to be easy with the "Count" but it wanted to put the 4 digit values into Recipe1.NameA, Recipe2.NameA rather than incrementing .NameA to .NameB, etc. Makes sense, but of course I am always looking for the non-sense solutions. But it does work as long as I type them all in to the dialog box.

Auto select for arrayed data always makes it Recipe0-31 so it winds up easier to just type it out.

But STRGETB SS0 to D0 length 16, then COPY those D's to .Name1, .Name2 does get it into the "recipe". So far so good!

[Controls Guy]

Sometimes, you just need to let go and move on.   

Maybe somebody can do an XP skin for WinX!

Just kidding -- when I can no longer use W7 it'll be Mac or Linux or BSD on bare metal and Windows only in VM's.  No Microshaft past 7 (on bare metal) for this guy.

[franji1]

But STRGETB SS0 to D0 length 16, then COPY those D's to .Name1, .Name2 does get it into the "recipe". So far so good!

That is definitely the way to do it, if you like that sort of thing.

I like the corresponding data-block idea myself (i.e. RecipeName String data block and the corresponding Recipe RecipeStruct UDT data block).

[Controls Guy]

I know, but... ports, old hardware/software to be supported, trackpad that doesn't autonomously reprogram PLCs by itself, fondness for familiarity, non-transferable licenses, etc.

Not to mention operating systems changing overnight (thanks to updates) and breaking stuff. And if you don't let it, you can no longer access stuff. Slippery slope.

Virtual machines are your friend, my brother!  VMWare can even virtualize a machine in place (use their Converter program) and in my experience AB and GE licenses survive it just fine.  Siemens licenses you can readily move around so you can move it to a thumb drive while doing the conversion.

Virtual PC is probably a tiny bit simpler, but not quite as powerful as VMware.  There's Virtual Box too, and tons of others.

[Controls Guy]

But Do-more does not support nested structures.

Well, time to get on that!  It's important!   

Thanks for the update BTW -- going through the PDF now.

[Evilbeard]

It's like having an extra Holiday in September!!

[Controls Guy]

From Updates.PDF:

COPY – Copy Data lets you perform most of the data assignment operations in one compact
instruction.  It merges the functionality of MOVE, MOVER, and SETNUMR for numeric data;
SET/RST, SETR/RSTR for bit data; copying entire structures and ranges of structures; and
moving Strings of different maximum lengths between each other, for example moving SS0 to
SL5.

Seems like it supersedes MAPIO as well.

[franji1]

Seems like it supersedes MAPIO as well.

Yes.  MAPIO is similar to COPY in that it just wraps other core instructions.  MAPIO was JUST for BITs, since Bit Mapping I/O is a "thing".

[Mike Nash]

MAPIO was JUST for BITs, since Bit Mapping I/O is a "thing".

Not in my world! But I do see this mentioned in the help.

When used as intended

[BobO]

MAPIO doesn't provide anything you couldn't already do, but it does provide a nicely compact display. I still like using it for the application clarity.