|
Untitled Page
ARCHIVED FORUM -- April 2007 to March 2012 READ ONLY FORUM
This is the first Archived Forum which was active between 17th April 2007 and
1st March February 2012
Search
-
[quote user="stefan"] I just noticed that Safari can not open beotech..(?) [/quote] Probably a temporary problem - won't work for me either with Firefox, although I visited there just yesterday. Have to say that those pages are incredibly messy, probably because of having evolved over time... (and the actual page is (supposed to be) here
-
No, I don't think so - as I mentioned in the opening post, all that stuff works just great when I connect it to the BS6500.
-
[quote user="vikinger"] EDIT A lot of forums are suggesting that the Welsh Moel y Parc transmitter is putting out a new powerful signal that is making TVs lock onto this in retuning.... moving the BBC NW Winter Hill channels down to frequency 800+. But why this should happen with aerials pointing away from Moel y Parc is a bit of a mystery
-
Dunno how relevant this is over there since our DVB semantics differ slightly, but often there will be problems with automatic tuning if the box first locks on a transmitter from a wrong area while receiving the network information; then it will search for the rest of the channels at incorrect frequencies for the area. If you know the frequencies of
-
There was no need to dig in the middle... I put the scope straight on the relevant port pin of the processor and the data from the MCL came cleanly all the way there. Nothing out in return, though. It could be that the output function of the 8031 port pin is damaged - but that still doesn't explain why the all-standby command goes through and is
-
Well, what better way to pass time inbetween cooking than opening Beomasters. So here is the CPU module - and clearly the updated software ROM is there, so there must be some other problem. Too bad the processor is not socketed, so I will not just try replacing it although I have 8031's laying around. TR3 on the preamp module will be attacked next
-
[quote user="Friedmett"] I got a MCL manual saying the serial should be after: 05101264 for being ready for Beolink. [/quote] Great info, thanks. This is s/n 0682xxxx, so it might have a fault after all. Have to look into it. I guess the part number will be on a sticker on the ROM chip, so that should tell it for sure...
-
Well, that is up to you - if you can live with the current buzz, just let it be. The supply of replacement transformers will not be exactly plentiful unless you want to put something modern in there, and that could also be difficult (apparently 20 + 110 V secondaries are needed). A transformer from another 1500 might have the same problem. According
-
OK, thanks - in that case I'll probably solve the issue by not installing the 5500 in an MCL setup After posting, I had the sense to try with an MCP6500 through MCL (and putting an oscilloscope on the data line) and the BM isn't responding in any way on the MCL. In addition, it is only the long "all-standby" command that goes through
-
I have a spare MCL2A I'm trying to make sense of in case I need it later. I tried it with a BM5500 I had lying around but ran into local room control problems... first of all, it works just fine with my Beosystem 6500 so there should be nothing wrong with the transceiver, the box, the cabling or my option programming. With the 5500, the transceiver
|
|
|