• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mex

  • Rank
    MIDIbox Newbie
  1. sidbox does not send sysex (on patch dump)

    just a quick update, as i purchased the plyotec gm5, around 30€, it is working now, so maybe it really was the cheapo usb buy from amazon, amybe something else, but patch upload does work now :)   so maybe this helps everyone :)
  2. ok everything is working fine, just finished screwing the stuff together, now MIDI Ports are missing, and then I am ready to go, think they are still on the way from modularaddict, but igot some IIC MIDI outs with the PICs on, maybe ill try those first as long as the midi is on its way.    
  3. Update #1: got the testprograms running the: wilba-seq-cs-hw-test-blinking.hex   so i know my encoders do all work, but the buttons do also work, but i dont know the exact numeration and if its important?   for example in the pdf the bottom right button is named: S51 and the LED is L51 But the program tells me it is Button Nr.6 and Led Nr 51 is the green one above the song button, in  the pdf named: L20   i dont know if that should be aligned, anyway i keep testing.   i dont know exactly how to flash back another testfile into the STM32 :) mios is not detected , hm maybe i need to flash it again, but i cant imagine that, i will keep on trying.
  4. got it working, but thanks for reading, i was a little fast, but you know how it is, just writing about my problems usually gives me another point of thinking about it, so the LCDs are working, now i am a bit struggling with the menu pages and wheather my fronpanel is working , i guess it should not work at all if the SI SO would been in wrong alignment,?   ok i think something is not yet working, maybe its a simple thing like , wrong file on the sd card. Then i think my rotary encoders have wrong detents, and i have not quite figured out which LCD is the left and which the right? I assume the logo appears on the right one on startup. My buttons dont seem to work , but it could also be that i simply dont understand the usage yet, I did try to do the thing from the beginners guide: press menu and events... but somethign else is happening, And yes i think something is fishy, when i press the Divider button ( 5  or E ) the right diplay says:   step view 113-128   so i think something is wrong, i will check on how to get the file to the sd card again and hope i will have it all working in an hour :)    
  5. #Update 1: working now, did forgot to solder the R33 resistor network on the bottom PCB under the STM32F4 eval board... silly me This tends to happen quite a lot to me when i have half finished projects lying around everywhere. So LCDs do work sweetly, but do not know exactly if the wilbas frontpanel is correctly working, seems quite random some of the led pattern, but i will have to look into that when i finish ubilding.     Hello, as i did finish my MidiBoxSid  a while ago, I did follow the advice of some other member here and looked into the MidiSeq v4. So i simply ordered all the stuff, or had it at home anyway. Now i am running in some issues, which are probably easily solved by some of you guys who already have one:   So My MIOS32 bootloader did flash on my STM board easily without trouble, I can also detect and upload the MidiSeq newest firmware, and it is read by the MIOS studio software, it says 1 minor issue was detected while flashing, but also states that it could be solved whatever that means, so I think everything might be ok with the Code. I can also open the MIOS file viewer and see that something is stored on the sd-cardm so I assume everything is working properly, right?   Now I did attach the Wilbas Frontpcb and the 2 LCDs, some from newhaven ordered via mouser, they run on 5V and the rest should also be connected fine :) at leats i do hope so right now, I did go thru the cabling quite a lot since it is kind of tricky since it is mirrored and stuff.   When I connect the USB cables for power then the backlight is lit on both, but i only get dark rectangles on the upper collumn, I thought maybe the midibox logo or version number should appear and so on, so something is not working right yet.   So here the big question? Do i have to configurate something else? The LCDs should work without any Front-PCB attached, right? since they are not connected whatsoever. Why do my LCDs not show the right things, maybe wrong LCDs, but I assume mouser is only providing the "right" ones. maybe some file missing on the sd-card, but it should simply work without the sd-card, right? I mean for testing something should be printed on the LCDs?   MIOS Studio is stating that the right seque code is detected, so there should not be a problem with that, maybe i simply flash the bootloader again later and go on form there, check all the ICs.   And last question, the J8/9 cable, goes 1:1 to the mirrored plug form the frontpanel, or does it have to be mirrored just liek the LCD type??? This is specially confusing to me since it is not clear if SI is supposed to go on SI, or like ususally in communications, SI is going to SO! Kind of tricky to document too,but luckily nothing be damages if this connection is wrong it simply wont work.     Thanks for reading and probably helping. cheers.  
  6. sidbox does not send sysex (on patch dump)

    oha still alive, did not believe this :)   My next step is to buy a new usb to midi converter for the PC and then try again, i am using a ultracheap china clone sub 10€ bought 10 years ago or so, but i could flash my midibox without any problems with this thing and MIOS studio also seems to work as it detects a running application and stuff. I did use win7 and win10 to try it both with the same errors as you got.
  7. sidbox does not send sysex (on patch dump)

    sorry to necro bump this old thread, but i am having the exact issue, maybe maybe someone found out a solution for this, as I really would like ot use this librarian feature of the MIOS. Thanks a lot.  
  8. MidBox SID Core Module schematic

    quick 2 pictures, I got the front lasercutted in our local fablab, very nice word, maybe i get a real wood, but for now i really like the used look.   Just a minot thing, the 4 buttons besides the LCD do not work like printed, i thought i read somewhere how to change it in the assembelr or mios, i got to look back again or someone points me ot it.   When i press up, its going down , but maybe again this is intended to do exaclty this. Ive been playing around quite a bit, i gotta admit its right now a very special sound, i like it  a lot, very versatile, have been using mutable quite a bit, ambika and shruthi, but the SID is a killer.   baseline is really nice, too. SO far the drums are only the initial patch, i need to get my own or downlaod some for the future, did read something about other patches, but did find them yet.   One thing, I think my pic1 is always doing some sound when pressing the play button, that is not really nice, but i will see how that plays out, maybe my one SID has an errro , or the pic, everything else behaves just fine, I think. My future use, will be send some midi clocks and notes, and not use the internal play mode, so maybe it works around that problem.   Great project, great work, looking forward to inspect the midi code and reuse it in my own projects.   Will ordersome new PCBs to be able in some boring moment, to built another one :)  
  9. MidBox SID Core Module schematic

    yeah i read that one for a bit, though a internal passive mixer is already on board, do you know that? I use that output for testing, but do not know how i plan for future use, since my 16channel mixer well already is kind of used with a lot of stuff, so additional 8 channels from the SIDs does not make sense to my setup.   And a quick maybe solution to your swinSID sound problem. I do leave both jumpers off the SwinSID boards, one should emulate for 8580 sound when plugged, the other one will put an additional 1k to ground into your audio out signal path, you dont need that one, since there is already a 1k on the wilba PCB, if you connect the swinSID jumper in, you will halfe that 1k, since they are paralell. Effectivly halfing your audio signal too, so there might be the problem, of course easily repairable jsut unplug the jumper. If it is not that problem, well you have to do some troubelshooting :)   And yeah i also get some VCA bleeding and backgroundnoise on the 6581, the 8085 is much quieter, and swinSIDs are simply not as high of output level, i thought about putting a small opamp buffer int here with gain of 2, maybe i will do that and post the brd files, but not in the near future :)
  10. MidBox SID Core Module schematic

    so far so good, yeah sounds playing, can püaly sound over MIOS and the respective MIDI channels. So far so good, can only say as I got one 8580 9V plugged and one 6581 12V, they both seem pretty similar, so far cannot hear any difference when unplugging or plugginh the filter caps, maybe they will be important in some other modes of playing. another fun thing, the 12V 6581 I did let run from 9V out of fear that it could be the wrong, it sounds a little bit more weak than with 12V, but works just fine, of course it is probably not recommended to run it with 9V, that was just for testing.   And no surprise, the swinSID nanos, just soudn way weaker than the original sids, so no chance to mix them otgether, well over seperated inputs to the main mix it will work out just fine, but right now for testing i got all over the passive on board resistor mixer ocnnected ( well done btw very nice feature for testing purposes) it is really hard to find the right cables these days :)   So mybe i buy another set of PCBs and hunt down 6 other SIDs during my lifetime :)
  11. MidBox SID Core Module schematic

    UPDATE #1 I followed that one and got it working i think, so cloning is NOT working properly in the wilbas mn6582 I would assume right now, but its easy to fix, just placing the Jumper on J11 on the device you wanna flash via MIOS and then send the mb6582.hex to the PICs one by one, beforehand i switched the device IC, cause this part is not altered by the flash process. Sweet sweet bootloader and MIOS flash tool, I love it, works like a charm, who needs cloning with that anyway :)   Ok. got the whole thing working, did not really test the sid sounds yet, and only the first two sids have been tested for the audio amplifiers, but i am pretty confident it will wokr out, or at least i know where to fix the others since i got some of them working :)   I thought i could clone whatever program there is on the first sid, stupid me, i assume this only works with the actual midibox sid program, not with the audio test program. Well i stuffed in the other 3 PICs, had to search for the menu button, shockingly thought to mayself maybe i should have installed a switch endocer as menu encoder and not the one without switch, but turns out there actually is a menu button right under the decoderto the right. So then I did clone the mb6582 hex file to all the other SIDs, in the display some strange stuff like 0D!!!! was presented, maybe that indicates that something is wrong??? I will find out later, then i just randomly clicked stuff in to test a bit around, at startup i can hear some sounds, after that I do not know yet how to produce sounds or maybe even program a sequence in it, but i will find that out later.   Also a minor other thing, when i connect the LCD to the other PICs J15, just the PIC device ID 1, 2, 3 is shown in the LCD and no background is lot, as those pins are not connected according to the board file..
  12. MidBox SID Core Module schematic

    hi great news with your deivce, congrats, looks and sounds pretty convincing.   And thanks for all those information, I kind of already have read over that, and I did not mean the J11 jumpers but the J11 Core jumpter, i dont really get those as one can short the tx rx from the PICS.   Anyway, did oyu mean this hex? setup_mb6582.hex ? I will try now to flash the MIOS again and then upfinally recognize it with my MIOS on the mb6582 board, will also probe around witht he scope if it wont work, but i am pretty sure MIDI is working just fine until the PICs. Since my hardwareloop is recognized and I get the sysex message out: [300922.170] f0 00 00 7e 40 00 01 f7 every second or so   edit1: short update, I did get another badge of fresh PICs yesterday via the nice microchip sampling service, cause I thought, maybe i messed up with some configurator bytes? is that even possible with the pickit programmer and the diamex??? I am only very very familiar with code composer and the  Texas Instruments controllers, Atmel I had before because of the great work of Oliver at mutable instruments. What puzzles me a bit is the complicated way Atmel works with its fuse and other settings, with the Texas controllers you just flash a hex file and everything else you dont have to care, or someone else already took care of in the code, Atmel you have a working hex files but the code wont work because someone forgot to tell you about those fuse settings... seems kind of unnecessary ot me.   So because of that expirience I wondered or still wonder, is it the same with the PIC, can I possibly mess up a perfect hex file with wrong config bit settings, I read :   and there it at least says so.     So enough of my rant back to business:   I did flash a couple of those PICs I got, btw i also got some PIC18LF devices, are those the same, what does the L stand for, at least i could flash them also. Now after yesterdays struggle I think something might have changed in my connections ( I am programming on a prototyping solderless board right now, so open connections and too much parasitic capacitance could actually be a thing), because now the hex code seemed to work fine and I can now also verify the program ( I assume the pic program checks if the actual code on the PIC matches the imported hex file from my PC )   Then I connected the PIC back into the core module, startet Mios.exe and a couple of times the same as yetserday no MIOS detected and so on. I also flashed the troubleshoot PIC code on one device, strangly no echo occured, BUT the one pin on J14 I think toggled when I did send a random code over the MIOS, so flashing probably works I thought. Well after some more fiddling, the first time the upload of the mios hex file did work, it stated MIOS8 detected, that was on device id 0, then i switched on dev 1, it did not detect anything, then back to dev 0, again no mios detected, hmmm. But anyway I assume MIOS studio got some issues for itself, and i cannot blame it its hard to program communication stuff on pc and midi then having to rely on some external cheap chinese midi gear like i got and so on. anyway after restart it detected MIOS8 again and so on, then i had to leave home for work, but the hopes are high to produce a sound until the end of the week.   And just a headsup, i inserted a pic wrong way around one time ( with 10 pics and on and off troubleshooting and all quick and on a messy workbench, this is 100% sure to happen to anyone :) ) just wanted to say i "think" it is still working, at least i could reflash and verify it.   thats all for now.  
  13. MidBox SID Core Module schematic

    Just beeing able to flashing my pics..   i dont know exactl yif it worked, but the pickit kit says so, i cannot verify this, but anyway i gotta trust something.   Now i did want to update the mios on the pics in my PCB setup, but sadly the MIOS is not recognizing my midi PICs yes. Does someone know what the hell J11_CORE is for? Is it just a bridge from MIDI(UART) TX to RX? I had that jumper set all the time, to it was kind of a short, i hope i cannot damage the output pins with that.   I can test a feedback loop just liek stated in the troubleshooting, but my PIC MIOS is never recognized yet. Just spent 2 hours of my night to get it working, also tried my older PIC18F4620 setup, doesnt seem to recognize it neither, but i know that that one worked like 4 years ago :)   THen something odd happend, i was pulling and stuffing the J11_CORE in and out while querying to see if i can can loops, and indeed it happend, and surprise in the beginngin one time he also stated MIOS recognized, but of course i cannot work with that, as it vanished when i pulled the J22 again or stuffed it back in.   So the journy goes on. BTW brilliant written troubelshoot guide, really something to read acutually helpfull and sensible stuff, great work.   Right now i am suspicious of my noname midi interface, i got that from amazon a while ago for 7€ or so, but it did work for the last 'PIC and MIOS so im am not that sure, well maybe it works with notes but not with sysex, do not know that yet, i cannot recall if i bought a mios PIC back in the time or just a preburned one, but i think  i got it from the german site so probably only bootloader installed, which means mios upload did work once before, well maybe it is dependent on my win10 now, who knows..   Second thing, as i am not yet that familiar with PICs and i got myself of course the cheap diamex substitue instead of the pickit flasher, I am a bit suspicious about it. I am using the official microchip software for the pickit2 kit, and it states that my code is on the device, but i cannot see that , cannot verify it,the button simply says its not possible, i guess somehow the pic is not readable, at least that would make a bit of sense. So if the upload of the bootloader did not work, then of coursethe MIOS wouldnt work.   Which leads me to something new.. Is the pic supposed to be MIOSable if only the bootloader is flahsed the first time?? I would assume maybe not, hmmmmmm.   anyway it is kind of late, i am passed my sleeping window for 2 hours, so will inform you as soona s i squeeze the first bit of sound out of it.   cheers
  14. MidBox SID Core Module schematic

    just a quick updateon behalf of the lcd connection:   I can only detect D7 to D4 connected on all the 4 PICS to J15, the LCD port, is that true or some defect? I guess right now maybe the LCD is working in a different mode and those connections are not needed, did not power up yet to see if it is working.   Just noticed and thought hm this seems strange, will maybe come back to it when it doesnt work. On a sidenote on my original mike smashtv PCBs those pins were all correctly connected according to the uCapps website documents.   we will see how it works out. btw all the PICs did arrive , but i do not know if i can flahs them otday i think rather not, so i will test the thing with my old PIC and only 2 SIDs     PS: Edit#1 Just saw in the wilba design files, somehow it loads very unstable on my PC, ist a huge pdf or my pdf reader is broken, the baord file, and there it can be seen where those ocnnections go, so no probrlem after all everythign is fine
  15. MidBox SID Core Module schematic

    Quick update on my behalf. I dont know where i got the rotary encoders from, but it seems i can detent them by opening, so i will do so for 14 parts besides the main menu encoder, I hope this i sright, and nothing else will be used as an menu encoder. btw i think i got the one from the netherland   What stops me a bit is the missing frontpanel, maybe i will lasercut it in my local fablab, but i do not know if thta can happen in the next days, so i am a bit stuck with the led matrix, i would like to solder them when i know the front panel measures.   Today i orderedthe Pics and some more Amegas88 for the swinSID, at first i got some Atmega88V turns out the V variant is for probably less than 32MHz, the PA is also only 20MHz but will be driven with a 32MHz clock anyway, I hope this all works out, it is not my designs, someone else did those, so I hope it will work :)   For now I am probably trying to lasercut the fronts tomorrow, and will get the PICs flashed, when they hopefully arrive tomorrow morning. If that does not work out :) whihc it probably does not, recalling murphy, i got one PIC18F452, the one without CAN onboard, and will try try to work 2 SIDs from that one, just to get a proof that the whole thing works. Really looking forward to producing the first sounds..   Ah and btw I did recycle the original PSU socket and power switch from the original PCB by destroying it today :) Maybe i will try fitting in the midiBOX into the original case C64 as well, but I will decide on that later, making sound is more important right now, btw I saw your milled pictures, really looks beautiful. cheers