[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

3438.0. "Packetprobe won't communicate with console term.." by TOPTEN::LEONARD (Paid to play) Wed Apr 10 1996 19:58

    I have a new Packetprobe that I am trying to get going.  I can't get
    the console to communicate with me.  I am using a H8571-J at the Probe,
    an BC16E cable, and another H8571-J at the DB9 connector on my PC.  I
    get no response.  Also, the # light is off even though I have a
    thinwire T and two terminators connected to the Probe.  
    
    Is this device dead?
T.RTitleUserPersonal
Name
DateLines
3438.1Look at the Power BrickBSS::RIGGENThu Apr 11 1996 14:215
    Double check the Power Brick you are using if this is standalone unit
    The H7857-AA causes Console problems....
    
    
    Jeff
3438.2Still no worky...TOPTEN::LEONARDPaid to playThu Apr 11 1996 17:433
    The power supply is a H7827-BA... Is this the right supply?  Any other
    ideas??
    
3438.3Try a VT screen with H8575-AGIDDAY::MORETTIDeath is just a formalityThu Apr 11 1996 23:3412
    
    try using a VT screen with the following cable/adapters :
    
    H8571-J ===== DECconnect cable =======H8575-A
    
    your power supply is correct.
    
    I tested the above combination and it works fine to a VT220 screen.
    
    Cheers
    
    John
3438.4Is the # light really the Network OK indicator??KYOSS1::JLEONARDPaid to play...Fri Apr 12 1996 09:2211
    A VT terminal is not readily convenient at this moment, all I have easy
    access to are PC's and their serial ports.  Works to talk to most other
    equipment...  Before I request replacement of this unit I will take it
    into the office and try connecting to a VT.
    
    Can anyone tell me whether the absence of the # light with a properly
    terminated thinwire connection indicates a problem?  I started with
    this device on a live network - same indication, # light out.  The
    documentation states that the  # light is the Network OK indicator. 
    When on the network port is properly terminated, when out it is not.
    Is this the true meaning of this light?  
3438.5no # light indicates problemGIDDAY::MORETTIDeath is just a formalitySun Apr 14 1996 20:4027
    
    
    I have tried :
    
    H8571-J ===== DECconnect cable  ========H8571-J
    
    and this works fine on my laptop 425.
    
    The lights are as follows in a hub90 :
    
    top (power)			= on
    2nd (network activity)	= depends on traffic
    3rd (network OK)		= on whether terminated or not
    
    I put a terminator in the 10baseT port and also the 10base% port and
    this made no difference to the status of the lights on my WORKING
    packetprobe.
    
    You should be able to connect the above cable/adapter combination and
    turn the probe on and see the bootup sequence.
    
    This has always been the case with my probe which has been upgraded
    from V1.0 to V2.6 and still responds the same way.
    
    cheers
    
    John
3438.6This Probe was DOA...TOPTEN::LEONARDPaid to playWed May 01 1996 09:563
    This Packetprobe was DOA...  I replaced it and can now connect to the
    console of the new device from the serial port on my PC with (2)H8571-J
    and BC16E.  Thanks for the assistance.