Jump to content

Can't get my Core SysExed


Guest domas

Recommended Posts

Guest domas

Finally I have got my JDM working under XP and I have programmed several PIC. So I decided to try them in action, finished my core module, tested voltages, put in a  PIC programmed with BootLoader, soldered midi cable,  as in http://www.ucapps.de/mbhp/mbhp_midi_gameport.gif and hooked it up to my Live!. Configured MIDI-OX as in BootLoader page. Turned my core on got that nice string after that I tried to SysEx it but I only get that request string. Here is the log:

 TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               
 0001D83D   9  XXX    F0  Buffer:     8 Bytes   System Exclusive      
 SYSX: F0 00 00 7E 40 00 01 F7
 0001DFA4   9  XXX    F0  Buffer:     8 Bytes   System Exclusive      
 SYSX: F0 00 00 7E 40 00 01 F7
 0001E70A   9  XXX    F0  Buffer:     8 Bytes   System Exclusive      
 SYSX: F0 00 00 7E 40 00 01 F7
 0001EE70   9  XXX    F0  Buffer:     8 Bytes   System Exclusive      
 SYSX: F0 00 00 7E 40 00 01 F7
 0001F5D6   9  XXX    F0  Buffer:     8 Bytes   System Exclusive      
 SYSX: F0 00 00 7E 40 00 01 F7
 0001FD3C   9  XXX    F0  Buffer:     8 Bytes   System Exclusive      
 SYSX: F0 00 00 7E 40 00 01 F7
 000204A2   9  XXX    F0  Buffer:     8 Bytes   System Exclusive      
 SYSX: F0 00 00 7E 40 00 01 F7
 0066FF4B   9  --     FF    --    --   --  ---  System Reset          

After first string I started sending mios_v1_3.syx, but as you can see it simply don't get that SysEx. I tried to SysEx it witk onboard sound car, but get the same - nothing. What is wrong? I'm confused:-/, I checked all configurations, reprogrammed PIC without any use.

Link to comment
Share on other sites

Hello Domas!!!

You should try leaving your buffers under sysex/configure to 2048 * 4 @ 700ms delay after F7. The delay should also be at zero. Thorsten had suggested these as a possible standard, and they work great.

Also go to the devices section and disable automatically attach inputs to outputs, go to the top right cell open the midi output and erase the input from the output.

I myself had problems initially similar to this.

I would check the midi ports and make shure they are connected properly first.

Second I would test my voltages, let me know what voltages you are getting ( Especially at the LCD +5v :)

I would initially disconnect the LCD to make shure this is not causing problems like it did in mine.

--------------------------------------------------------------------

You can test this

by removing the D7 and +5V line - in this case the LCD driver should

get a timeout and ignore all following calls to MIOS_LCD_*

Thanks Thorsten :)

--------------------------------------------------------------------

Check all your connections (all of them making shure buttons and AIN are pulled up/down properly.

If it seems to load the MIOS with the LCD disconnected check your LCD connections. If these are correct add a 100 ohm resistor at the LCD +5v. This helped stablize my system.

When you load MIOS you should see 13 checksums.

After loading MIOS it will restart and only send the verification string once. You can check and see if MIOS is working by send the string (F0 00 00 7E 40 00 0F F7) it should reply fairly fast. Also you can verify if MIOS is working by uploading the CRC application.

Let me know what you find!

-Sephult

Link to comment
Share on other sites

  • 3 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...