All Activity

Hi @TK. A great alternative for this would be to have the active SID led 'flash/dim' whenever there is midi activity like this is done in the FM v1. (instrument 1/4 led flash/dim) Would that be a feasible option (both programming wise, as resource PIC wise)?

my problem was a bad driver chip on the bhp_seq interface board....

Hi Keeze, I am not sure how, but I missed your offer. Many, many thanks, but sorry again for missing your response. Currently I am running with 2 blue modules, and my problem was solved by replacing the driver IC on the mbhp_seq interface board. So many thanks for your offer, and unless your are going to scrap our lcd's, I am not in a need anymore.

I just shared this thread in the Discord channel. Maybe that helps. At least there are knowledgable people there :-) Also tried to find some clues in the code, but this is hard for me. I did find something interesting (not sure if it is relatated at all), in src/cs_menu_leds.inc Searching for the word 'TMP5' shows in line 127: 127 ;; TMP5[5..0]: LFO waveform and in line 159: 159 ;; TMP5[6]: SID play state So in this file it looks like it's structured, but is the 'array' [5..0] correct? Should it be [4..0], and should there be a separate section for TMP5[5]?

Hello acfnews, Thank you for your reply and your test. I suspect that the LED would indicate the positive range of the currently selected LFO. That would make the most sense to me. In some pictures and videos, I find SIDs that have this LED installed. But I have not seen it light up in any picture or video. Perhaps someone who has installed this LED and has it displaying something can say more about it. If you find out more or get the function to work, please let me know. :-) Best regards, Oli

Hi Oli, I just stumbled upon your question, and I never considered this function, however, it might be interesting... My first question would also be, which of the LFO's would it indicate, as there are 6? Is it a sum? Not sure.... As a test I configured my ASM file, and added a line for the function (and removing a working function from the hardware position just like you did). In my case the first SR1,0 (normally used for SID1 LED indicator). DOUT_ENTRY TMP5, 4, 0, 0 ; LFO Random LED DOUT_ENTRY TMP5, 5, 1, 0 ; LFO positive LED ;; additional LED functions which could be added: However, on first test, no magic....` I will also have a look to see if I get thus going in a way...

Many thanks for the quick reply. Yes, I sent another function to this LED as a test and it then worked without any problems. So I can actually rule out everything on the hardware side. Unfortunately, I can't find many SIDs where the LED is used. I also couldn't find any videos on YouTube where someone has installed this LED and you can see it in use. In my *.asm file, the DOUT line looks like this (Shift Register 6): DOUT_ENTRY TMP5, 5, 6, 7 ; LFO Positive LED Is that all I need to enter for the LED function to work?

Have you used the diode test function with your multimeter to see if the LED illuminates? First thing I would check is if the anode and cathode are in the correct holes or if the LED is dead.

Hi, I'm currently building a MIDIbox SID V2 with the complete Control Surface. Everything works great, except for one thing. The additional ‘LFO POSITIVE LED’ never lights up. I can rule out errors on the hardware side, as I have already assigned ‘TMP5, 5,’ to other DOUTs and the LED does not light up then either. However, other functions are displayed on the outputs without any problems. I have of course already changed the LFO DEPTH and RATE. With positive LFO waveforms, for example, Random + Sine lights up, as described in the manual. Can anyone tell me what the problem might be or does something else need to be changed in the code? Thanks!

Absolutely beautiful build and much more affordable front panel design also. If you could upload the STLs to the MB-6582 wiki page under the "Panel Designs" section it would be the best place for them: http://www.midibox.org/dokuwiki/doku.php?id=wilba_mb_6582 Otherwise they will not be preserved for future builders.

the rest off them are now sold to @wlinart can be closed - thx.

DM sent

First of all sorry I am replying to an old topic. I hope there's still someone reading this topic and able to help me. Many, many years ago I built an MB-6582 with 8 real 6582A chips in it. I use an original C64C powersupply. I love my MB-6582 but it's a bit to noisy for my taste. So I'm considering buying 4 ARM2SID's to replace my 8 real sids. I think that would make it a lot quiter. If I understand correctly the arm2sid only requires 5 volts. I am not very skilled in electronics (when I built it, I simply followed the steps). I suppose I can still use my current C64C power supply, but I also read they can destroy sids (or more) when they fail, which is not very unlikely after more than 40 years. So with the new arm2sids I think I also want to replace my power supply for a modern one. Can I simply buy myself a 5V power supply and attach that to the 5V pin (number 5) of the power connector and also connect the ground pins? Or do I have to remove components from the board. The benefit of not having to remove components is that I always can decide to put back the original and use my original power supply. So what would be the simplest way to use a new 5V power supply with my arm2sids without having to remove a lot of components from the pcb? Are there schematics of the MB-6582 somewhere on the net so I (or a skilled friend) can look at the my whishes with the power supply? Also I considder recreating the control surface, because I'm not happy with the way I constructed it many year ago (the leds are not equally leveled). I think it's hard to remove all the leds. Can I still get the control surface pcb somewhere?

