The flag bits

[maciek]

Is there a way to make the flag bits(meaning on success or on error bits) start from c100 or c200 not the first available c-bit , I like c0 and so on for hmi and control stuff.

[RBPLC]

I assume you mean for commands such as Modbus read/writes. If so, you can assign success/error bits to whatever bit memory locations you want. If so desired you could add a memory block for only success/error bits.

[franji1]

Is there a way to make the flag bits(meaning on success or on error bits) start from c100 or c200 not the first available c-bit , I like c0 and so on for hmi and control stuff.

That's what the Element Picker is for.  In the Element Picker, hit C100 bit button in the picker (or just type C100), then hit Next Unused.

This works with any detent start address.  Say alarm bits start at C1000, enter C1000, or hit the button for C1000, then hit Next Unused.

[RBPLC]

Related to this topic, franji, can you guys modify the behavior (or provide an option) so that the element picker or create nickname dialog box will recognize nicknamed memory as "used". Currently nicknamed memory that is not used in the program is seen as available to the picker and nickname dialogue box. This is aggravating because if I've nicknamed a bunch of memory elements that I intend to use but haven't written them into the program yet, when the picker comes up with these locations shown as available (which technically they are) however, I've already "reserved" them for later use. They're shown as available and the create element dialogue catches that that memory already has an assigned nickname and the "find next unused" seems to then skip over nicknamed but unused memory to find the next available. There's been similar conversation on here about ranged indirect variables (which is easier to understand why they're seen as available, and harder to determine that they're used) but it would be nice to be able to "use" nicknamed variables that weren't currently used in the program. Is this an option that I'm missing?

Edit: Nicknames are shown in the top of the element picker dialogue box but it would be nice to see them X'd out in the bottom memory picker section as well. 

[franji1]

Related to this topic, franji, can you guys modify the behavior (or provide an option) so that the element picker or create nickname dialog box will recognize nicknamed memory as "used". Currently nicknamed memory that is not used in the program is seen as available to the picker and nickname dialogue box. This is aggravating because if I've nicknamed a bunch of memory elements that I intend to use but haven't written them into the program yet, when the picker comes up with these locations shown as available (which technically they are) however, I've already "reserved" them for later use. They're shown as available and the create element dialogue catches that that memory already has an assigned nickname and the "find next unused" seems to then skip over nicknamed but unused memory to find the next available. There's been similar conversation on here about ranged indirect variables (which is easier to understand why they're seen as available, and harder to determine that they're used) but it would be nice to be able to "use" nicknamed variables that weren't currently used in the program. Is this an option that I'm missing?

Edit: Nicknames are shown in the top of the element picker dialogue box but it would be nice to see them X'd out in the bottom memory picker section as well.

These are all good ideas.  I think Ranges are already flagged in the Element Buttons in the Element Picker, but I don't think "Next Unused" behavior is there like you pointed out.   We might be able to squeeze them in this next release (no promises).

[ATU]

Maybe instead of X them out in the picker, perhaps color the block yellow to indicate that they are named but not used? Just a thought.

[RBPLC]

Differentiating them is a good idea. X's are used, - are ranged and maybe O for nicknamed? Coloring works as well.