Talk:Biphase mark code

SVG picture

I made the picture with Dia, so I could export it in SVG as well. I did it, but I got a wrong output, as you can see in Image:Bmc.svg: I don't know whether it is a problem of the programme or of wikipedia's engine. Anyway I used the PNG version you see in the article. Alessio Damato 14:29, 21 September 2005 (UTC)[reply]

Merge with Differential Manchester

If a merge is to happen between these two codes, it might be an idea to merge with Manchester as well. The basic idea of all three schemes is very similar and comparison and contrast may be useful. I like having separate pages for things like this though as a useful reference. A big page isn't that. I vote no on the merge, especially if only BMC and Differential Manchester are to be merged.--Ktims 05:33, 15 March 2006 (UTC)[reply]

I think it would be better to keep them separated; we might create another page where we compare them, but having one page each is clearer. Alessio Damato 08:54, 1 June 2006 (UTC)[reply]

I agree with Alessio. I vote no, too, for the same reasons. It also allows for technical detail that might be out of context in a merged topic. Aki Korhonen 18:28, 18 July 2006 (UTC)[reply]

Page title

Can we really consider this to be a proper noun? I think the page should be named 'Biphase mark code' instead. This would match the other line codes here, as well as Wiki policy.--Ktims 07:09, 1 June 2006 (UTC)[reply]

I agree Alessio Damato 08:54, 1 June 2006 (UTC)[reply]

Sources?

Bot wants sources. All I have is Stallings, which doesn't mention BMC, only Manchester and DManchester. Anyone got some reputable material we can reference?

Clock Frequency?

The article states that "the frequency of the clock is twice the bitrate of the original signal." From the diagram, it seems to me that the clock frequency is equal to the bitrate of the data (original signal). 63.167.168.8 20:58, 5 March 2007 (UTC)[reply]

Yup, I'll correct it. Either would work fine in practice (symbol clock detects either edge, bit clock detects rising edge, for example), but the article and diagram should obviously match. --Ktims 04:27, 7 March 2007 (UTC)[reply]

Still not sure about this one, "the symbol rate must be twice the bitrate of the original signal", only 1 bit of data is transmitted per symbol, so the symbol rate is the same as the bitrate, should perhaps be changed to "The data is encoded onto a clock with twice the frequency of the bitrate" or similar. If this is incorrect please delete.--80.44.157.77 15:16, 27 April 2007 (UTC)[reply]

We're using one technical definition of the term "symbol rate", which is "how often the voltage on the line can change" (symbol (data)). Since in biphase mark code, the voltage can change twice per bit, that's 2 "symbols" per bit. Since the symbol rate of "biphase mark code" is double the symbol rate of non-return-to-zero, the bandwidth required for "biphase mark code" is double the bandwidth required for non-return-to-zero (at the same bitrate). In 8B/10B encoding, a group of line voltage changes (symbols) (in this case 10) decodes into 8 bits. Alas, some people look at the entire group (10 symbols) and call it one "symbol". I wouldn't be surprised if this were another perfectly valid, official definition of the word "symbol", but it sure makes things confusing. What can we do to make this article correct, without being unnecessarily confusing? --75.37.225.73 03:49, 10 May 2007 (UTC)[reply]

Would this be less confusing (and just as correct)? Do things the same as Return-to-zero: use "bandwidth" instead of "symbol rate", replacing the confusing sentence

"When encoding, the symbol rate must be twice the bitrate of the original signal."

with

"The bandwidth required for biphase mark code is double the bandwidth required for non-return-to-zero, at the same data rate."

? --75.41.34.231 03:28, 18 May 2007 (UTC)[reply]