22 Dec
2021
22 Dec
'21
7:59 a.m.
I am looking for the service guide for the RF30 DSSI disk. It is not on Manx
and not on BitSavers. Does anyone know of a copy? The part number is
apparently EK-RF30D-SV.
Thanks
Rob
23 Dec
23 Dec
1:45 a.m.
I wonder if anyone knows what diagnostic code 300B means?
>>set host/dup/uqssp/disk 2 params
PARAMS> status config
Configuration:
Node DIA0 is an RF30 controller
Software RFX V103 built on 5-MAY-1989 13:18:42
Electronics module name is EN94019334
Unit is inoperative, error code 300B(X)
Last known unit failure code 300B(X)
In 60233 power-on hours, power has cycled 189 times
System time is 5-MAY-1989 13:19:46
Regards
Rob
-----Original Message-----
From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob Jarratt via
cctalk
Sent: 22 December 2021 15:59
To: General Discussion: On-Topic and Off-Topic Posts
<cctalk at classiccmp.org>
Subject: DEC RF30 Integrated Storage Element Service Guide
I am looking for the service guide for the RF30 DSSI disk. It is not on
Manx and
not on BitSavers. Does anyone know of a copy? The part
number is
apparently EK-RF30D-SV.
Thanks
Rob
9:46 a.m.
I have tried three different RF30 disks, two of them from one source and one
from a completely different source, so completely
different histories. They
all give me the same diagnostic error code, 0x300B, which
seems to be too
much of a coincidence, so I think it may be something in my configuration.
I am using a MicroVAX 3800 (KA655 with KFQSA). When I power on, the fault
light comes on and then goes out after a while. This I believe is normal
behaviour. However, as soon as I try to access the disk (e.g. SHOW DEVICES
in the console firmware) the fault light come on and when I boot to VMS
(from a different disk), VMS can't see the drive.
I thought it might be some kind of DSSI ID conflict because I have an RF72
in the machine at ID 0. Removing the RF72 does not change the behaviour.
Installing an ID=0 plug on the RF30 does not change the behaviour. I set the
DIP switches on the RF30s to have an ID=1 and still it doesn't work and
PARAMS reports UNITNUM=0. I followed this page
http://mcmanis.com/chuck/computers/vaxen/dssi-plug.html but it didn't work:
PARAMS> sho /mscp
Parameter Current Default Type Radix
--------- ---------------- ---------------- -------- -----
MSCPNVR 2020202020202020 2020202020202020
2020202020202020 2020202020202020
2020202020202020 2020202020202020
2020202020202020 2020202020202020 String Hex RO
UNITID 1502401193918703 0000000000000 Quadword Hex RO
ALLCLASS 0 0 Byte Dec B
MEDIAID 2264601E 2264601E Longword Hex RO U
UNITNUM 0 0 Word Dec U
FIVEDIME 1 1 Boolean 0/1 B
FORCEUNI 1 1 Boolean 0/1 U
FORCECID 1 1 Boolean 0/1 RO
CNT_TMO 60 60 Word Dec RO
PARAMS> set unitnum 1
PARAMS> set forceuni 0
PARAMS> write
Failed to acquire unit, cannot WRITE
Am I doing something wrong?
Thanks
Rob
-----Original Message-----
From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob Jarratt via
cctalk
Sent: 23 December 2021 09:45
To: 'General Discussion: On-Topic and Off-Topic Posts'
<cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
I wonder if anyone knows what diagnostic code 300B means?
>>set host/dup/uqssp/disk 2 params
PARAMS> status config
Configuration:
Node DIA0 is an RF30 controller
Software RFX V103 built on 5-MAY-1989 13:18:42
Electronics module name is EN94019334
Unit is inoperative, error code 300B(X)
Last known unit failure code 300B(X)
In 60233 power-on hours, power has cycled 189 times
System time is 5-MAY-1989 13:19:46
Regards
Rob
-----Original Message-----
From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob Jarratt
via cctalk
Sent: 22 December 2021 15:59
To: General Discussion: On-Topic and Off-Topic Posts
<cctalk at classiccmp.org>
Subject: DEC RF30 Integrated Storage Element Service Guide
I am looking for the service guide for the RF30 DSSI disk. It is not
on
Manx and
> not on BitSavers. Does anyone know of a copy? The part number is
> apparently EK-RF30D-SV.
>
>
>
> Thanks
>
>
>
> Rob
1 Jan
1 Jan
11:29 p.m.
Can anyone help me to understand why all my RF30 disks report the same
diagnostic code 0x300B?
Thanks
Rob
-----Original Message-----
From: Rob Jarratt <robert.jarratt at ntlworld.com>
Sent: 23 December 2021 17:46
To: rob at jarratt.me.uk; 'Rob Jarratt' <robert.jarratt at ntlworld.com>;
'General
Discussion: On-Topic and Off-Topic Posts'
<cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
I have tried three different RF30 disks, two of them from one source and
one
from a completely different source, so completely
different histories.
They
all give me the same diagnostic error code, 0x300B,
which seems to be too
much of a coincidence, so I think it may be something in my configuration.
I am using a MicroVAX 3800 (KA655 with KFQSA). When I power on, the fault
light comes on and then goes out after a while. This I believe is normal
behaviour. However, as soon as I try to access the disk (e.g. SHOW DEVICES
in the console firmware) the fault light come on and when I boot to VMS
(from a different disk), VMS can't see the drive.
I thought it might be some kind of DSSI ID conflict because I have an RF72
in
the machine at ID 0. Removing the RF72 does not change
the behaviour.
Installing an ID=0 plug on the RF30 does not change the behaviour. I set
the
DIP switches on the RF30s to have an ID=1 and still it
doesn't work and
PARAMS reports UNITNUM=0. I followed this page
http://mcmanis.com/chuck/computers/vaxen/dssi-plug.html but it didn't
work:
PARAMS> sho /mscp
Parameter Current Default Type Radix
--------- ---------------- ---------------- -------- -----
MSCPNVR 2020202020202020 2020202020202020
2020202020202020 2020202020202020
2020202020202020 2020202020202020
2020202020202020 2020202020202020 String Hex RO
UNITID 1502401193918703 0000000000000 Quadword Hex RO
ALLCLASS 0 0 Byte Dec B
MEDIAID 2264601E 2264601E Longword Hex RO U
UNITNUM 0 0 Word Dec U
FIVEDIME 1 1 Boolean 0/1 B
FORCEUNI 1 1 Boolean 0/1 U
FORCECID 1 1 Boolean 0/1 RO
CNT_TMO 60 60 Word Dec RO
PARAMS> set unitnum 1
PARAMS> set forceuni 0
PARAMS> write
Failed to acquire unit, cannot WRITE
Am I doing something wrong?
Thanks
Rob
> -----Original Message-----
> From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob Jarratt
> via cctalk
> Sent: 23 December 2021 09:45
> To: 'General Discussion: On-Topic and Off-Topic Posts'
> <cctalk at classiccmp.org>
> Subject: RE: DEC RF30 Integrated Storage Element Service Guide
>
> I wonder if anyone knows what diagnostic code 300B means?
>
> >>>set host/dup/uqssp/disk 2 params
> PARAMS> status config
>
> Configuration:
> Node DIA0 is an RF30 controller
> Software RFX V103 built on 5-MAY-1989 13:18:42
> Electronics module name is EN94019334
> Unit is inoperative, error code 300B(X)
> Last known unit failure code 300B(X)
> In 60233 power-on hours, power has cycled 189 times
> System time is 5-MAY-1989 13:19:46
>
> Regards
>
> Rob
>
> > -----Original Message-----
> > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob
> > Jarratt via cctalk
> > Sent: 22 December 2021 15:59
> > To: General Discussion: On-Topic and Off-Topic Posts
> > <cctalk at classiccmp.org>
> > Subject: DEC RF30 Integrated Storage Element Service Guide
> >
> > I am looking for the service guide for the RF30 DSSI disk. It is not
> > on
> Manx and
> > not on BitSavers. Does anyone know of a copy? The part number is
> > apparently EK-RF30D-SV.
> >
> >
> >
> > Thanks
> >
> >
> >
> > Rob
2 Jan
2 Jan
5:01 a.m.
Rob,
I know this is probably a stupid suggestion, but are they terminated
correctly?
Dave
-----Original Message-----
From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob Jarratt via
cctalk
Sent: 02 January 2022 07:30
To: 'General Discussion: On-Topic and Off-Topic Posts'
<cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
Can anyone help me to understand why all my RF30 disks report the same
diagnostic code 0x300B?
Thanks
Rob
-----Original Message-----
From: Rob Jarratt <robert.jarratt at ntlworld.com>
Sent: 23 December 2021 17:46
To: rob at jarratt.me.uk; 'Rob Jarratt' <robert.jarratt at ntlworld.com>;
'General
Discussion: On-Topic and Off-Topic Posts'
<cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
I have tried three different RF30 disks, two of them from one source
and
one
from a completely different source, so completely
different histories.
They
all give me the same diagnostic error code,
0x300B, which seems to be
too much of a coincidence, so I think it may be something in my
configuration.
I am using a MicroVAX 3800 (KA655 with KFQSA). When I power on, the
fault light comes on and then goes out after a while. This I believe
is normal behaviour. However, as soon as I try to access the disk
(e.g. SHOW DEVICES in the console firmware) the fault light come on
and when I boot to VMS (from a different disk), VMS can't see the drive.
I thought it might be some kind of DSSI ID conflict because I have an
RF72
in
the machine at ID 0. Removing the RF72 does not
change the behaviour.
Installing an ID=0 plug on the RF30 does not change the behaviour. I
set
the
> DIP switches on the RF30s to have an ID=1 and still it doesn't work
> and PARAMS reports UNITNUM=0. I followed this page
> http://mcmanis.com/chuck/computers/vaxen/dssi-plug.html but it didn't
> work:
>
> PARAMS> sho /mscp
>
> Parameter Current Default Type Radix
> --------- ---------------- ---------------- -------- -----
> MSCPNVR 2020202020202020 2020202020202020
> 2020202020202020 2020202020202020
> 2020202020202020 2020202020202020
> 2020202020202020 2020202020202020 String Hex RO
> UNITID 1502401193918703 0000000000000 Quadword Hex RO
> ALLCLASS 0 0 Byte Dec B
> MEDIAID 2264601E 2264601E Longword Hex RO U
> UNITNUM 0 0 Word Dec U
> FIVEDIME 1 1 Boolean 0/1 B
> FORCEUNI 1 1 Boolean 0/1 U
> FORCECID 1 1 Boolean 0/1 RO
> CNT_TMO 60 60 Word Dec RO
>
> PARAMS> set unitnum 1
>
> PARAMS> set forceuni 0
>
> PARAMS> write
> Failed to acquire unit, cannot WRITE
>
> Am I doing something wrong?
>
> Thanks
>
> Rob
>
> > -----Original Message-----
> > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob
> > Jarratt via cctalk
> > Sent: 23 December 2021 09:45
> > To: 'General Discussion: On-Topic and Off-Topic Posts'
> > <cctalk at classiccmp.org>
> > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> >
> > I wonder if anyone knows what diagnostic code 300B means?
> >
> > >>>set host/dup/uqssp/disk 2 params
> > PARAMS> status config
> >
> > Configuration:
> > Node DIA0 is an RF30 controller
> > Software RFX V103 built on 5-MAY-1989 13:18:42
> > Electronics module name is EN94019334
> > Unit is inoperative, error code 300B(X)
> > Last known unit failure code 300B(X)
> > In 60233 power-on hours, power has cycled 189 times
> > System time is 5-MAY-1989 13:19:46
> >
> > Regards
> >
> > Rob
> >
> > > -----Original Message-----
> > > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob
> > > Jarratt via cctalk
> > > Sent: 22 December 2021 15:59
> > > To: General Discussion: On-Topic and Off-Topic Posts
> > > <cctalk at classiccmp.org>
> > > Subject: DEC RF30 Integrated Storage Element Service Guide
> > >
> > > I am looking for the service guide for the RF30 DSSI disk. It is
> > > not on
> > Manx and
> > > not on BitSavers. Does anyone know of a copy? The part number is
> > > apparently EK-RF30D-SV.
> > >
> > >
> > >
> > > Thanks
> > >
> > >
> > >
> > > Rob
6:05 a.m.
I thought I had checked, but I can double check just to be sure. Thanks for
the suggestion, it certainly feels like it could be something like this.
-----Original Message-----
From: dave.g4ugm at gmail.com <dave.g4ugm at gmail.com>
Sent: 02 January 2022 13:01
To: rob at jarratt.me.uk; 'Rob Jarratt' <robert.jarratt at ntlworld.com>;
'General
Discussion: On-Topic and Off-Topic Posts'
<cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
Rob,
I know this is probably a stupid suggestion, but are they terminated
correctly?
Dave
> -----Original Message-----
> From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob Jarratt
> via cctalk
> Sent: 02 January 2022 07:30
> To: 'General Discussion: On-Topic and Off-Topic Posts'
> <cctalk at classiccmp.org>
> Subject: RE: DEC RF30 Integrated Storage Element Service Guide
>
> Can anyone help me to understand why all my RF30 disks report the same
> diagnostic code 0x300B?
>
> Thanks
>
> Rob
>
> > -----Original Message-----
> > From: Rob Jarratt <robert.jarratt at ntlworld.com>
> > Sent: 23 December 2021 17:46
> > To: rob at jarratt.me.uk; 'Rob Jarratt' <robert.jarratt at
ntlworld.com>;
> 'General
> > Discussion: On-Topic and Off-Topic Posts' <cctalk at classiccmp.org>
> > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> >
> > I have tried three different RF30 disks, two of them from one source
> > and
> one
> > from a completely different source, so completely different histories.
> They
> > all give me the same diagnostic error code, 0x300B, which seems to
> > be too much of a coincidence, so I think it may be something in my
> configuration.
> >
> > I am using a MicroVAX 3800 (KA655 with KFQSA). When I power on, the
> > fault light comes on and then goes out after a while. This I believe
> > is normal behaviour. However, as soon as I try to access the disk
> > (e.g. SHOW DEVICES in the console firmware) the fault light come on
> > and when I boot to VMS (from a different disk), VMS can't see the
drive.
> >
> > I thought it might be some kind of DSSI ID conflict because I have
> > an
> > RF72
> in
> > the machine at ID 0. Removing the RF72 does not change the behaviour.
> > Installing an ID=0 plug on the RF30 does not change the behaviour. I
> > set
> the
> > DIP switches on the RF30s to have an ID=1 and still it doesn't work
> > and PARAMS reports UNITNUM=0. I followed this page
> > http://mcmanis.com/chuck/computers/vaxen/dssi-plug.html but it
> > didn't
> > work:
> >
> > PARAMS> sho /mscp
> >
> > Parameter Current Default Type Radix
> > --------- ---------------- ---------------- -------- -----
> > MSCPNVR 2020202020202020 2020202020202020
> > 2020202020202020 2020202020202020
> > 2020202020202020 2020202020202020
> > 2020202020202020 2020202020202020 String Hex RO
> > UNITID 1502401193918703 0000000000000 Quadword Hex RO
> > ALLCLASS 0 0 Byte Dec B
> > MEDIAID 2264601E 2264601E Longword Hex RO U
> > UNITNUM 0 0 Word Dec U
> > FIVEDIME 1 1 Boolean 0/1 B
> > FORCEUNI 1 1 Boolean 0/1 U
> > FORCECID 1 1 Boolean 0/1 RO
> > CNT_TMO 60 60 Word Dec RO
> >
> > PARAMS> set unitnum 1
> >
> > PARAMS> set forceuni 0
> >
> > PARAMS> write
> > Failed to acquire unit, cannot WRITE
> >
> > Am I doing something wrong?
> >
> > Thanks
> >
> > Rob
> >
> > > -----Original Message-----
> > > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob
> > > Jarratt via cctalk
> > > Sent: 23 December 2021 09:45
> > > To: 'General Discussion: On-Topic and Off-Topic Posts'
> > > <cctalk at classiccmp.org>
> > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> > >
> > > I wonder if anyone knows what diagnostic code 300B means?
> > >
> > > >>>set host/dup/uqssp/disk 2 params
> > > PARAMS> status config
> > >
> > > Configuration:
> > > Node DIA0 is an RF30 controller
> > > Software RFX V103 built on 5-MAY-1989 13:18:42
> > > Electronics module name is EN94019334
> > > Unit is inoperative, error code 300B(X)
> > > Last known unit failure code 300B(X)
> > > In 60233 power-on hours, power has cycled 189 times
> > > System time is 5-MAY-1989 13:19:46
> > >
> > > Regards
> > >
> > > Rob
> > >
> > > > -----Original Message-----
> > > > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of
Rob
> > > > Jarratt via cctalk
> > > > Sent: 22 December 2021 15:59
> > > > To: General Discussion: On-Topic and Off-Topic Posts
> > > > <cctalk at classiccmp.org>
> > > > Subject: DEC RF30 Integrated Storage Element Service Guide
> > > >
> > > > I am looking for the service guide for the RF30 DSSI disk. It is
> > > > not on
> > > Manx and
> > > > not on BitSavers. Does anyone know of a copy? The part number is
> > > > apparently EK-RF30D-SV.
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > > > Rob
7:18 a.m.
Rob,
If that is not the issue, do you need to try them in the MicroVax 4000 here?
Dave
(p.s. can SCSI terminators fit in a DSSI bus socket by mistake)
U
-----Original Message-----
From: Rob Jarratt <robert.jarratt at ntlworld.com>
Sent: 02 January 2022 14:05
To: dave.g4ugm at gmail.com; rob at jarratt.me.uk; 'General Discussion: On-
Topic and Off-Topic Posts' <cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
I thought I had checked, but I can double check just to be sure. Thanks
for
the suggestion, it certainly feels like it could be
something like this.
histories.
-----Original Message-----
From: dave.g4ugm at gmail.com <dave.g4ugm at gmail.com>
Sent: 02 January 2022 13:01
To: rob at jarratt.me.uk; 'Rob Jarratt' <robert.jarratt at ntlworld.com>;
'General
> Discussion: On-Topic and Off-Topic Posts' <cctalk at classiccmp.org>
> Subject: RE: DEC RF30 Integrated Storage Element Service Guide
>
> Rob,
>
> I know this is probably a stupid suggestion, but are they terminated
> correctly?
>
> Dave
>
>
> > -----Original Message-----
> > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob
> > Jarratt via cctalk
> > Sent: 02 January 2022 07:30
> > To: 'General Discussion: On-Topic and Off-Topic Posts'
> > <cctalk at classiccmp.org>
> > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> >
> > Can anyone help me to understand why all my RF30 disks report the
> > same diagnostic code 0x300B?
> >
> > Thanks
> >
> > Rob
> >
> > > -----Original Message-----
> > > From: Rob Jarratt <robert.jarratt at ntlworld.com>
> > > Sent: 23 December 2021 17:46
> > > To: rob at jarratt.me.uk; 'Rob Jarratt'
> > > <robert.jarratt at ntlworld.com>;
> > 'General
> > > Discussion: On-Topic and Off-Topic Posts' <cctalk at
classiccmp.org>
> > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> > >
> > > I have tried three different RF30 disks, two of them from one
> > > source and
> > one
> > > from a completely different source, so completely different
> They
> > all give me the same diagnostic error code, 0x300B, which seems to
> > be too much of a coincidence, so I think it may be something in my
> configuration.
> >
> > I am using a MicroVAX 3800 (KA655 with KFQSA). When I power on,
> > the fault light comes on and then goes out after a while. This I
> > believe is normal behaviour. However, as soon as I try to access
> > the disk (e.g. SHOW DEVICES in the console firmware) the fault
> > light come on and when I boot to VMS (from a different disk), VMS
> > can't see the
drive.
> >
> > I thought it might be some kind of DSSI ID conflict because I have
> > an
> > RF72
> in
> > the machine at ID 0. Removing the RF72 does not change the
behaviour.
> > > Installing an ID=0 plug on the RF30 does not change the behaviour.
> > > I set
> > the
> > > DIP switches on the RF30s to have an ID=1 and still it doesn't
> > > work and PARAMS reports UNITNUM=0. I followed this page
> > > http://mcmanis.com/chuck/computers/vaxen/dssi-plug.html but it
> > > didn't
> > > work:
> > >
> > > PARAMS> sho /mscp
> > >
> > > Parameter Current Default Type Radix
> > > --------- ---------------- ---------------- -------- -----
> > > MSCPNVR 2020202020202020 2020202020202020
> > > 2020202020202020 2020202020202020
> > > 2020202020202020 2020202020202020
> > > 2020202020202020 2020202020202020 String Hex RO
> > > UNITID 1502401193918703 0000000000000 Quadword Hex RO
> > > ALLCLASS 0 0 Byte Dec B
> > > MEDIAID 2264601E 2264601E Longword Hex RO
> >
UNITNUM 0 0 Word Dec U
> > FIVEDIME 1 1 Boolean 0/1 B
> > FORCEUNI 1 1 Boolean 0/1 U
> > FORCECID 1 1 Boolean 0/1 RO
> > CNT_TMO 60 60 Word Dec RO
> >
> > PARAMS> set unitnum 1
> >
> > PARAMS> set forceuni 0
> >
> > PARAMS> write
> > Failed to acquire unit, cannot WRITE
> >
> > Am I doing something wrong?
> >
> > Thanks
> >
> > Rob
> >
> > > -----Original Message-----
> > > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob
> > > Jarratt via cctalk
> > > Sent: 23 December 2021 09:45
> > > To: 'General Discussion: On-Topic and Off-Topic Posts'
> > > <cctalk at classiccmp.org>
> > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> > >
> > > I wonder if anyone knows what diagnostic code 300B means?
> > >
> > > >>>set host/dup/uqssp/disk 2 params
> > > PARAMS> status config
> > >
> > > Configuration:
> > > Node DIA0 is an RF30 controller
> > > Software RFX V103 built on 5-MAY-1989 13:18:42
> > > Electronics module name is EN94019334
> > > Unit is inoperative, error code 300B(X)
> > > Last known unit failure code 300B(X)
> > > In 60233 power-on hours, power has cycled 189 times
> > > System time is 5-MAY-1989 13:19:46
> > >
> > > Regards
> > >
> > > Rob
> > >
> > > > -----Original Message-----
> > > > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of
Rob
> > > > Jarratt via cctalk
> > > > Sent: 22 December 2021 15:59
> > > > To: General Discussion: On-Topic and Off-Topic Posts
> > > > <cctalk at classiccmp.org>
> > > > Subject: DEC RF30 Integrated Storage Element Service Guide
> > > >
> > > > I am looking for the service guide for the RF30 DSSI disk. It
> > > > is not on
> > > Manx and
> > > > not on BitSavers. Does anyone know of a copy? The part number
> > > > is apparently EK-RF30D-SV.
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > > > Rob
7:51 a.m.
I have other DSSI machines to try them in, just a bit less easy to install
them in those machines. Going to check the termination now.
-----Original Message-----
From: dave.g4ugm at gmail.com <dave.g4ugm at gmail.com>
Sent: 02 January 2022 15:19
To: rob at jarratt.me.uk; 'General Discussion: On-Topic and Off-Topic Posts'
<cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
Rob,
If that is not the issue, do you need to try them in the MicroVax 4000
here?
Dave
(p.s. can SCSI terminators fit in a DSSI bus socket by mistake)
U
> > > > UNITNUM 0 0 Word Dec U
> > > > FIVEDIME 1 1 Boolean 0/1 B
> > > > FORCEUNI 1 1 Boolean 0/1 U
> > > > FORCECID 1 1 Boolean 0/1 RO
> > > > CNT_TMO 60 60 Word Dec RO
> > > >
> > > > PARAMS> set unitnum 1
> > > >
> > > > PARAMS> set forceuni 0
> > > >
> > > > PARAMS> write
> > > > Failed to acquire unit, cannot WRITE
> > > >
> > > > Am I doing something wrong?
> > > >
> > > > Thanks
> > > >
> > > > Rob
> > > >
> > > > > -----Original Message-----
> > > > > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf
Of Rob
> > > > > Jarratt via cctalk
> > > > > Sent: 23 December 2021 09:45
> > > > > To: 'General Discussion: On-Topic and Off-Topic Posts'
> > > > > <cctalk at classiccmp.org>
> > > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> > > > >
> > > > > I wonder if anyone knows what diagnostic code 300B means?
> > > > >
> > > > > >>>set host/dup/uqssp/disk 2 params
> > > > > PARAMS> status config
> > > > >
> > > > > Configuration:
> > > > > Node DIA0 is an RF30 controller
> > > > > Software RFX V103 built on 5-MAY-1989 13:18:42
> > > > > Electronics module name is EN94019334
> > > > > Unit is inoperative, error code 300B(X)
> > > > > Last known unit failure code 300B(X)
> > > > > In 60233 power-on hours, power has cycled 189 times
> > > > > System time is 5-MAY-1989 13:19:46
> > > > >
> > > > > Regards
> > > > >
> > > > > Rob
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: cctalk <cctalk-bounces at classiccmp.org> On
Behalf Of
> > > > > > Rob Jarratt via cctalk
> > > > > > Sent: 22 December 2021 15:59
> > > > > > To: General Discussion: On-Topic and Off-Topic Posts
> > > > > > <cctalk at classiccmp.org>
> > > > > > Subject: DEC RF30 Integrated Storage Element Service Guide
> > > > > >
> > > > > > I am looking for the service guide for the RF30 DSSI disk.
> > > > > > It is not on
> > > > > Manx and
> > > > > > not on BitSavers. Does anyone know of a copy? The part
> > > > > > number is apparently EK-RF30D-SV.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > >
> > > > > >
> > > > > > Rob
>
-----Original Message-----
From: Rob Jarratt <robert.jarratt at ntlworld.com>
Sent: 02 January 2022 14:05
To: dave.g4ugm at gmail.com; rob at jarratt.me.uk; 'General Discussion: On-
Topic and Off-Topic Posts' <cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
I thought I had checked, but I can double check just to be sure.
Thanks
for
the suggestion, it certainly feels like it could
be something like this.
histories.
-----Original Message-----
From: dave.g4ugm at gmail.com <dave.g4ugm at gmail.com>
Sent: 02 January 2022 13:01
To: rob at jarratt.me.uk; 'Rob Jarratt' <robert.jarratt at ntlworld.com>;
'General
> Discussion: On-Topic and Off-Topic Posts' <cctalk at classiccmp.org>
> Subject: RE: DEC RF30 Integrated Storage Element Service Guide
>
> Rob,
>
> I know this is probably a stupid suggestion, but are they terminated
> correctly?
>
> Dave
>
>
> > -----Original Message-----
> > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Rob
> > Jarratt via cctalk
> > Sent: 02 January 2022 07:30
> > To: 'General Discussion: On-Topic and Off-Topic Posts'
> > <cctalk at classiccmp.org>
> > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> >
> > Can anyone help me to understand why all my RF30 disks report the
> > same diagnostic code 0x300B?
> >
> > Thanks
> >
> > Rob
> >
> > > -----Original Message-----
> > > From: Rob Jarratt <robert.jarratt at ntlworld.com>
> > > Sent: 23 December 2021 17:46
> > > To: rob at jarratt.me.uk; 'Rob Jarratt'
> > > <robert.jarratt at ntlworld.com>;
> > 'General
> > > Discussion: On-Topic and Off-Topic Posts'
> > > <cctalk at classiccmp.org>
> > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> > >
> > > I have tried three different RF30 disks, two of them from one
> > > source and
> > one
> > > from a completely different source, so completely different >
They
> > all give me the same diagnostic error code, 0x300B, which seems
> > to be too much of a coincidence, so I think it may be something
> > in my
> configuration.
> >
> > I am using a MicroVAX 3800 (KA655 with KFQSA). When I power on,
> > the fault light comes on and then goes out after a while. This I
> > believe is normal behaviour. However, as soon as I try to access
> > the disk (e.g. SHOW DEVICES in the console firmware) the fault
> > light come on and when I boot to VMS (from a different disk),
> > VMS can't see the
drive.
> >
> > I thought it might be some kind of DSSI ID conflict because I
> > have an
> > RF72
> in
> > the machine at ID 0. Removing the RF72 does not change the
behaviour.
> > > Installing an ID=0 plug on the RF30 does not change the behaviour.
> > > I set
> > the
> > > DIP switches on the RF30s to have an ID=1 and still it doesn't
> > > work and PARAMS reports UNITNUM=0. I followed this page
> > > http://mcmanis.com/chuck/computers/vaxen/dssi-plug.html but it
> > > didn't
> > > work:
> > >
> > > PARAMS> sho /mscp
> > >
> > > Parameter Current Default Type Radix
> > > --------- ---------------- ---------------- -------- -----
> > > MSCPNVR 2020202020202020 2020202020202020
> > > 2020202020202020 2020202020202020
> > > 2020202020202020 2020202020202020
> > > 2020202020202020 2020202020202020 String Hex RO
> > > UNITID 1502401193918703 0000000000000 Quadword Hex RO
> > > ALLCLASS 0 0 Byte Dec B
> > > MEDIAID 2264601E 2264601E Longword Hex RO
8:04 a.m.
Hmm... There was already a terminator installed. I tried to remove it in
case there was some kind of double termination, but that didn't seem to
resolve it. The terminator is good because the machine works with other
disks.
Regards
Rob
-----Original Message-----
From: Rob Jarratt <robert.jarratt at ntlworld.com>
Sent: 02 January 2022 15:52
To: 'dave.g4ugm at gmail.com' <dave.g4ugm at gmail.com>;
'rob at jarratt.me.uk' <rob at jarratt.me.uk>; 'General Discussion:
On-Topic and
Off-Topic Posts' <cctalk at classiccmp.org>
Subject: RE: DEC RF30 Integrated Storage Element Service Guide
I have other DSSI machines to try them in, just a bit less easy to install
them
in those machines. Going to check the termination
now.
> -----Original Message-----
> From: dave.g4ugm at gmail.com <dave.g4ugm at gmail.com>
> Sent: 02 January 2022 15:19
> To: rob at jarratt.me.uk; 'General Discussion: On-Topic and Off-Topic
Posts'
> <cctalk at classiccmp.org>
> Subject: RE: DEC RF30 Integrated Storage Element Service Guide
>
> Rob,
> If that is not the issue, do you need to try them in the MicroVax 4000
here?
> Dave
> (p.s. can SCSI terminators fit in a DSSI bus socket by mistake)
>
> > -----Original Message-----
> > From: Rob Jarratt <robert.jarratt at ntlworld.com>
> > Sent: 02 January 2022 14:05
> > To: dave.g4ugm at gmail.com; rob at jarratt.me.uk; 'General Discussion:
> > On- Topic and Off-Topic Posts' <cctalk at classiccmp.org>
> > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> >
> > I thought I had checked, but I can double check just to be sure.
> > Thanks
> for
> > the suggestion, it certainly feels like it could be something like
this.
> >
> > > -----Original Message-----
> > > From: dave.g4ugm at gmail.com <dave.g4ugm at gmail.com>
> > > Sent: 02 January 2022 13:01
> > > To: rob at jarratt.me.uk; 'Rob Jarratt'
> > > <robert.jarratt at ntlworld.com>;
> > 'General
> > > Discussion: On-Topic and Off-Topic Posts' <cctalk at
classiccmp.org>
> > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> > >
> > > Rob,
> > >
> > > I know this is probably a stupid suggestion, but are they
> > > terminated correctly?
> > >
> > > Dave
> > >
> > >
> > > > -----Original Message-----
> > > > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of
Rob
> > > > Jarratt via cctalk
> > > > Sent: 02 January 2022 07:30
> > > > To: 'General Discussion: On-Topic and Off-Topic Posts'
> > > > <cctalk at classiccmp.org>
> > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> > > >
> > > > Can anyone help me to understand why all my RF30 disks report
> > > > the same diagnostic code 0x300B?
> > > >
> > > > Thanks
> > > >
> > > > Rob
> > > >
> > > > > -----Original Message-----
> > > > > From: Rob Jarratt <robert.jarratt at ntlworld.com>
> > > > > Sent: 23 December 2021 17:46
> > > > > To: rob at jarratt.me.uk; 'Rob Jarratt'
> > > > > <robert.jarratt at ntlworld.com>;
> > > > 'General
> > > > > Discussion: On-Topic and Off-Topic Posts'
> > > > > <cctalk at classiccmp.org>
> > > > > Subject: RE: DEC RF30 Integrated Storage Element Service Guide
> > > > >
> > > > > I have tried three different RF30 disks, two of them from one
> > > > > source and
> > > > one
> > > > > from a completely different source, so completely different
> histories.
> > > > They
> > > > > all give me the same diagnostic error code, 0x300B, which
> > > > > seems to be too much of a coincidence, so I think it may be
> > > > > something in my
> > > > configuration.
> > > > >
> > > > > I am using a MicroVAX 3800 (KA655 with KFQSA). When I power
> > > > > on, the fault light comes on and then goes out after a while.
> > > > > This I believe is normal behaviour. However, as soon as I try
> > > > > to access the disk (e.g. SHOW DEVICES in the console firmware)
> > > > > the fault light come on and when I boot to VMS (from a
> > > > > different disk), VMS can't see the
> > drive.
> > > > >
> > > > > I thought it might be some kind of DSSI ID conflict because I
> > > > > have an
> > > > > RF72
> > > > in
> > > > > the machine at ID 0. Removing the RF72 does not change the
> > behaviour.
> > > > > Installing an ID=0 plug on the RF30 does not change the
behaviour.
> > > > > I set
> > > > the
> > > > > DIP switches on the RF30s to have an ID=1 and still it
doesn't
> > > > > work and PARAMS reports UNITNUM=0. I followed this page
> > > > > http://mcmanis.com/chuck/computers/vaxen/dssi-plug.html but it
> > > > > didn't
> > > > > work:
> > > > >
> > > > > PARAMS> sho /mscp
> > > > >
> > > > > Parameter Current Default Type Radix
> > > > > --------- ---------------- ---------------- -------- -----
> > > > > MSCPNVR 2020202020202020 2020202020202020
> > > > > 2020202020202020 2020202020202020
> > > > > 2020202020202020 2020202020202020
> > > > > 2020202020202020 2020202020202020 String Hex
RO
> > > > > UNITID 1502401193918703
0000000000000 Quadword Hex
RO
> > > > > ALLCLASS 0
0 Byte Dec
B
> > > > > MEDIAID 2264601E
2264601E Longword Hex
RO
> U
> > > > > UNITNUM 0 0 Word Dec
U
> > > > > FIVEDIME 1
1 Boolean 0/1
B
> > > > > FORCEUNI 1
1 Boolean 0/1
U
> > > > > FORCECID 1
1 Boolean 0/1
RO
> > > > > CNT_TMO 60
60 Word Dec
RO
> > > > >
> > > > > PARAMS> set unitnum 1
> > > > >
> > > > > PARAMS> set forceuni 0
> > > > >
> > > > > PARAMS> write
> > > > > Failed to acquire unit, cannot WRITE
> > > > >
> > > > > Am I doing something wrong?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Rob
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: cctalk <cctalk-bounces at classiccmp.org> On
Behalf Of
> > > > > > Rob Jarratt via cctalk
> > > > > > Sent: 23 December 2021 09:45
> > > > > > To: 'General Discussion: On-Topic and Off-Topic
Posts'
> > > > > > <cctalk at classiccmp.org>
> > > > > > Subject: RE: DEC RF30 Integrated Storage Element Service
> > > > > > Guide
> > > > > >
> > > > > > I wonder if anyone knows what diagnostic code 300B means?
> > > > > >
> > > > > > >>>set host/dup/uqssp/disk 2 params
> > > > > > PARAMS> status config
> > > > > >
> > > > > > Configuration:
> > > > > > Node DIA0 is an RF30 controller
> > > > > > Software RFX V103 built on 5-MAY-1989 13:18:42
> > > > > > Electronics module name is EN94019334
> > > > > > Unit is inoperative, error code 300B(X)
> > > > > > Last known unit failure code 300B(X)
> > > > > > In 60233 power-on hours, power has cycled 189 times
> > > > > > System time is 5-MAY-1989 13:19:46
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Rob
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: cctalk <cctalk-bounces at classiccmp.org>
On Behalf Of
> > > > > > > Rob Jarratt via cctalk
> > > > > > > Sent: 22 December 2021 15:59
> > > > > > > To: General Discussion: On-Topic and Off-Topic Posts
> > > > > > > <cctalk at classiccmp.org>
> > > > > > > Subject: DEC RF30 Integrated Storage Element Service
Guide
> > > > > > >
> > > > > > > I am looking for the service guide for the RF30 DSSI
disk.
> > > > > > > It is not on
> > > > > > Manx and
> > > > > > > not on BitSavers. Does anyone know of a copy? The
part
> > > > > > > number is apparently EK-RF30D-SV.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Rob
> >
10:07 a.m.
On Sun, Jan 2, 2022 at 9:22 AM Rob Jarratt via cctalk
<cctalk at classiccmp.org> wrote:
Hmm... There was already a terminator installed. I tried to remove it in
case there was some kind of double termination, but that didn't seem to
resolve it. The terminator is good because the machine works with other
disks.
If other disks work when they are swapped in without making any other
changes, it is probably not a termination issue.
However, you still might want to double check that the DSSI bus is
properly terminated at both ends. If the M7769 KFQSA is attached to a
bulkhead connector panel, there are two versions, one with a single
DSSI connector, and one with two DSSI connectors.
If the bulkhead connector panel has a single DSSI connector, there
should be SIP terminators installed on the M7769 KFQSA next to the
DSSI connector on the M7769 KFQSA as one end of the DSSI bus.
If the bulkhead connector panel has two DSSI connectors, the SIP
terminators should be removed on the M7769 KFQSA next to the DSSI
connector on the M7769 KFQSA, and there should be an external
terminator on one of the two DSSI connectors on the bulkhead connector
panel.
If there is no bulkhead connector panel connected directly to the
M7769 KFQSA, and instead it is connected to an internal DSSI bus cable
inside the chassis, and the M7769 KFQSA is at the end of the internal
DSSI bus cable, there should be SIP terminators installed on the M7769
KFQSA next to the DSSI connector on the M7769 KFQSA as one end of the
DSSI bus. I would expect the other end of the internal DSSI bus cable
to connect to a bulkhead connector panel, which should have an
external terminator attached as the other end of the DSSI bus.
3 Jan
3 Jan
3:23 a.m.
-----Original Message-----
From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Glen Slick via
cctalk
Sent: 02 January 2022 18:07
To: General Discussion: On-Topic and Off-Topic Posts
<cctalk at classiccmp.org>
Subject: Re: DEC RF30 Integrated Storage Element Service Guide
On Sun, Jan 2, 2022 at 9:22 AM Rob Jarratt via cctalk <cctalk at classiccmp.org>
wrote:
Yes, other disks work and I don't think it can be a termination problem. However, I
did check your points below and everything does seem to be correct, please see responses
below. The problem persists though.
Hmm... There was already a terminator installed. I tried to remove it
in case there was some kind of double termination, but that didn't
seem to resolve it. The terminator is good because the machine works
with other disks.
If other disks work when they are swapped in without making any other
changes, it is probably not a termination issue.
However, you still might want to double check that the DSSI bus is properly
terminated at both ends. If the M7769 KFQSA is attached to a bulkhead
connector panel, there are two versions, one with a single DSSI connector,
and one with two DSSI connectors.
My KFQSA has only one DSSI connector and it is not connected to a bulkhead connector
panel.
If the bulkhead connector panel has a single DSSI connector, there should be
SIP terminators installed on the M7769 KFQSA next to the DSSI connector on
the M7769 KFQSA as one end of the DSSI bus.
There are terminators installed behind the DSSI connector. The KFQSA manual says they
should be removed if using a bulkhead connector, but I am not. I have the cable coming
down from the storage area into the DSSI connector.
If the bulkhead connector panel has two DSSI connectors, the SIP
terminators should be removed on the M7769 KFQSA next to the DSSI
connector on the M7769 KFQSA, and there should be an external terminator
on one of the two DSSI connectors on the bulkhead connector panel.
If there is no bulkhead connector panel connected directly to the
M7769 KFQSA, and instead it is connected to an internal DSSI bus cable inside
the chassis, and the M7769 KFQSA is at the end of the internal DSSI bus cable,
there should be SIP terminators installed on the M7769 KFQSA next to the
DSSI connector on the M7769 KFQSA as one end of the DSSI bus. I would
expect the other end of the internal DSSI bus cable to connect to a bulkhead
connector panel, which should have an external terminator attached as the
other end of the DSSI bus.
This is indeed the case.
842
days inactive
854
days old
10 comments
3 participants
participants (3)
-
dave.g4ugm＠gmail.com -
glen.slick＠gmail.com -
robert.jarratt＠ntlworld.com