Ian Smith wrote:
>
> I was looking over Mathew's shoulder during the problems with the ip
> address for the gpib/lan gateway. I wonder if it would simplify things if
> one either gave the whole ip address, rather than a fragment,
Not possible, as explained in the documentation, due to the fact that
GPIB_IO hardware link declares only a 'short' (16 bits) for the link
number. Full ip address needs 32 bits and even this will brake as soon
as ipv6 comes into consideration.
> or, declared
> the beast in the startup script with a hostAdd.
>
> The second method would be my favoured one as it is the easier to change
> if the gateway ip address changes.
Same problem. Don't have a free string field in GPIB_IO link type to
specify gateway name. Existing string field is already used by device
support.
The better solution is to use the new GPIB support. There you explicitly
define the mapping between link numbers and hardware addresses (such as
ip address of the gateway) by a driver configuration call from startup
script.
Ben
- References:
- Re: HP E2050A LanGpib gateway driver Ian Smith
- Navigate by Date:
- Prev:
Re: HP E2050A LanGpib gateway driver Ian Smith
- Next:
capfast document Ian Smith
- Index:
1994
1995
1996
1997
1998
1999
<2000>
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: HP E2050A LanGpib gateway driver Ian Smith
- Next:
Re: HP E2050A LanGpib gateway driver Eric Norum
- Index:
1994
1995
1996
1997
1998
1999
<2000>
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|