Re:pncconf - feature requests

Yes,I think lowercase would be most consistent with hostmot2 pin names, I think.
self discovery of course would be best., but in the mean time I will just hard code the pin names for mode 0.
I'm, not sure what boards are most popular. After i code the framework adding cards should be easier.
As long as the pin names for each mode on the card don't change this will work ok.

cmorley wrote:

I will just hard code the pin names for mode 0.

Does it make more sense to hard-code the pins for mode 2?

If there is no disadvantage to mode 2 then yes.
I see mode ADDS not replaces.
Why is there a mode 2 then?

Modes may change/replace pins, (they just dont happen to on the 7I76 but do on the 7i69, 7I73 and others)

The reason that you do not just always have the maximum amount of data (like mode 2 on the 7I76)
is that it may be too much data for a given servo thread period, that is if you need a fast servo thread you may need to reduce unwanted data transfers (for example mode 2 takes an average of 24 uSec longer than mode 0 as it means the 7I76 echos 48 more bits)

We dont want to unnecessarily limit thread rates if we dont have to, especially with data that may not be used.

That makes sense even to me.

John

yes I suspected this was going to be the answer.
since mode 1 or 2 doesn't add anything that PNCconf configures then mode 0 it is.
It would be trivial for the user to change modes and add the HAL commands for the pins.