VOGONS


First post, by x73rmin8r

User metadata
Rank Newbie
Rank
Newbie

I just got an Akai SG01K, got it hooked up to a working PC/MIDI system, but I can't get it to receive any MIDI signals through the MIDI IN port. Other midi boxes play music correctly when I swap the midi cable between them, and the Akai will play its internal demo tracks if I select them, but it doesn't play anything through the MIDI cable. There's a small indicator light that blinks when it's supposed to be processing MIDI signals that blinks when it's playing the demos, but never any other time.

Does anybody who has one of these know if it has some special mode it needs to be in to accept signals? I've tried switching between Single and Multi Channel mode. Is the input probably just broken? All the other MIDI modules I've used just start playing as soon as there's an input signal, interrupting whatever menu you were in.

Had a look at the solder connections and nothing looked messed up.

Reply 1 of 12, by dominusprog

User metadata
Rank Oldbie
Rank
Oldbie

First of all, clean the socket with contact cleaner. If nothing changed, check for broken solder joints.

Duke_2600.png
A-Trend ATC-1020 V1.1 ❇ Cyrix 6x86 150+ @ 120MHz ❇ 32MiB EDO RAM (8MiBx4) ❇ A-Trend S3 Trio64V2 2MiB
Aztech Pro16 II-3D PnP ❇ 8.4GiB Quantum Fireball ❇ Win95 OSR2 Plus!

Reply 2 of 12, by SuperDeadite

User metadata
Rank Member
Rank
Member

This is known to happen. The Akai auto saves everything and it's internal memory can do weird things if not used for a long time. Factory reset should fix this. Plug in the unit and turn it off with the power switch on back. Next use one hand to push and hold the UP and DOWN buttons.on the front. While holding both of these, use your other hand to press the power switch and turn it on. You will see CLR flash on the display.

Modules: CM-64, CM-500, SC-55MkII, SC-88 Pro, SY22, TG100, MU2000EX, PLG100-SG, PLG150-DR, PLG150-AN, SG01k, NS5R, GZ-50M, SN-U110-07, SN-U110-10, Pocket Studio 5, DreamBlaster S2, X2, McFly, E-Wave, QWave, CrystalBlaster C2, Yucatan FX, BeepBlaster

Reply 3 of 12, by x73rmin8r

User metadata
Rank Newbie
Rank
Newbie

Thanks for the recommendations!

I checked the midi connector by plugging in a midi cable and checking the pins on the other end of the midi cable against the solder connections on the back of the circuit board for the connector and got continuity on all the pins.

I tried the reset, got it to display the "CLR", but no change.

I noticed that the internal battery seems to have been replaced with a socket like you'd see on a motherboard instead of the soldered on battery that I saw in a picture online of the inside of one of these. I tried running it with and without the battery, no difference.

Reply 4 of 12, by SuperDeadite

User metadata
Rank Member
Rank
Member

Are you giving it enough power? The original ac adapter was 10v@800mA.

Modules: CM-64, CM-500, SC-55MkII, SC-88 Pro, SY22, TG100, MU2000EX, PLG100-SG, PLG150-DR, PLG150-AN, SG01k, NS5R, GZ-50M, SN-U110-07, SN-U110-10, Pocket Studio 5, DreamBlaster S2, X2, McFly, E-Wave, QWave, CrystalBlaster C2, Yucatan FX, BeepBlaster

Reply 5 of 12, by x73rmin8r

User metadata
Rank Newbie
Rank
Newbie

Yup, pleasantly surprised to find that the AC adapter it came with was actually 10v instead of 9 or 12. 850mA.

Reply 6 of 12, by x73rmin8r

User metadata
Rank Newbie
Rank
Newbie

Anybody have any last minute suggestions?

Assuming the midi-in connector is working correctly and it's an issue with the memory, and the factory reset didn't solve it?

I can still return it if it's not something I can fix.

Thanks for the responses everybody.

EDIT: It's kind of working now! I left it plugged in and on for a while and now it actually accepts midi-in signals, or at least some of them. It'll play songs, but very haltingly and corrupted. Like it's only playing some of the notes and instruments.

Reply 7 of 12, by dominusprog

User metadata
Rank Oldbie
Rank
Oldbie

Have you checked for broken solder joints on the board?

Duke_2600.png
A-Trend ATC-1020 V1.1 ❇ Cyrix 6x86 150+ @ 120MHz ❇ 32MiB EDO RAM (8MiBx4) ❇ A-Trend S3 Trio64V2 2MiB
Aztech Pro16 II-3D PnP ❇ 8.4GiB Quantum Fireball ❇ Win95 OSR2 Plus!

Reply 8 of 12, by x73rmin8r

User metadata
Rank Newbie
Rank
Newbie

I didn't see any, though I didn't have any magnification or anything.

Not sure if you saw the edit, it sort of half works now, I'd left it powered on for a while and after that it accepts signals (the light blinks when MIDI data is sent to it) and it plays sounds, but not all the sounds it's supposed to.

Reply 9 of 12, by x73rmin8r

User metadata
Rank Newbie
Rank
Newbie

Good news! It works seemingly fine now. I guess it just had to cook a while. If anybody ever runs into a similar problem the solution seems to be to plug it in and turn it on, leave it that way for a while, reset it a few times, and exercise it by trying to play stuff through it until it works the kinks out.

Also make sure you've got it in "multi" mode, even once it's working right it will only play one instrument in "single" mode.

Reply 10 of 12, by SuperDeadite

User metadata
Rank Member
Rank
Member

Typically "warm up time to function properly" = bad capacitors.

Modules: CM-64, CM-500, SC-55MkII, SC-88 Pro, SY22, TG100, MU2000EX, PLG100-SG, PLG150-DR, PLG150-AN, SG01k, NS5R, GZ-50M, SN-U110-07, SN-U110-10, Pocket Studio 5, DreamBlaster S2, X2, McFly, E-Wave, QWave, CrystalBlaster C2, Yucatan FX, BeepBlaster

Reply 11 of 12, by x73rmin8r

User metadata
Rank Newbie
Rank
Newbie

Gotcha, guess I better measure them before they pop

Reply 12 of 12, by dominusprog

User metadata
Rank Oldbie
Rank
Oldbie
SuperDeadite wrote on 2024-09-02, 23:10:

Typically "warm up time to function properly" = bad capacitors.

True, the board needs a recap.

Duke_2600.png
A-Trend ATC-1020 V1.1 ❇ Cyrix 6x86 150+ @ 120MHz ❇ 32MiB EDO RAM (8MiBx4) ❇ A-Trend S3 Trio64V2 2MiB
Aztech Pro16 II-3D PnP ❇ 8.4GiB Quantum Fireball ❇ Win95 OSR2 Plus!