Feedback MC6847digitizer

[c0pperdragon]

Please let us know about your experience with this device. Pictures of the install and screenshots are highly appreciated.

[MC6809E089]

Hello, just wanted to give an update. I've received my MC6847digitizer, put a socket on it (mounted upside down to keep it in the correct orientation obvs), plugged it into my PAL Dragon 64 and (drumroll)... it works great. :)

It works fine with most of the internal and external mods and expansions I have, so the CoCoSDC, Dragon MMC, and SuperSpriteFM carts, and the internal lower-case/alternate char-set mod board. The only thing it seems to be incompatible with is the Dragon RGB mod I have.

It's not really a surprise to me that the Dragon RGB mod doesn't play nice with the MC6847digitizer, and I think it's probably not the MC6847digitizer's fault. I would guess the RGB mod further messes with the already shonky PAL/NTSC line and sync generation which PAL Dragons do to make the 6847 compatible-ish with the PAL tv standard. I can still see a picture coming out of the 6847Digitizer when the RGB mod is connected at the same time but it's all flickery (almost rolling) like it's losing vertical sync.

The picture from the MC6847digitizer via the RGBtoHDMI is way better than the RGB mod + OSSC etc. anyhow, so no need for both of them to be in the computer at the same time. I did end up with a bit of a megadrive-like "tower of power" but there is still plenty of room in the Dragon's case, both above, and around the MC6847digitizer, so no problem with it physicially fitting inside.

I'll post some pictures when I get chance, in case they are of help to anyone else.

Thanks again c0pperdragon! :)

[c0pperdragon]

Hi! Great to hear that this works so nicely. About the incompatibility with the Dragon RGB, I also can only guess. If this is that board https://dragonpluselectronics.com/product/superrgb-6x09-for-dragon-and-coco-12-computers/ then the only lines that are used by it and my board are the CLK (pin 33) and the FS (pin 37). From my understanding, the SuperRGB does not intentionally alter any of the signals, but it may well but some extra load on an already marginal clock signal, or creates signal reflection because of the non-neglegible length of its flex cable. Measurements with an oscilloscope could of course be helpful. best regards, Reinhard Am Mi., 25. März 2026 um 18:07 Uhr schrieb MC6809E089 < ***@***.***>:

…

*MC6809E089* left a comment (c0pperdragon/LumaCode#48) <#48 (comment)> Hello, just wanted to give an update. I've received my MC6847digitizer, put a socket on it (mounted upside down to keep it in the correct orientation obvs), plugged it into my PAL Dragon 64 and (drumroll)... it works great. :) It works fine with most of the internal and external mods and expansions I have, so the CoCoSDC, Dragon MMC, and SuperSpriteFM carts, and the internal lower-case/alternate char-set mod board. The only thing it seems to be incompatible with is the Dragon RGB mod I have. It's not really a surprise to me that the Dragon RGB mod doesn't play nice with the MC6847digitizer, and I think it's probably not the MC6847digitizer's fault. I would guess the RGB mod further messes with the already shonky PAL/NTSC line and sync generation which PAL Dragons do to make the 6847 compatible-ish with the PAL tv standard. I can still see a picture coming out of the 6847Digitizer when the RGB mod is connected at the same time but it's all flickery (almost rolling) like it's losing vertical sync. The picture from the MC6847digitizer via the RGBtoHDMI is way better than the RGB mod + OSSC etc. anyhow, so no need for both of them to be in the computer at the same time. I did end up with a bit of a megadrive-like "tower of power" but there is still plenty of room in the Dragon's case, both above, and around the MC6847digitizer, so no problem with it physicially fitting inside. Thanks again c0pperdragon! :) — Reply to this email directly, view it on GitHub <#48?email_source=notifications&email_token=ACTIHVCJ3OQHEXSBEJQIIBT4SQG3JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJSHAZDMNJYGEYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4128265810>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACTIHVHMSLSQ7HV5S5UXZEL4SQG3JAVCNFSM6AAAAACWUJ3AIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMRYGI3DKOBRGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>