Jump to content

SID now sorta works...


nILS

Recommended Posts

Hi!

When I test my SID (Core stuffed with 16F) with the SID_V2 test program, I get that wonderful chord at startup. ;D After that, I should according to µcApps be able to play notes on Channels 1-3. Whenever I sent notes to the core, all I get's a clicking sound. One "click" for note on, another one for the note off event. ??? Has anybody ever come across the same problem? Any ideas?

Link to comment
Share on other sites

??? Ok, since the SID played that beautiful song with the test program it appears to work. So, I assume that the problem I have is a software problem. I still only get that clicking sound no matter what I do. I tried playing some notes on channel 1 using JSynth (tried Presets, too), MidiOX and my keyboard - all I hear is "click"... :(

Link to comment
Share on other sites

Hmmmm, I just noticed - my Core doesn't send ANY SysEx at all. Not even with the test_tx program. It used to give me some SysEx with that, and the SID_V2 still works, too! ??? What 's up with that?

MidiOx is configured correctly though (tested with my Roland Synth) and the MidiOut on the Core is hooked up correctly, too... Strange. Any idea, TK?

/edit: Some add. info

Link to comment
Share on other sites

Does the tx test send other events than SysEx data? -> you've activated the SysEx filter in MIDI-Ox

Did you check the pinning of the MIDI socket? -> exchanged cables

Did you check the output signals with a LED? http://www.ucapps.de/howtodebug/midi_out_led.gif

NOTE: this simple LED circuit helps to indicate the outgoing signal, but it consumes some power - you have to disconnect the LED before connecting the MIDI Out of your MIDIbox with the MIDI In of your PC!

Best Regards, Thorsten.

Link to comment
Share on other sites

For some unknown reason the core sends  "volume" with the test tx again =) The SID firmware still doesn't give me any results though.

I checked the pinning on the midi socket - all correct.

Any more ideas?

Thanks for your time, TK!

Link to comment
Share on other sites

No, with these inputs (sometimes working, sometimes not) it's impossible to give usefull tips into the right direction.

First try to find the root cause why your hardware is so unstable - check the solderings, cables, etc... and use the verify function of IC-Prog to ensure that the firmware has been burned correctly into the PIC.

Best Regards, Thorsten.

Link to comment
Share on other sites

I followed your advice and checked everything again - didn't find anything. But since the last time the problem of something not working occured, everything seems fine - except for the Core not working with the SID firmware. The PIC is burnt right, too.

So, everything seems to be stable now ;) BUT as I said, the firmware doesn't work. To me it seems the problem could be that the Core is not really getting the MIDI IN right. Is there a test program to check that?

Sorry, that I can't give you some more information that would sort some sources of the problem out...  :(

Link to comment
Share on other sites

No, the PIC18F isn't code compatible to the PIC16F...

however, the bootloader provides all the functions which are necessary to test the MIDI IO: it sends a SysEx string after power-on (MIDI-Out test) and it reacts on incoming upload requests (MIDI-In test)

Best Regards, Thorsten.

Link to comment
Share on other sites

After a lot more testing and checking I'm down to that:

  • The hardware is all ok.
  • The PIC is burnt correctly
  • The software on my computer is set up correctly
  • The cables are ok
  • SID_V2 works
  • test_tx works
  • test_rxtx does NOT do anything
  • the sid firmware does NOT do what it's supposed to. Clicking sound for every MidiEvent. Sound does NOT come up, when the MidiIn cable is disconnected - MidiIn seems to work. The click is louder when the MidiOut cable is connected.

I hope this helps a little. I really don't have any clue what the problem might be...

Link to comment
Share on other sites

could you please record the clicking sound? I guess that it doesn't come from the SID, but from your MIDI port, and the reason could be that the optocoupler isn't connected correctly. But I need an audible impression to realize what is going on there.

Best Regards, Thorsten.

Link to comment
Share on other sites

I'll try to record it, BUT: The signal is really low, so when I try to record it, I have to turn the volume up so much that all I get is static. I'll try to figure something out.

I ordered a new optocoupler just in case. Should be here on Tuesday...

Link to comment
Share on other sites

Alright - this is not the SID, this is digital noise from the MIDI In port - possibly the optocoupler is still ok, the error must be between optocoupler and PIC.

Just follow these instructions:

http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1055726526;start=1#1

especially check the polarity of the 6N138, the 1N4148 diode and the MIDI cable

Best Regards, Thorsten.

Link to comment
Share on other sites

Done with all the testing:

I confirmed once more, that all the parts are mounted right. They are.

Checks with the LED: LED lights up, but does not dim or flicker, no matter what. (SysEx stream, Midi Events ).

When I connect the LED directly to the MidiIn it lights up for every Event. So the signal gets lost somewhere in the Core, I guess?! Optocoupler gone?!

Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...