• Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About borfo

Profile Information

  • Gender Not Telling
  • Location Toronto

Recent Profile Visitors

545 profile views
  1. I'm trying to program four PIC18f4685's for my MB-6582 from scratch, and I'm having problems...  I seem to have at least sort of successfully flashed the bootloader using a Pickit 2 and MPLAB X, but I can't flash MIOS to the SID over MIDI in MIOS Studio.  I can query the core, and it says the bootloader is running, but whenever I try to flash any .HEX, MIOS Studio times out and says "no response from the core after 16 attempts. The Core is sending out these messages (which I guess is the upload request) about 120 times a second all the time the SID is powered on...  From other forum posts, it seems this is way too fast - should these messages be sent that often, or is there something wrong with the clock speed on the PIC or something?  Anyone have any thoughts?  Voltages seem fine on the PIC... [25442.111] f0 00 00 7e 40 00 01 f7 [25442.120] f0 00 00 7e 40 00 01 f7 [25442.128] f0 00 00 7e 40 00 01 f7 [25442.136] f0 00 00 7e 40 00 01 f7 [25442.145] f0 00 00 7e 40 00 01 f7 [25442.153] f0 00 00 7e 40 00 01 f7   I've never used MPLAB or flashed a PIC before, so it is possible I didn't flash the PICs correctly...  (although MPLAB said the flashes were successful) Is it possible that flashing the bootloader in an incorrect way in MPLAB could somehow make the PIC's clock go way too fast? Or, is it possible that the circuit I used to connect the PIC physically to the PICKIT 2 could have been incorrect in a way that could make the clock speed go way too fast?  (there is a pcb with the PICKIT that fits smaller PICS and connects to the PICKIT - I just connected the appropriate pins on that pcb to the pins on my PIC18F4685s via breadboard leads.) ...even thought MIOS Studio reports that the bootloader is running when it queries the core?   Is there a complete HEX of the MB-6582 PICs that I could try flashing in MPLAB so I don't have to install MIOS via MIDI?   Any help or pointers would be much appreciated. 
  2. Cool - have fun!   Out of curiosity, did you try installing pyBLM on windows as well?  I'm assuming you didn't, but if you did, how did it go? 
  3. Hi - I think I've tested it on a raspberry pi...  It should work anyway.   ...Are you sure you're installing Mido into Python3, not just into Python 2?  Try "pip3 install mido" and rt-midi...  If that doesn't work you You might also try installing as your user rather than sudoing it.  You could also try installing python3-mido and rt-midi from your package installer (if they're there) instead of through pip.  
  4. You could try the python BLM implementation - if you do, let me know if it works for you:  edit:  Oops - didn't notice that you were already aware of the python BLM thing.  because the virtual BLM and pyBLM use totally different codebases, I thought the issue you're having under the virtual BLM software with conflicting device names might not occur with pyBLM.  Might be worth giving pyBLM a shot now rather than trying to work out the issue in virtual BLM if you're planning on using pyBLM anyway.    ...pyBLM should work in windows too, I think, provided the dependencies will install.
  5. Thanks everyone - I'm not sure they're fried, but they're certainly corrupted, and the bootloaders on all of them are no good.  I think I overvolted the board while I was impatiently trying out some ill-considered power supply ideas after my commodore 64 psu arrived DOA.  I tried flashing one with an arduino PIC programmer circuit I found on the internet, and the burn failed.   I've found someone local to borrow a Pickit 2 from and I'll try reflashing my existing PICs...  If that doesn't work I just bought four compatible PICs for cheap on eBay, so I should finally be able to get this thing working one way or another.
  6. I just found 4 cheap PICs on ebay actually...  I'm in Toronto, Canada - probably easier to figure out something local rather than sending PICs back and forth to Scotland.  Thanks a lot for the offer though.
  7. I think I fried mine...  Does anyone have an extra set?  Or some extra PICs that you could program for me?
  8. midibox stuff pic programmer, core, lpc board LCD

    [Deleted message asking about PICs to replace the corrupted ones in my MB SID] Edit:  Nevermind - I just found a cheap set of PICs on ebay.
  9. Older pics programmer and book on programming

    Hi - I have to get a pic programmer anyway to fix my MB SID...   What would shipping to M6H1N2 in Toronto Canada cost?   Are there any PIC18F4685's in there?
  10. (WTB) Seq V4 parts ( 2 raystar oleds for trade )

    Hm.  If I don't get rid of the frontpanel PCB I shouldn't get rid of the parts either...  I could still do the LPC17 core if you like though.
  11. (WTB) Seq V4 parts ( 2 raystar oleds for trade )

    I have a PCB for Wilba's Seq v4 frontpanel, new, nothing soldered to it yet.  I have other parts as well that I could probably part with...  I have a set of the rotary encoders and a set of the bicolor LEDs...  A datawheel knob... I have an assembled LPC17 core that I could get rid of as well - it's a totally functional core for the time being, although as the SEQ forks off into the V4+ you'll miss out on some functionality down the road.  You can always upgrade the core though. I could put together a set of knobs that would fit the encoders, but they're potentiometer knobs, so they've got that position indicator stripe on them, and I might have to mix up colors a bit, not sure if I have 16 of any one color...  Anyway, not the prettiest knobs on the block, but they would work. I have an assembled STM32F4 core as well that isn't being used right now, but I think I want to keep it. What color are the OLEDs?  Where are you located? Anyway, let me know if you're interested in any of that.
  12. Since the MBSEQV4+ is imminent, it would be great if all of the standard button functions on the SEQ and whatever new functions will be on the new V4+ were made accessible via MIDI, with LED feedback signals to allow fully functional MIDI interfaces to be built.  Right now, a lot of SEQ functionality is accessible via CC, SYSEX, and NRPN, which is great - don't get rid of that stuff.  But there is no LED feedback signalling which would allow illuminating buttons on MIDI devices just like the buttons on the standard SEQ.  (Like the GP buttons, for example - on the SEQ, they light up in color - unless I'm mistaken, there's currently no way for a MIDI controller script to receive lighting signals for any of the buttons. Take a look at the picture attached to this post - two Novation Launchpad Minis line up perfectly with the 16 GP buttons and knobs on the current SEQ -  the launchpad works as a BLM already - if there was midi access to the button functions and lighting, we could build SEQ V4+'s with just the 40x2 LCDs and one row of encoders - all the rest of the button functionality could be offloaded onto the Launchpads.  (or onto any other midi controller, for that matter), and if LED feedback worked as well, MIDI devices would work just as well as DIY hardware SEQ interfaces...  For those of us with midi controllers sitting around, this would allow some pretty neat designs at very low cost.   It would be great if you could configure MIDI connectivity in the MBSEQ_HW.V4 file - so that all of the hardware buttons you can configure for DIY hardware could alternatively be mapped to MIDI right in the hardware config file (or maybe in a MBSEQ_MIDI.V4 file or something. Anyway, given the extra capacity on the V4+ core, I thought there might be room for this sort of functionality...
  13. I've printed a first batch of these boards, and have assembled a couple.  Haven't had time to test them thoroughly, but I figure I may as well post the Gerbers anyway in case anyone wants to print some.  Let me know if they work for you, or if you find any issues.
  14. kicad schematic files for MB modules?

    I've built modules in Kicad from the schematics on from scratch - just copying the schematics into Kicad.  They're pretty straightforward, and the copying exercise has been a great way to learn Kicad. If you're interested in DIN or DOUT modules, I could send you my kicad files for this board if you want:   
  15. R3 DIN Printed Circuit Board or Kit

    I've got a bunch of prototypes of this combined DIN/DOUT module board that I made...  Haven't tested it thoroughly yet, but it should work fine.  If you want to try one of these boards I could mail you one.  $5 +postage? Alternately, ucapps has board files and schematics.