The trouble I’m encountering is when I attempt to re-probe after I’ve already used the motion controller object to probe before. If I unplug, say, the last axis, the axis count stays the same, even though the node count goes down by 1.
Internal stuff to help us keep track of how the above relate.
Node Name
Node VendorId
Node ProductCode
Node Revision
Node Serial Number
Node Station Alias
Some IO stuff which shouldn’t be relied on until the network is fully started.
The probe method is intended to get details about what is on the network so we can generate an ENI file. It is also useful to check expected Node Count with actual Node Count. If they are different, you wouldn’t expect Start to work.
We assume that you might create phantom axes. We aren’t going to degree the node count because we discovered less than configured. Use Node Count. Not Axis Count.
That function should return the number found in NodeInfo.xml. It is accurate except for nodes in which a user specifically choose to pretend was an axis. This is most often done by those who want an Encoder to ~be~ an axis so you can use Gearing or Camming with it.
You are right, the Axis Count is only loaded on Network Start. I’ll edit the above post to remove it for now. In a near future release, I’ll be reviewing all potential information that can be updated on Discovery rather than just Start.