dwestbury

Members
  • Content count

    46
  • Joined

  • Last visited

Community Reputation

7 Neutral

About dwestbury

Contact Methods

  • MSN Dwestbury_505@msn.com

Profile Information

  • Gender Male
  • Location New York City Area
  • Interests Electronic Music, Retro Demo Scene, DIY Electronics, Data Visualization

Recent Profile Visitors

144 profile views
  1. SID "Clones" List/Sources/Experiences

    Nice list! One I’d like to see added is the great sounding SID implementation that Gideon from the Ultimate 1541 / Ultimate 64 project (https://ultimate64.com/) has made with a Xilinx FPGA. I don’t think he’s been persuaded to consider selling it as a separate product yet however.    I hear that SwinSID ultimate is very good, but they’re nowhere to be found and the creator has gone a little mad from what I understand (https://www.facebook.com/262253294115914/posts/798860600455178/?d=n&substory_index=0)   Regular SwinSIDs are cheap as chips and seemingly easy to come by (eBay, etc.), but there’s lots of complaints about sound quality online.    What’s the verdict on the ARMSID? I haven’t heard much about them?   Cheers.  
  2. The FPGASID Project

    At €79, the FPGASID feels a little price-prohibitive. You get 2x SIDs for that price, but the installation into a real C64 is a bit convoluted.    Did @TK. finalize a design that actually bypassed the need for a SID module (see his comments above from Oct 2017)? That would potentially raise the value in my mind...   
  3. SID 4 not available can bus errors

    [PROBLEM SOLVED] Quite embarrassed to admit that the issue was not related to the electronics at all, but rather the false assumptions I made while trying to figure out how to setup the firmware on my PIC Core modules. I thought that changing the PIC device ID (applying device_id_0X.hex through MIOS) was the last step in the firmware deployment process, but I still needed to add the setup _mb6582 hex, after the device ID change. It's interesting to note how the device responds with CAN Bus Error when it the firmware is incomplete.  Now I'm happy to say that all core modules are working perfectly... wheew... Yet another lesson learned...  Finally off to *jam* with this thing!
  4. I was seeing an error on startup which read "SID 4 not available (CAN bus errors)", along with a flashing top row of LEDs and flashing left column.        I searched the forum and found this thread, which gave me some direction: http://midibox.org/forums/topic/13270-sidx-not-available-can-bus-errors-after-wiring-mb-6582-cs/#comment-119958 Specifically this comment from Wilba:   So, I disconnected my LCD from the control surface and the flashing LED issue went away, so I must have been shorting the tactile switches behind the control surface. However, I'm still getting the same error whenever I try to access any SID module other than SID1... For reference, I can confirm that all of the D1_COREX diodes are in place, as well as R80. I've reflowed them to be sure the solder joints are good, but still no luck...     Perhaps I should replace the diode under Core1?  Other suggestions? Appreciate any insights.  
  5. MIDIbox V2 2nd sid problem

    The sammichSID only contains one SID module (called SID module 1 or just SID 1), but this module supports two SID chips. If your sammichSID came with some preinstalled patches, you can step through them to hear the stereo separation (assuming you're using a stereo TRS audio out cable as opposed to mono TS cable). If not, you can find a great collection of patches here: https://github.com/midibox/mios8/tree/master/apps/synthesizers/midibox_sid_v2/presets You can use the Sysex librarian built into MIOS Studio to install them using your MIDI interface: http://www.ucapps.de/mios_studio.html The control surface menu will allow you to intentionally activate or deactivate SID chips, but the default behavior is to play from both. The first steps guide in the user manual explains how to read the display: http://www.ucapps.de/midibox_sid_manual_l.html     
  6. To me, the JB Weld bit is way tougher than the electronics ;-) Keeping fingers crossed that I don't make an absolute mess of it... -Darrell    
  7. Change PIC ID using a Mac for MB-6582 Core 0

    Connecting two posts that inevitably crossed into the same territory... After completing the steps above to create the Master Core Module, I stumbled around a bit more to understand how to change device ID’s for the slave modules...  All the required steps are outlined here...  http://midibox.org/forums/topic/21261-pic-programming-question/?do=findComment&comment=186267
  8. PIC programming question

    @Noise-Generator you are of course right my friend.. I spent way too much time trying anything and everything, except what was most obvious and directly in front of my face... Lessons learned... Fortunately, now I can say that I've walked through the entire end-to-end process of creating the Master and Slave PIC Cores, including bootloader, MIOS OS & MB-6582 specific firmware, as well as setting the proper Device IDs. I documented the experience here in case anyone else is interested: https://1drv.ms/w/s!AtmSvwylfFJaggnN1TtalEzGQK1C?e=sRlAiG (MS Word format). Cheers and thanks again!
  9. MB-6582 panel check

    Totally understood regarding the hard work... I really like what you've done though and I'd love to buy this panel set from you... PM me if we can make that work. Cheers, -Darrell
  10. SUCCESS! My hunched panned out... So now I have all cores working properly, with the correct Device ID's... Once again, in the end the process was simple and straight forward, but easy enough to get confused with...   For anyone that's interested in a step-by-step guide, here's what I did... Step 1: Write the basic bootloader to all 4 of your PICs Step 2: Place the PIC that will become the Master Core 1 into the correct Socket, launch MIOS on your computer and access it as Device 0 Step 3: Now you'll use MIOS to write the MIOS OS hex, followed by the setup_mb6582 hex. (more info for steps 1-3 here: (http://midibox.org/forums/topic/21324-change-pic-id-using-a-mac-for-mb-6582-core-0/#comment-186254) Step 4: Once you're done with Core 1, you can test your control surface navigation, listen to the default patch sound, etc... Step 5: At this stage I chose to remove Core 1. I didn't want MIOS to be confused when I added in Core 2, which will have the same Device ID 0 (not sure if this step was necessary though?) Step 6: Place the first Slave, Core 2, into its proper destination socket. You'll need to move the J11 jumper to position 2 to enable MIDI out to come from Core 2. You'll also need to move the LCD cable to J15_CORE2 so you can watch the screen through each update phase Step 7: Power up your MB-6582, MIOS should see Core 2 as Device ID 0 now. You'll change Core 2 to become Device ID 1 by using MIOS to write the 'device_id_01.hex' file that comes bundled with 'change_id_v1_9g.zip' (available in the troubleshooting section http://www.ucapps.de/mios_download.html) Step 8: Your device should reboot after you've written the device_id_01.hex. When it comes back online your LCD should show "New ID Header: 0000000000000001" - you've done it! MIOS should see Core 2 as Device ID 1 now Step 9: Go ahead and write the MIOS OS and setup _mb6582 hex files, to device ID 1, just as you did for the Master Core 1 ...Now you'll basically be repeating Steps 6-9 for each of the remaining Slave Cores...   Step 10: Power down your MB-6582 and add Core 3 into its proper destination socket. Move J11 to position 3 and the LCD cable to J15_CORE3    Step 11: Power up and do the same as Step 6, using MIOS with Device ID 0, you're ready to change Core 3 to become Device ID 2. Write the 'device_id_02.hex' file you downloaded with the change_id package Step 12: When your device finishes rebooting, your LCD should show "New ID Header: 0000000000000002" and MIOS should see Core 3 as Device ID 2   Step 13. Go ahead and write the MIOS OS and setup mb_6582 hex files  Step 14: Power down your MB-6582 again, add Core 4 into the proper destination socket, move J11 to position 4 and the LCD cable to J15_CORE4   Step 15: Power up and do the same as Step 6, using MIOS with Device ID 0, you're ready to change Core 4 to Device ID 3. Write the 'device_id_03.hex' file you downloaded with the change_id package Step 16: When your device finishes rebooting, your LCD should show "New ID Header: 0000000000000003" and MIOS should see Core 4 as Device ID 3   Step 17: Go ahead and write the MIOS OS and setup mb_6582 hex files Step 18: Power down your MB-6582, add Core 1 back into its lonely socket, move J11 to position 1 and the LCD cable to it's permanent home on J15_CORE1   That's it.. When you power back up you should have a full set of Master and Slave cores with all the correct Device IDs!   Moving forward, you'll never need to physically touch the cores and jumpers again to update the firmware. You can simply write new firmware to Core 1 (Device ID 0), then reboot while holding down the menu button, to automatically clone to all slave cores (magic!).    Word Doc with full procedure here for offline reading: https://1drv.ms/w/s!AtmSvwylfFJaggnN1TtalEzGQK1C?e=D6UJrH Cheers!      
  11. @Noise-Generator yet more useful info, thanks... I've been digging through so much online material that it's clearly started to clog my brain and prevent the facts from making their way in! My MB-6582 contains 8 x 8580R5's, so the ability to clone across all cores whenever a new firmware comes out, would actually be really useful. I'd prefer not to have to touch the hardware again. The piece my brain is struggling with is, at what point in the process of creating the Slave cores do they receive their unique Device ID?  I have a hunch that I should have been using MIOS to apply the device specific hex files, instead of my PIC writer... I'm going to try that now... (fingers crossed)   
  12. I'm actually having this issue right now (almost ~5 years after this post originated ;-) I tried writing just the basic bootloader hex to each PIC, then running through the clone process (press menu button while powering on), but this fails for me every time, exactly the same way as in the original post...  Following the advice here, I tried the same approach that @EsotericLabs has outlined, of burning the basic bootloader to each PIC (e.g., bootloader_v1_2b_pic18f4685.hex) then moving them, one-by-one, into the Core 0 socket in the MB-6582, so that I could apply firmware using MIOS (e.g., mios8_v1_9h_pic18f4685.hex). That process worked fine, but once I moved the PICs into their correct sockets, MIOS couldn't see them as Device ID 1, 2 or 3? In a separate thread, there's discussion of having to use "change_id v1_9g" to change the default Device ID of 0 that the PICs receive with base bootloader image. The 'change id' package even contains new hex files with names like device_id_00.hex, device_id_01.hex, device_id_02.hex, device_id_03.hex. I've tried to use these in place of bootloader_v1_2b_pic18f4685.hex, but this didn't help.  MIOS can communicate perfectly with my Master Core 0, but it's unable to see any of my Slave cores over a different Device ID. BTW - I can confirm that I've been moving J11 to correspond to the Core I wanted MIOS to be able to communicate with. ...So basically, I still haven't been able to create Slave Cores. (uhg!) Any suggestions are appreciated.
  13. Change PIC ID using a Mac for MB-6582 Core 0

    OK, OK, OK... After several days of mind bending torture, I finally figured it out... And it's actually extremely easy... DOH! Step 1:  Write bootloader_v1_2b_pic18f4685.hex to the PIC using your favorite Microchip utility (I used MPLAB X IDE, others like IPE Pickit Programmer, etc.). Step 2: Load up MIOS (I'm using v2.4.9). It should detect the PIC as Device 0 (default behavior), then you can write mios8_v1_9h_pic18f4685.hex (both hex files above come from 'mios_v1_9h.zip' available in the Operating System section of the downloads page: http://www.ucapps.de/mios_download.html) Step 3: If all goes well, your LCD will show "READY." (a cute throwback to the old C64 days), then finally you can write setup_mb6582.hex Step 4: When your system finishes rebooting, it should be ready for control surface testing...   Big thanks to @Noise-Generator for keeping me sane as I careened off one cliff and onto another... Wheew...   Special note: I wasted a ton of trial-and-error-time time before I finally realized that I had one bad PIC in my batch.  Newbie brain + fat fingers mean, I probably installed it backwards into the chip writer one too many times or maybe I exceeded its natural rewrite threshold, etc. I was always able to write the bootloader to it, but MIOS would never detect it. I didn't have enough experience with the process to realize that I was working with a dud...    In hindsight, a telltale sign to remember is that every LED on the control surface was lit up when this PIC was in the Master Core 1 socket. This is what you would see if you powered up with no PIC in the Master Core 1 socket. With a properly functioning PIC, you won't see any active lights on the control surface until the setup_mb6572.hex is installed... Mentally filed under lessons learned....  
  14. Change PIC ID using a Mac for MB-6582 Core 0

    I wrote bootloader_v1_2b_pic18f4685.hex to a different PIC (using the IDE) and was finally able to get MIOS to recognize it as Device 0. I was also able to use MIOS to write setup_mb6582.hex - Progress! However, my control surface and LCD still aren't working? - Torture!   
  15. Change PIC ID using a Mac for MB-6582 Core 0

    First off, thanks for riding this rollercoaster with me. In the end I'm sure it's a case of "user error" ;-) I think I need to burn three hex files to get the proper bootloader  ('bootloader_v1_2b_pic18f4685.hex', 'mios8_v1_9h_pic18f4685.hex' and 'device_id_00.hex'). The default behavior of the IDE is to erase the PIC before writing, so I either need to figure our how to turn that option off or somehow combine all three files together and write once? Hope I'm pointing in the right direction now ;-)