Jump to content

ChinMuzik

Members
  • Posts

    105
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by ChinMuzik

  1. On 9/20/2017 at 4:23 AM, Smithy said:

    It's not Java Script, it's a Java executable. 

    Just download and install Java on your machine and run the .jar file. 

    Make sure the midi in and midi out of the MIDIbox SID is connected properly otherwise you won't be able to open the patch editor interface.

    Right, but in the link you posted there's no .jar files just CLASS files.

  2. On 6/20/2017 at 11:18 AM, jaytee said:

    I bit the bullet and bought my Mb6582 display from Crystalfontz. It was a little pricy, but with how much variance in quality there is between LCDs, I figured it was worth it to get something nice.

    I wish but they don't have a white character on black backing. I kind of need it. 

  3. 3 hours ago, latigid on said:

    Of course, I asked incessantly if they could add switches, but because of the design that isn't possible. The workaround is to use individual metal touch sensors, which is a bit different but is quite easy to get used to I think. 

    I might be alone on this, but I actually prefer the capacitive touch knobs over push encoders

  4. I was browsing Hawkeyes MBProgramma build and was wondering how intensive a project for a similar patch editor would be which would consist of the following.

    16 LED ring encoders

    8 faders

    16 buttons

    Each with a dedicated scribble strip which would display the parameters of a synth (which would be saved as a layout in MIOS?)

    Maybe even highlight the relative controls, similar to the Kiwi Patch Editor.

    Thoughts?

  5. Just had a weird revelation. 

    After burning the bootloader, even though MIOS studio doesn't send any message that the bootloader is detected, it clearly sees the bootloader as it will allow the uploading of MIOS and the LCD driver. 

    Is this a know quirk of MIOS studio or am I just overlooking some obvious indication that the bootloader is being detected?

  6. So I ended up exporting the .hex from the preburned PIC I received from SmashTV and then flashing it to each PIC I received from Mike, then changing each ID with the change_id app. Successful, MIOS sees all 4 cores.

    Still would like to know why it was failing to see the PIC after burning the bootloader.

  7. So my PICkit2 came in today. I loaded the PIC into the ZIF and the application detected it as the 18f6485 family...

    I burned the bootloader hex successfully and verified it successfully. But when stuffing it in the mb6582 base PCB, MIOS Studio still isn't seeing it. But sees the PIC I purchased from Tim with no issue. 

    Also, when I take the PICs I purchased from Mike back to the PIC programmer, it can no longer verify the program and it cannot be deleted either. It will show deleted but when doing a blank check it will fail.

    What are the odds of having 4 bad chips? Could they be counterfeit possibly?

  8. On 12/29/2010 at 3:20 PM, jojjelito said:

    +1oneoneeleven!!!!111

     

    As long as the ST32 outputs the correct timer signals to the 3396's waveform converters we are gold.

    Me on this: Stalled for now :(

     

    Back to Xcode.

    How bout the 3372 too?? :D

  9. I buy all my resistors, ceramic caps, diodes, some transistors, jacks and sockets from Tayda.

    I don't buy pots, IC's and electrolytics and film/mylar caps from them. 

    I did buy the shift registers for the MB build from them though. 

    Even the caps and resistors I buy I test with this handy little thing (pictured).

     

    Also: back to the troubleshooting. Reset at the PIC didn't help...and I am pretty sure the 10mhz crystals are parallel cut, I remember someone telling me values that low are almost always parallel cut. One other thing on that, even if it was serial cut..Doesn't the PIC force the crystal to oscillate how it wants? 

     

    One more last ditch attempt before I dump the funds on a Pickit2...I didn't check the following (because the test flow considered both I/O to be functional). 

    • TEST OUT3: Somebody noticed in the forum, that the MIDI Out of his core module didn't work because of an "incompatibility issue" with the bench supply he used and the switching PSU of his PC. The solution was to disconnect the middle pin of J12 (ground line of MIDI Out port)

    What is J12 represented as on the mb6582 PCB? I can't seem to locate it.

     

     

     

     

     

    IMG_20170316_182910.jpg

  10. Ok, tried again.

    I've attached photo to show exactly what happens.

    The first photo show the messages that flood when I turn the PSU on with any 3 of the 4 PIC loaded in any single core.

    The second picture shows what happens when I query the same 3 of the 4 PIC's

    The third picture shows a different message that will OCCASIONALLY appear when doing a query. 

    These events are the same in all positions on the PCB and no matter what Device ID is set in MIOS

     

    The 4th PIC generates no messages no matter where it's seated.

    IMG_20170316_153001.jpg

    IMG_20170316_153008.jpg

    IMG_20170316_153018.jpg

  11. 4 minutes ago, latigid on said:

    If you have one "Core" position where one PIC works and another doesn't, maybe it's a problem with those PICs? If you're in Germany, you could send me the PICs and I'd check them for you.

    Technically, none of them work. They just "don't work" in different ways lol. Which is why I believe it to not be the PICs..Unless the they weren't burned with the bootloader. But Mike explicitly said they would be. 

    I'm in the states, it might be more cost effective to get a clone PickIt2. Just that it would suck to buy it and it not be the issue.

     

×
×
  • Create New...