Some moths ago we discussed about replacements for the dying DS1287A RTC chips used in some machines, like the VAXStation 4000. At that time I found (and shared) a chinese dealer who had some chips in stock. I ordered a pair of those, and:
- One of them was dead on arrival.
- The other one was working, but it died a month ago (so I guess the chinese stock is made with old chips whose battery cells are dying).
Fortunately, there are good news. There is a snap-in replacement made by MAXIM. The chip is the DS12887A, and can be bought from regular electronics sources. I got mine from Farnell, at 11,13 a piece, and it aparently works flawlesly. This is the datasheet:
http://www.farnell.com/datasheets/22860.pdf
The Farnell part # is 1606597.
(I also have tried to fix one of my dead 1287's, but I'm not very good with the solder iron...)
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On 2014-05-02 13:56, Jordi Guillaumes i Pons wrote:
El 02/05/2014, a les 10.59, Cory Smelosky <b4 at gewt.net> va escriure:
Johnny,
You needed an ULTRIX box to test against, right?
9.5 should work for that. Once I figure out how to configure the guest account!
BITXOU (7.82) is also up and running, access info is guest/guest. It is running in a Raspberry Pi, sharing the little thingy with a KLH10 instance, a PDP11 and another VAX, so don't expect a whooping speed :)
Yay! Works. But damn, that was slow. :-)
Also, seems like FAL on Ultrix-32 have some bugs. :-)
Thanks. One more system checked against RSX with my new fix in place.
Johnny
El 02/05/2014, a les 10.59, Cory Smelosky <b4 at gewt.net> va escriure:
Johnny,
You needed an ULTRIX box to test against, right?
9.5 should work for that. Once I figure out how to configure the guest account!
BITXOU (7.82) is also up and running, access info is guest/guest. It is running in a Raspberry Pi, sharing the little thingy with a KLH10 instance, a PDP11 and another VAX, so don't expect a whooping speed :)
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On Fri, 2 May 2014, Brian Hechinger wrote:
Reloading router: 75.49.13.201 hecnetconfigupdate 199.166.5.172
tunnel-dev.gimme-sympathy.org-ipv4.txt
running.................................................................................................................................
failed
Well, different error this time. :)
-brian
It might be timeout related. It's a bit slow. cisco 2524 (68030) processor (revision J) with 14336K/2048K bytes of memory.
I've got SNMP debug on so try another push.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Fri, 2 May 2014, Brian Hechinger wrote:
Let me know when you're ready for a push.
Done. Try now.
-brian
On May 2, 2014, at 7:37, Cory Smelosky <b4 at gewt.net> wrote:
On Fri, 2 May 2014, Brian Hechinger wrote:
UDP
That'd be why. ;)
-brian
On May 2, 2014, at 4:22, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 1 May 2014, Brian Hechinger wrote:
Still doesn't like you. :)
Reloading router: 75.49.13.201 hecnetconfigupdate 199.166.5.172 tunnel-dev.gimme-sympathy.org-ipv4.txt
Error reloading router: dev.gimme-sympathy.org :: No SNMP response received before timeout
Is SNMP using UDP or TCP?
pass in on $ext_if proto tcp from 199.166.5.172 to any port snmp rdr-to 10.10.0.10 port snmp
access-list 2 permit 199.166.5.172
All seems like it should be working...perhaps SNMP is supposed to be UDP?
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Let me know when you're ready for a push.
-brian
On May 2, 2014, at 7:37, Cory Smelosky <b4 at gewt.net> wrote:
On Fri, 2 May 2014, Brian Hechinger wrote:
UDP
That'd be why. ;)
-brian
On May 2, 2014, at 4:22, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 1 May 2014, Brian Hechinger wrote:
Still doesn't like you. :)
Reloading router: 75.49.13.201 hecnetconfigupdate 199.166.5.172 tunnel-dev.gimme-sympathy.org-ipv4.txt
Error reloading router: dev.gimme-sympathy.org :: No SNMP response received before timeout
Is SNMP using UDP or TCP?
pass in on $ext_if proto tcp from 199.166.5.172 to any port snmp rdr-to 10.10.0.10 port snmp
access-list 2 permit 199.166.5.172
All seems like it should be working...perhaps SNMP is supposed to be UDP?
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Fri, 2 May 2014, Brian Hechinger wrote:
UDP
That'd be why. ;)
-brian
On May 2, 2014, at 4:22, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 1 May 2014, Brian Hechinger wrote:
Still doesn't like you. :)
Reloading router: 75.49.13.201 hecnetconfigupdate 199.166.5.172 tunnel-dev.gimme-sympathy.org-ipv4.txt
Error reloading router: dev.gimme-sympathy.org :: No SNMP response received before timeout
Is SNMP using UDP or TCP?
pass in on $ext_if proto tcp from 199.166.5.172 to any port snmp rdr-to 10.10.0.10 port snmp
access-list 2 permit 199.166.5.172
All seems like it should be working...perhaps SNMP is supposed to be UDP?
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Reloading router: 75.49.13.201 hecnetconfigupdate 199.166.5.172
tunnel-dev.gimme-sympathy.org-ipv4.txt
running.................................................................................................................................
failed
Well, different error this time. :)
-brian
On Fri, May 02, 2014 at 07:40:16AM -0400, Cory Smelosky wrote:
On Fri, 2 May 2014, Brian Hechinger wrote:
Let me know when you're ready for a push.
Done. Try now.
-brian
On May 2, 2014, at 7:37, Cory Smelosky <b4 at gewt.net> wrote:
On Fri, 2 May 2014, Brian Hechinger wrote:
UDP
That'd be why. ;)
-brian
On May 2, 2014, at 4:22, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 1 May 2014, Brian Hechinger wrote:
Still doesn't like you. :)
Reloading router: 75.49.13.201 hecnetconfigupdate 199.166.5.172 tunnel-dev.gimme-sympathy.org-ipv4.txt
Error reloading router: dev.gimme-sympathy.org :: No SNMP response received before timeout
Is SNMP using UDP or TCP?
pass in on $ext_if proto tcp from 199.166.5.172 to any port snmp rdr-to 10.10.0.10 port snmp
access-list 2 permit 199.166.5.172
All seems like it should be working...perhaps SNMP is supposed to be UDP?
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
UDP
-brian
On May 2, 2014, at 4:22, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 1 May 2014, Brian Hechinger wrote:
Still doesn't like you. :)
Reloading router: 75.49.13.201 hecnetconfigupdate 199.166.5.172 tunnel-dev.gimme-sympathy.org-ipv4.txt
Error reloading router: dev.gimme-sympathy.org :: No SNMP response received before timeout
Is SNMP using UDP or TCP?
pass in on $ext_if proto tcp from 199.166.5.172 to any port snmp rdr-to 10.10.0.10 port snmp
access-list 2 permit 199.166.5.172
All seems like it should be working...perhaps SNMP is supposed to be UDP?
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Johnny,
You needed an ULTRIX box to test against, right?
9.5 should work for that. Once I figure out how to configure the guest account!
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