I have DM'ed for a PCB Thanks

I am trying these as they are similar but a little smaller - will update if they work… https://uk.rs-online.com/web/p/memory-card-connectors/7636794 EDIT: It works fine - but footprint is a bit smaller so may need gluing as well if the card is going to be removed often.

Does anyone have spare sd card holders for the core or a suggester part substitution? (It is actually for a different pcb but is the same part as used on the stm32f4 core) 3M have stopped manufacturing them and I havent found an alternative that is the same size as SD-RSMT-2-MQ or SD-RSMT-2-MQ-WF ( I have found 9/11 pin versions which are shorter with different positions for the mounting tabs). Thanks a lot.

Thanks a bunch, stever! Looking forward to try it later this week when I return home. f

Prompted by a message from freddy, I've attached the project files below. They contain the source and the binaries for the bootloader and the main code. 1.05 is the latest version - there was a fix in the bootloader and the main code. I included some memory in the final hardware design but never got around to doing anything useful with it. I had plans to save one or more demo tunes as MIDI files and perhaps save some settings as profiles for different scenarios - my interests had moved on before that happened. You can find more project info at https://web.archive.org/web/20210206041027/http://www.grapevyne.com/pic.projects/ - the documentation links are all active so you can download the magazine articles and also my original source for the articles (a few errors crept into the magazine article during editing). mistralXG project files.zip mistralBoot.zip

I designed a box in FreeCAD. The box lid clicks to the box, so it is easy to open and close it. I added a switch to connect Midi 1 with Midi2. You can download the files at weigu.lu: https://www.weigu.lu/music/midibox_hp_2x2/index.html

thank you for your numerous answers, i will try to get it right when i find the time, br ranger930

Sorry to revive this long-dead thread after almost 13 years, I had MistralXG project on my to-do list for more than 10 years and I finally got to make the PCBs. Alas, meanwhile, Stever's website is down and Wayback Machine (https://web.archive.org/web/20210206041027/http://www.grapevyne.com/pic.projects/) only stores the primary site, not the linked images or other files. That means that I'm left with no firmware - anyone still has the binary HEX for PIC 18F2550 with (updated, based on the archived webpage contents, it should be v1.05)? Or even the sources, maybe? Thanks, freddy

i jst saw that tk answered the same question regarding mios8. The same should apply here. It works alsmost like the code i suggested above, with one big difference: I was suggesting a global variable. That does work, but is usually a good idea to avoid. The neat thing i just learned, and since we are both learning i like to share this:: What is a static variable? It is a variable that will be created once and not change over function calls. So if the code below would read "unsigned char ain_sent = 0;" without the static keyword, the variable would be recreated every tick and midi would be sent every ms. With static, this variable will be created once inside the function block (so it is not polluting the global namespace). Next time it will be 1 and the condition in the if statement will fail. ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS in the mainloop when nothing else is to do ///////////////////////////////////////////////////////////////////////////// void Tick(void) __wparam { static unsigned char ain_sent = 0; if( ain_sent == 0 ) { unsigned char pin; unsigned char num_ain = MIOS_AIN_NumberGet(); ain_sent = 1; // only sent once after startup for(pin=0; pin < num_ain; ++pin) { MIOS_MIDI_TxBufferPut(0xb0); // CC at channel 1 MIOS_MIDI_TxBufferPut(pin); // pin number corresponds to CC number MIOS_MIDI_TxBufferPut(MIOS_AIN_Pin7bitGet(pin)); } } }

it´s in the manual under din http://midibox.org/mios32/manual/ I cannot try this right now, but i would assume something like int my_button = MIOS32_DIN-PinGet(0); will save 1 or 0 to the variable my_button. But again, if you have a normal "digital" push button this will only work while the button is actually pressed.

s32 MIOS32_DIN_PinGet (u32 pin) With this function you gen poll the state of a din pin, eg when using switches in your setup.

The thing is: With all digital inputs you cannot get any state UNLESS a button is pressed. It would be different with actual switches that hold their state low or high. But a button or encoder has no permanent state. When you press or turn it you get a pulse that will trigger the mios callback routine. Thats it. So the direction you should be looking is to save the last state of all buttons and encoders in your code, and load it on startup. Unfortunately i am still a noob, so i cannot really tell you how to do that. But there is some example code for sd cards and bancsticks.