Another Pinlist problem - Contact counts aren't working

[drathak]

Ok.  So in trying to set up some complex relays (SEL power system relays) I have created the following blocks:

   VCR1_SELPS - power supply symbol (parent)
   VCR24_SELINPT - Digital input (child)

   VCR24_SELOUT - Digital Output. Maybe be NO or NC depending on programming (child)

For the most part my pinlists only have one NO contact (the alarm contact)  The rest are type four denoted as 4IN, 4OUT, 4CURR (current inputs) and 4POT (potential inputs).  I have the PINLIST_TYPE attribute set in the children components to match the above, and it works to filter the list of available pins for the cildren.  Nice.

However, after I insert one of the children, the second one triggers a warning that I have exceeded the number of available contacts.  (See attached image.)  It's like ACADE isn't recognizing the type 4 entries in the pinlist for this particular check.  Any ideas?

At firstthe CONTACT attribute for the children defaulted to NO.  So I have changed them to match the type they are, but that doesn't seem to help.  I'd like to not have to
"Ignore" a warning.  That makes some people kinda nervy.

[davidhall]

Can you post the 3 blks? Maybe it's a DB entry thing

[drathak]

The drawings and the pinlist table are attached.  Probably crossed an "I" or dotted a "T" somewhere.

[drathak]

Only three attachments allowed.

Well, won't let me attache an MDB.  Exported pinlist data to XLS for this.

[davidhall]

which SEL were you inserting?  I was trying to read the pinlist, making sure you had commas and semicolons where necessary.  They all look correct, so I wanted to try and make it crash here

[davidhall]

just a thought....is there a character limit on pinlist?

[davidhall]

OK, i got the answer, but Im not sure how to fix it w/o the dialog box.  In the parent, under NO/NC setup, change all the 0's to blanks for the 4 types

[drathak]

Yeah, I did that but I don't want to do that (or have to remember to do that) every time I use one of these.  There should be a way to set that in the parent block shouldn't there?

[davidhall]

i would think so.......

[testsubject]

A quick look in the database shows this information is passed through from the database when a catalog number is selected but I am unsure of how to reference a Type 4 contact...

[drathak]

Right.  It is almost as if it isn't seeing them for the "number of contact" checks, but does for the pinlist filtering.  (See attached.)

I guess for now I'll have to have people ignore it.  I need to try adding all of the inputs and see what happens then...

[davidhall]

to ref a type FOUR, its just 4,pinnumber followed by a ;

[davidhall]

something I didn't try yet was changing the 4curr to just a 4......

[davidhall]

ok, I changed the 4CURR, 4POT, 4IN AND 4OUT TO JUST 4 and it worked w/o the error.  I also edited the in block, pinlist att to just a 4 as well

[drathak]

I started that way, but all the examples I saw had 4something.  In the help file it says:

You can set up subcategories of type 4 pin combinations so that some apply to specific contact types and other pin combinations to other contact types. Encode the Pin List entries with a "4" plus a character to provide further filtering of what contacts are available for a given child contact. At the contact end, an attribute PINLIST_TYPE (or Xdata of the same name) must carry a value of "4" plus a character to match up with the coding in the pin list string.

That's why I split them up into 4IN, 4OUT, etc.  With just a "4" they all show up in the pinlist no matter which type I'm looking for.

[davidhall]

Im really reaching here..... In the help file it said 4 plus a character (singular)  could that be it?

[drathak]

---

@davidhall wrote:

ok, I changed the 4CURR, 4POT, 4IN AND 4OUT TO JUST 4 and it worked w/o the error.  I also edited the in block, pinlist att to just a 4 as well

---

Hmm.... I had it that way yesterday. Do you see all the type fours in the box where you select the pins to use?  Maybe I was hoping for too much when I thought I could filter by type.

[davidhall]

That appears to be it.....

[davidhall]

I changed them all to a 4 plus 1 character, I or O for the input and output.  It worked, filtered all the extra out.

[davidhall]

AND as a bonus, it removed all the 0's from the NO/NC setup box