Am 06.11.2013 um 12:01 schrieb EBo <[email protected]>: > On Nov 6 2013 3:38 AM, Michael Haberler wrote: >> Am 06.11.2013 um 10:59 schrieb andy pugh <[email protected]>: >> >>> On 6 November 2013 06:27, Michael Haberler <[email protected]> >>> wrote: >>>> - on startup, rather than using the hal Python comp to connect >>>> directly to HAL, collect all pin names, types and direction, and pass >>>> this list to an HALrcomp API class instance; this would be the basis >>>> for the initial bind operation >>> >>> Rather than explicitly add new pins, would it be practical to change >>> the function of the "net" command to provisionally create/register >>> any >>> pins that don't exist when it is called? >> >> hm, interesting idea; I need to think this through >> >> what once could do is say state in halcmd >> >> autocreate gladevcp.* >> >> which would cause net's to gladevcp.* not fail but rather put them in >> a dormant state, and have halserver gooble those up and create the >> unbound component around them >> >> the key problem I see with this idea is: one cannot determine the pin >> direction just because the pin is named in a net statement; there >> might be several net commands to link more pins to the same signal >> and >> one would have to look at the complete set >> >> even if you have the complete net - pins and the signal, it isnt a >> valid conclusion to draw that if all other pins except the gladevcp.* >> pin are input, then the gladevcp.* pin must be output - it might have >> been intended as input, but the whole signal/pin net left unconnected >> to a writer for now >> >> both pro-forma declaration by 'newpin foo in float' and remote >> creation by the bind message handle this case unambiguously > > This assumes that pins are either input, or output. Have you ever > played with tristate logic? Is it even appropriate to think of tristate > logic in HAL when considering a distributed system?
not played, but it is certainly possible to include IO pins in change detection, as well as setting them remotely. if that makes a lot of sense in a remote UI scenario is a different matter. I cant even remember seeing a HAL_IO widget so far. -m > > > ------------------------------------------------------------------------------ > November Webinars for C, C++, Fortran Developers > Accelerate application performance with scalable programming models. Explore > techniques for threading, error checking, porting, and tuning. Get the most > from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
