Organize writable members when editing Lookout PLC connections

Can you hide native writable members when editing PLC connections in Lookout Direct?

No. No filter box, hide control, or resize handle appears in the Lookout Direct documentation, so the native members stay in the list; the working fix is naming, and prefixing your database aliases with A puts their rows at the top of the writable-member list.

The list you are fighting lives in the Edit Connections dialog box. The Using LookoutDirect documentation describes direct connections as ones made in that dialog and fixed once made, so this is an editor for mappings, not a view you can tune.

The native rows are not clutter you added. They belong to the object class, and the documentation for editing object databases places the native database for each class at the end of that class's definition, in the online help and the Object Reference Manual. That is where to look up any native member whose purpose you cannot place.

If a future edition ships a member-list filter, its release notes will name it. The edition notes checked for this article announce new objects and a new Historical Data Viewer, which is exactly the kind of entry a member-list control would look like. Until your installed edition's notes carry one, plan around the list as it ships.

What does the writable-member list show?

Every writable member of the object you connected to: the class's native members and your aliases, interleaved in name order, which is why a handful of aliases vanish inside a long list.

The rows come from two places. Native members ship with the object class, documented per class as the previous section says. Aliases come from your project: each row of the text data member database carries exactly three fields, Alias, Member and Description, per the Lookout Direct developer's manual. Alias is the name you pick. Member is the member it references. Description is free space, and it is where the mapped PLC point belongs.

Each symptom points at one cause:

• The write points sit screens down the list. Native members and aliases share one name-ordered list, so an alias named TempSP1 sorts in among the T names. The fix is the A prefix, next section.
• Two rows carry similar names. One is a native member, one is your alias; they are separate rows with separate references. Compare Member and Description before you write.
• The list outruns the dialog and nothing searches it. The documented dialog has no type-to-filter box. Shrink the scan: prefix the write set and keep that set small.
• A write lands on a value the PLC did not expect. The wrong row was selected. Stop writing, restore the known-good project file, and recheck the mapping; the repair path matches the one for an imported HMI tag that ignores PLC register writes.

How do you keep your aliases at the top of the list?

Prefix every alias you write through with a single A character; one character is the whole change, and it lifts each row above every unprefixed name in the list.

1. Save the project first, or read it from the panel before editing, so you can prove what the project looked like before you touched a connection.
2. Open the text data member database and list the aliases your operators write through. Keep the set to the written points only.
3. Rename each one so it starts with A and keeps a tail that means something on your floor: A_TempSP1, A_LineSpeed and A_BatchQty1 show the pattern.
4. Type the mapped PLC point into each alias's Description field, exactly as your mapping sheet prints the register, address or tag.
5. Touch nothing else: no native members, no PLC addresses, no mappings. Sort order is the only thing changing.
6. Reopen the Edit Connections dialog and confirm the A rows sit above every unprefixed row. If they do not, stop and report it; the last section covers that.

How do you check a member's target before you write to it?

Read the row, not the name: Alias is only the display name, Member carries the reference the write follows, and Description should hold the PLC point you mapped, so a row passes when Member and Description match the mapping sheet, whatever its name looks like.

Run the checks in this order:

1. Field check. Open the alias in the database and read Member and Description against the mapping sheet. A familiar name is not a match; matching fields are.
2. Native check. For a native member you cannot place, look it up in the class documentation before writing, as described in the second section.
3. Link check. After the connection edit, verify the link with a PLC heartbeat counter before you trust any write through it.
4. First write. Make one controlled write to a low-stakes point and read the value back at the PLC. A match finishes the edit; a mismatch stops it.

One safety rule for this job: if any write reaches a value the process did not expect, stop writing and restore the known-good project file before anyone edits again. A rename cannot push a write to a new register; a wrong row selection can, and that is the fault this check exists for.

What does the rename look like on an example project?

On an example packaging-line panel whose one serial connection maps 46 members, with operators writing 9 of them, the A prefix cuts the rows a search can cover from 46 to 9: 37 rows fewer, about 80% of the list.

Scenario: a packaging-line panel holds one serial connection to the PLC. The connection maps 46 members. Operators write 9: three temperature setpoints, a line speed, four batch counts, and a reject threshold. Before the rename, the aliases carry plain names and interleave with the 37 native members in name order: BatchQty1 sits in the B names, TempSP3 in the T names, and one search can touch all 46 rows.

After the rename:

The arithmetic: 46 members minus 9 aliases leaves 37 native rows, and 37 / 46 = 0.80, so the worst-case scan drops 80%. Call it 1 second to scan a row: a search falls from 46 seconds to 9. For screen fit, a 1920 x 1080 plant monitor at roughly 36 pixels per text row fits 1080 / 36 = 30 rows at once, so all nine A rows stay in view without scrolling. The same naming rule holds for any list an operator scans on a shop-floor screen: the rows that matter go to the top by name, not by scrolling.

Recommendation: Prefix every alias an operator writes through with A, one alias per written point, and put the PLC target in each Description field. Do the rename in a scheduled edit, not mid-shift, and verify the first write against the PLC value before production resumes. Check the release notes of your installed edition for a member-list filter; if one ever ships, the prefix simply becomes a second line of defense.

What should you never rename to shorten the list?

The A prefix belongs only to the aliases you created, because they are rows in your own database; native members belong to the object class definition, and a PLC address or mapping never changes to shorten a list.

An alias rename touches one display name. A mapping edit touches a write path. Keep the two apart and the cosmetic fix stays cosmetic.

The prefix orders rows; it grants and blocks nothing. A prefixed member writes exactly as it did before, so write protection stays where it lives, in the controller program: interlocks, write-protect bits, and access limits on the points that can stop or damage the process.

Before renaming an alias, search the project for other uses of the name. A connection or database row that points at the old name points at a name that no longer exists after the rename, and one tidy list then hides a broken reference somewhere else.

When do you stop renaming and report the dialog?

Stop when the prefixed rows refuse to sort to the top, when a write reaches an unexpected value, or when the dialog renders too small to check a row; report the product version, the object class, the member count, and a numbered reproduction of what you did.

The first case is a version difference: check the release notes for your installed edition, because that is where a member-list filter would be named if one shipped. The second is the restore-and-recheck case above, and it outranks any tidying. The third is usually the host PC, because Windows font and display scaling decide how much of any dialog fits; there is a fix for HMI dialogs clipped by legacy Windows fonts, and it applies before any rename.

While the request sits with the vendor, the prefixed aliases keep the dialog workable. Nothing in this fix needs a hidden setting: the prefix is a name in your own database, and the sorting it relies on is the order the list already shows.

Questions