Jump to content

chriss

Members
  • Posts

    140
  • Joined

  • Last visited

Posts posted by chriss

  1. hi Thorsten,

    Yesterday i managed to work on my MBsid.

    The firmware for the slaves work so far, though it just react on note on/off when the menu is on Sid 1 and i can not change anything. It only plays the generic patch. I think thats because of the device ID.

    At the moment i don´t know how i can change the devicenumber.  When i go into the submenu i can only change the devicenumber of sid 1, in sid 2-4 submenu the field for the device ID doesn´t react and stays like that ___. i guess the core does not realize that there is a slave.

    Is the sid v1.4 default ID 00? Do i have to change it before i burn it? I read in the MB64 zip that the ID is not changeabel over sysex when connected to the to_com!

    When i send a ping to the box, with any ID, i get the same ID back (from 00 to 0F) The same when i try it with the device change syx. string. I just get the same string back. When i burned the bootstrap loader for the core i gave it ID 00, was this correct?

    Now to mios_v1_2c.

    Unfortunatly i couldn`t change the hex to syx. I really tried it two hours. but i only get weird signs in the command shell and the syx. file is empty.

    So no tests here. If you still want me to test the encoder handler (i read in an other post that you will release MIOS 1_3 soon), send me the mios_v1_2c as syx.file.

    thanks

    chriss

  2. hi Todd,

    "i guess I'm trying to make the ultimate step sequencer" thats what i thought and felt myself a littlebit stupid to tell you my plans, because thats absolute not ultimate.

    just having two rows of 16 encoders with ledrings. Two buttons on there site, changing (between note on/off and env depth for the first row, and cutoff and resonance for the second.

    And on row with 16 buttons. As well a button beside where you can switch between gate , accent and slide to be muted... and of course all the features TK is going to implement.

    All this is very simple and i guess i will rather stuck with your design. But as i said before this forum works like that and i shouldn´t be so shy.

    chriss

  3. hi nebula,

    just get yourself the free sofware from the schaeffer site and for example load the Mbsid v.3 (which is not recommended anymore) or draw a few circles by your own. Then go to "Preis berechnen" what means calculate price and the programm will calculate every single hole, adds everthing together (what is absolutly cool!) and stops for this panel at exactly 137,42 €.

    a lot, but doing it by your own costs more (time).

    chriss

  4. hi all,

    very cool that this topic come up again, in the meantime i was just designing some kind of sequencer based on theMbseq64 for my tb303 clone, because after using programms like logik for sequencing, i realized that i need something else.

    But my design is far away from yours stryd_one. so it is better not to talk about. and talk about yours since it looks very promising. can´t hardly wait that TK is getting out the Mbseq64 for MIOS and your design shows up. Unfortunatly i never owned a classical step sequencer (only an analog 16 step), so i am an absolut newbe on saving and editing and chaining patterns with buttons and encoders.  And i don´t  know anything about fruityloops so i have to see and learn. that´s good.

    so i am looking forward to see all your design implemtations and your panellayout.

    PS: You guys bring up the topic about the ML_303. A month ago I thought about getting a set cause i like the concept of the classical TB303 but i wanted to make some mods (i also like it when it also fits more in our time (display, etc.), and i like to design my own surface with my own buttons etc.)

    So i asked the site owner about getting the schematics and the code but his reply: thats not possible. I can understand this its very ok. it is a lot work to design a pcb and get all the parts and design the code, but it i is not good for the project though.

    I like this forum much more and i like TK for his long anwers and patience much more. And i like you guys for your great input.

    chriss

  5. Hello Thorsten,

    so these are my results:

    Did the quick and dirty and it works by stepping one with every second detent in the main menu and all others.

    tested the enc example #1 and i would say:

    non_detented mode: stepping two with one detent;

    detented: stepping one with two detent.

    0x81: stepping like detented

    So we need exactly the middle of both.

    funny though.

    Is there a difference in enc_example #2 and #3 concerning this issue? because i could try these as well.

    Ps:  Are you able to compile the PIC16F firmware with to-COM enabled for me? Maybe its usefull for others too.

    Thanks

    chriss

  6. hello Thorsten,

    i solved the MIOS 1.2 problem by reburning the pic. don´t know what went wrong but now it works. also the midi feedback problem is solved.

    Just another Question concerning the encoder mode.  

    As you may remember i am using the alps stec16b encoder like you i guess. when i turn it 360 degree it changes 36 steps. shouldn´t that be 72??

    And yesterday i got one stec11b which has an inbuild switch ( i want to use it for the menu and exec button), but it is detented.  so i changed the enc mode in Mplab and loaded it up. what comes out was that it only moves at every second step, and in the main menu only every fourth step.

    Then i uploaded the old version (non detented) and couldn´t see any difference?

    so how does this work actually? If on cycle is from low to high to low, then one cycle is one step or two? (with non detented) Because i checked today the alps stec11b with an osci  and every detent (raster) is half a cycle (changing from high to low for example).

    I already checked the connections and they are allright (ABC for stec16b and ACB for stec11b).

    Thanks for all that support and i hope we can clear things.

    chriss

  7. hi all,

    first i wanted to thank Thorsten for this inredible nice work.

    I took the chance to upload MIOS 1.2 with the new midi sid stepB application and my lcd still shows MIOS 1.1. I don´t know if this is an fault by Thorsten or the upload didn`t work. When i load MIOS 1.1 i can see after reboot >ready<, with MIOS 1.2 there is nothing on the sreen. I just have to power on the midi box, start midiox and send the new MIOS version. right? then boot again and send the application sysex.?

    The second question concerning the midi sid stepB application.

    Everthing is working ok so far, but there are some little questions. In local mode the box works like StepA only with midifeedback. thats very cool. But the lcd data does not change!!! So when i change for example the cutoff midiox is reseiving the data but on the lcd the value is not changing. when i close the midi input in midiox the lcd works fine again.

    Another problem which may have the same cause. As soon as i change to sid 1-4 the midi sid is sending a lot of data when i hit a note and never stops untill i change to local mode again.? Closing midi in port in midiox and everthing is fine.

    My setup is still using the to com interface. what me leads to the third question.

    Does the Pic 16f877 with hexfile sid v1.4 only work with midi baudrate? Where can i change that? otherwise i have to wait till the usb2midi is released and build.

    One last question about the hardware. whitch pins of the slavecore module can be left open or have to be grounded or need a pullup resistor.  i mean only these pins which are normaly connected to the I/O boards, bankstick, and lcd.

    Thanks and be ready for the stepD

    chriss

  8. hi

    just take some overhead foil (for laser printer), disable all layers in the eagle layer menu, then enable 16 bottom, 17 pads,  18 vias, 20 dimension, 39/40 keepout and go to print and check in the printer menu if black and solid is enabled and scale factor is 1; (you don`t need to mirror because you can turn the foil.)

    print.

    chriss

  9. hi

    just take some overhead foil (for laser printer), disable all layers in the eagle layer menu, then enable 16 bottom, 17 pads,  18 vias, 20 dimension, 39/40 keepout and go to print and check in the printer menu if black and solid is enabled and scale factor is 1; (you don`t need to mirror because you can turn the foil.)

    print.

    chriss

  10. hello

    Thorsten:thanks a lot for the reply.

    i changed the env sektion and it works. cool.

    concerning the knobs i called www.albs.de and its quite cheap actually.

    100 pieces of standard black knobs, 4mm flat type cost 26,90€ excl.Mwst.

    you only need to purchase at least 30 €. so you must take 100 or more.

    but if you take knobs from other companies like farnell or rs-components you pay1.50- 2€ a knob.

    so if you get 100 pieces from albs you can build on MB64, one MBsid and one MB16E for 30€. thats fairly cheap.

    chriss

  11. hello all

    first i want to give a small report of my MB SID so far. As for the moment i only tested the stepA and i am really exited. everething works apart from some minor problems.

    (i will refer to them later on). But  this is all nothing in comparison to what it can. it is really outstanding. And everthing can made so simple. You just have to read the hompage several times and the forum every day und with some patience and smartness you are in the MBclub.

    Big thanks to Thorsten!!!!

    My way so far. build the jdm programmer and tested it on a win2000 desktop and win98 laptop. both worked even i didn´t get the 13,7 volt, but only 12,7 volt. And on the win98 laptop i also needed to switch into API mode. otherwise i got error 0000. wanted to put the mios on it but only had a keyboard with usb to midi out interface and only could get a 6n139 optocoupler from my local supplier. seemed not to work so i build the to com interface burned the modefied bootstrap loader (changed the baudrate) and everything went fine. had to change one mistake on my SIDpcb (solderplob) and bingo.

    Know some little questions:

    1. Why is there no Vss conection between core and Dinx1  on the  2x20_enc.pdf as well on the other pdf´s? i didn´t try it without because i thought it´s an mistake in the drawing? but i wanted to ask. maybe i am missing something.

    2. can i seperate the ground from the core and the sid somehow? i am using two transformers one for the 5V, one  for the 12V so i have two seperate grounds available. might be better for the audio signal. (when i turn an encoder i can slightly hear  the movement.) that leads me to the next question.

    3. i hear slightly some sound from the sid after i the hit the first note. (thats fantastic you might think, but i mean after i released it again.) its for sure the sound of the sid (it is just the last played note and when i transpose the oscillators for example i can hear the changing) and it stay present until i change into another patch. it is very small though but i as i used very good sennheiser i noticed it.

    4. When i go into the envelope sektion, the first parameter shown is the number of the envelope. on my lcd everytime the default envelope number is 7! but there are only 2 envelops!

    5. is it right that stepA sends no midi so far? as mentioned  i am using the to com interface and for fun i loaded  the TC application and could send mididata.

    6. where can i change the direction of the encoders? (or what is the default setup? A=0;B=1 or B=0, A=1 on the shiftregister pins?)

    7.one parts question. where to find knobs in europe (preferred in germany or austria) for the alps stecB16 encoder which don´t have a marking?

    thats all i hope it is not to much.

    Thanks a lot i am looking forward to MB SIDstepD!

    chriss

  12. hello thorsten,

    thats cool that you got the same picture on your scope.

    "but I will integrate a fourth encoder mode into MIOS so that you will not notice a difference."

    what i don´t understand is,  if it will work when you don´t change the pins. because depending on the direction you turn the decoder, you will get output A starting simultaneously with output B, then going low befoe B goes low. if you turn in the other direction A starts to go high after B goes high but both go low at the same time. so you get a shift but only in the beginning (cw) or in the end (ccw).  if you think about what happens and look on the pinout (shematic) of the decoder, thats makes sense.

    i am asking because i couldn´t understand your reply fully (do i have to change the pins or not ?) and because i am wondering if the pic can read such non correct waveforms?

    sorry to bother you with this but all the MIOS is still to cryptical for me. (e.g. what you mean with encoder modes?)

    thanks

    chriss

  13. hello all,

    yesterday i got my encoders from schuricht and just for fun i measured the output waves with an scope. for this test i put the right and left pin with a 10k resistor to 5v and the middle pin to ground. just like the datasheet from alps descibes. then i measured pin right and pin left.

    now i didn´t get the 60 degree shifted waves signals as expected, but something else which is to hard for me to  describe in english. its not so important anyway, because i changed the connections, so that the ground pin was on the left(if you look from the top). and i got the expected outputs. so it seems that only the pins are connected differently, but without a dual band scope it´s nearly impossible to check.

    so the question is is there somthing wrong with me or with alps. i am asking because i did a pcb layout for all the encoders and would like to have a correct pinout.

    thanks a lot and i am looking forward to learn MIOS.

    chriss

  14. hallo thorsten,

    danke für deine schnelle antwort bei mir geht das ab heute auch so schnell weil unser router jetzt funktiniert und ich so mit zu hause netzt habe...

    zu deiner antwort: "Man kann mit den Ein- und Ausgehenden Signalen also anfangen was man moechte"

    das heisst die ledkränze und die dazugehörigen encoder hängen irgenwo auf dem din/dout board dran und werden nachträglich durch die software(/firmware?) zugeordnet?

    bleibt den die verkabelung der leds untereinander die selbe wie bei der midibox 16E. (frage nur weil ich schon so ein schönes eagle board für die leds gemacht habe, eigentlich auch schon für die taster und encoder)

    vielen dank schon mal und wann wird die erste sidbox erscheinen?

    chriss

  15. hallo thorsten und sonst alle,

    bin ungefähr seit  zwei tagen dabei deine super seite zu studieren und mir ein bild von alldem zu machen. ich möchte mir nämlich eine kleine sidbox bauen.

    eine frage die ich bei aller recherche noch nicht beantworten konnte und die für mich insofern wichtig ist da ich eine platine für die leds und die potis machen möchte, die über den DIN und DOUT boards ist und mit denen über steckerleisten verbunden ist

    1. dein aktuelles panel layout für die midiboxsid zeigt buttons die verschieden leds ansteuern -sid1,sid2,usw-(denke ich mal), also auch verschiedene digital outs benötigen.

    jetzt habe ich dem forum, welches übrigens wahnsinnig super ist, zwar gelesen das button1 zu led1 usw.geht  womit ja dann dein layout nicht funktionieren würde??. liegt das an dem 16F877 ? oder habe ich etwa noch nicht ganz verstanden?

    also nochmal: ist die zuordnung der buttons zu den leds (navigation ausgenommen) bei der neuen version der mb mit pic 18F flexibler als mit pic 16F?

    grüsse und vielen dank

    chriss

×
×
  • Create New...