There is loads of stuff here :Wow, the ADB I/O's manual seems like it contains a full specification of the ADB protocol... it's unfortunate that only the HTML version of it seems to have been archived, and that without any of the images. Grrr.
I suspect they used this style (voltage/brand/model tbc) of relay :Shoot, I thought I'd looked for that. Anyway, great! The appendix on the ADB format makes it quite straightforward to program a PIC to speak this language... can't promise anything, but I could definitely see implementing this in the not-too-distant future.
Thanks for this, I'll test other ADB devices when I come across them.Without splitting it open, there are some steps that you can perform (or that anyone with any ADB device can perform) to get some first-pass information on it:
Doing this will help me start to compile a list of devices and their IDs and benefit the general cause of Apple history. =)
- Download and run ADB Parser on a mac with the device plugged in
- Identify the device on the list
- Your ADB keyboard and mouse should be the devices at addresses 2 and 3, and the host should be at 0, so the ADB device under test should be whatever's left over if there are no other devices plugged into your ADB ports
- Click the device in the list and note the "Original Address", "Original Handler", "Current Handler", and "Current Address"
- Click "Talk" on the radio buttons in the left panel and enter "1" for the register, then click "Send Command" and note the data received below (if any)
- Do the same with "2" for the register
Hmm. When you say it "reports consistently", do you mean it gives the same sequence of outputs every time starting when reset/rebooted? If so, does it ever appear to loop?Talk "2" reports consistently as many times as the command is sent until the ADB Reinit button is pressed, the computer is rebooted, or the device is hotplugged.
Sorry, it reports the same value every time I click send command, up until I click ADB Reinit/etcHmm. When you say it "reports consistently", do you mean it gives the same sequence of outputs every time starting when reset/rebooted? If so, does it ever appear to loop?
You’re welcome!In any case, thank you, I've added the Sentinel Eve3 to the ADB devices list on TashNotes.
Also, aiee, don't hotplug unless you have more electrical engineering knowledge than I do (which isn't difficult) and know it to be safer than I think it is...
Interesting. I might have to slap the analyzer on mine to see if the host sends it something that seeds the value or something...it reports the same value every time I click send command, up until I click ADB Reinit/etc
I was thinking it could produce a sequence of rolling codes, but I took more readings and found repeats. They don't appear to be in a pattern though, maybe it just chooses from a list of valid codes and the software is set to expect a different one each launch?Interesting. I might have to slap the analyzer on mine to see if the host sends it something that seeds the value or something...
Whilst my PIC programming skills aren’t quite as developed, I’d happily design an interface PCB to include things like this. We can take this off line for now to ensure we don’t bombard this topic with noise, thoughIt would be nice to put some open collector outputs on it so we could drive interesting loads.... but I'm getting carried away.
Sure! I doubt I can crack it remotely (knowing as little as I do about Mac dongles) but I'd love to add it to the list.I can ask him to test it if it is of interest.
It certainly does! I'll DM you.Does this qualify ? It’s a Nubus image grabber (color) from neotech, but it also uses the ADB bus to control the box.