Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by ssp

  1. Nice to be back in the forum after work life got in the way and things had to change! Bought my cnc machine from work along with the laster system, just finished re-wiring it and fitting new cable chains, new power chassis for the main drive system. I used to use it for making pcbs and enclosures and faceplates so good to have this for use now. Dug my projects out and looking forward to finishing them finally over the winter months, no questions from me, just time to get on with things!
  2. Thats is some beautiful work there Phatline ;)
  3. I just got one of these to try here, all i am getting is just random pixels. https://www.diymore.cc/collections/led-display-module/products/2-42-inch-12864-oled-display-module-iic-i2c-spi-serial-for-arduino-c51-stm32-green-white-blue-yellow
  4. question!! so on my ng core i have set the core to have its own name and gave it a device id=127 (random pick) when i attach it to the pc it is picked up as normal however, when i then attach my gm5x5x5 to the computer all the ports are the same name if i plug in the gm5x5x5 first then the midibox ng it make all the ports the same as the ng core how do i resolve this any ideas? I have msg'd nils so waiting for some info ( hopefully) Update: solved found the info in the gm5 page at the bottom, good ol' Nils ;) Q: I want to use two GM5 modules for getting 10 MIDI IO ports, how can I give them individual names? A: Break the bridge at J8 of the PCB with a small screwdriver, so that IC2:IO4 is not connected to ground anymore. This selects the ploytec.com VID, so that your operating system can differ between two devices (midibox.org and ploytec.com) and installs an individual .inf file.
  5. edit update: Managed to get the NG working with my XVA1 today, had a few issues with the crappy chinesium midi cable interface thingy, its in the bin now. used teh GM5x5x5 and all worked first time. working on using sys-ex with it, found an old post in the forum to help me with the sys-ex streams really love the .NG
  6. thats ok Thomas ;) For now i will just bank things now i know how to, i need to learn a bit more about code writing etc before i jump into editing it. I am going to go through some of the tutorials in github and try a few other things out. there may be questions about code along the way, but only once i have written or edited things to try. Thanks again
  7. Currently here : https://github.com/midibox/mios32/tree/master/apps/tutorials/005_polling_j5_pins before i go ZZZzz is this the right section to read through ( going to print it out if it is and mark things as I go ) to try and learn how to use the other pins, or do I need to look at other sections of code as well? The info i pasted above from Ucapps page doesn't really go into anything and it wasn't followed up. in github there is this for the Ain module: https://github.com/midibox/mios32/tree/master/apps/tutorials/012_ain_muxed however for the ainsermuxed: https://github.com/midibox/mios32/tree/master/apps/tutorials/012b_ainser_muxed there is nothing in there. I would really like to learn how to edit the pins on j5 to add ainser64's and compile etc. Thanks.
  8. Hi Thomas the only thing i can find that maybe along those lines is this thread from fantomxr but this is for ainser8 I know nothing about this code or how to edit or compile I am afraid, so any pointers or help etc would be welcome for me. little bits make sense but I am no coder I am afraid.
  9. Question: On the Ainser64 info page it states that more than 2 ainser64 can be used: (i want to have 3 ainser64 connected using their own power feed in rather than from the core) Multiple MBHP_AINSER64 (or MBHP_AINSER8) modules are connected to J19 in parallel, and accessed by strobing dedicated chip select lines. J19 provides two chip selects (called "RC1" and "RC2"), if more modules should be scanned, common IO pins could be used for the same purpose (e.g. available at J5). To programmers: alternatively, AINSER64 modules could be chained, or a 3-to-8 MUX could be used for accessing 8 modules via 3 IO pins of the microcontroller. Does the underlined statement refer to j5a and j5b on the core board? Would i need to edit the mios for this or just the NGC file? I cannot find an example or any info for this. Thanks
  10. Many thanks Thomas, with the code and the other edits it is working , i will edit the main code for the 16 3 digit lcds tomorrow after work and see if it does the job.
  11. Thanks Thomas, The fwd_led i tried earlier but it wasn't playing ball for me. The build will have an dec bank and inc bank pair of buttons, with the leds above them 16 mini leds in all, this is just to give visual info on which one is selected. to sweep the cc# from 0:127 I will just use a single encoder. I have all of this working all bar the dec-inc leds so i will give this a try again, if no joy i will check the rats nest incase something is astray. Thanks as always.
  12. Can you have more than one meta event mapped to a button press at the same time?
  13. there isn't any real info on how I can do this, I have the bank code written and working yet don't seem to be able to assign a single led to a bank to show its active and then turn off when another bank is selected and that bank's led comes on. I have tried multiple versions of adapted code and do not seem to be getting anywhere. Searching the forum is hard work as it keeps erroring and not completing the search. I am going to try something in the .NGR script but even so I don't think that is the answer.
  14. Looking over the .NGR info and I am wondering if in this instance would I use the .NGR script to have a single led per bank to show that bank is active? (reading mode activated in the meantime!!)
  15. Question using the code above i edited to add banked leds. from this: # Bank 1 EVENT_AINSER id=1 hw_id =1 bank=1 fwd_to_lcd=1 type=CC chn=1 cc=16 range=0:127 offset=0 lcd_pos=2:1:1 label="FDR1 #%3i %3d@(2:1:2)%B" #Bank 2 EVENT_AINSER id=1 hw_id =1 bank=2 fwd_to_lcd=1 type=CC chn=1 cc=17 range=0:127 offset=0 lcd_pos=2:1:1 label="FDR2 #%3i %3d@(2:1:2)%B" To this: # Bank 1 EVENT_AINSER id=1 hw_id =1 bank=1 fwd_to_lcd=1 fwd_id=LED:1 fwd_to type=CC chn=1 cc=16 range=0:127 offset=0 lcd_pos=2:1:1 label="FDR1 #%3i %3d@(2:1:2)%B" #Bank 2 EVENT_AINSER id=1 hw_id =1 bank=2 fwd_to_lcd=1 fwd_id=LED:2 type=CC chn=1 cc=17 range=0:127 offset=0 lcd_pos=2:1:1 label="FDR2 #%3i %3d@(2:1:2)%B" However this just lit the led when the fader was moved and remained on when the bank was changed and then the other led came on and stayed on, not what i wanted. What i want is that when you press the bank buttons if you are on bank 1 then the led for bank one i9s lit, when you press the increment button to goto bank 2 led 1 goes out and led 2 for bank 2 come on press increment again and bank 3 led comes on and 2 goes out. how would i go about this? would i define an EVENT_LED id=1 and add functions to that or would i use a map? Thanks
  16. Got it all running, used 3 buttons and two displays and a single fader, the code works really nicely and I got to grips with it finally, this is good as I will need multiple functions to map rather than have too fit individual parts everywhere! Code: RESET_HW LCD "%C@(1:1:1)Bank Test" # Controlled from buttons # select Bank1 directly EVENT_BUTTON id=1 type=Meta meta=SetBank button_mode=OnOnly range=1:1 # For testing purposes: decrement bank EVENT_BUTTON id=2 type=Meta meta=DecBank button_mode=OnOnly # For testing purposes: increment bank EVENT_BUTTON id=3 type=Meta meta=IncBank button_mode=OnOnly # For testing purposes: cycle bank EVENT_BUTTON id=4 type=Meta meta=CycleBank button_mode=OnOnly # Bank 1 EVENT_AINSER id=1 hw_id =1 bank=1 fwd_to_lcd=1 type=CC chn=1 cc=16 range=0:127 offset=0 lcd_pos=2:1:1 label="FDR1 #%3i %3d@(2:1:2)%B" #Bank 2 EVENT_AINSER id=1 hw_id =1 bank=2 fwd_to_lcd=1 type=CC chn=1 cc=17 range=0:127 offset=0 lcd_pos=2:1:1 label="FDR2 #%3i %3d@(2:1:2)%B" # AIN hardware AIN enable_mask=00000000 # AINSER hardware AINSER n=1 enabled=1 muxed=1 cs=0 num_pins=1 resolution=7bit AINSER n=2 enabled=0 muxed=1 cs=1 num_pins=0 resolution=7bit # EVENTs #EVENT_AINSER id= 1 type=CC chn= 1 cc= 16 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=2:1:1 label="^std_ain"
  17. as soon as i have things set up and working i will share the pics and code as usual. just had to go out an buy a blooming piano for the kids.. electric!!
  18. I have attached an ainser64 to the core and the jitter has gone, im just going to get my head around this now and re code things and test the banking again.
  19. yes the ngc format is so much easier to go through than the old assembly!! but i got to grips with that in the end. I am trying to get to grips with everything then apply it in the thread in a more simplistic way for those coming in new and also it helps me visualise things better. I just got the fader working on the core once it was written it was simple # AIN hardware AIN enable_mask=10000000 ( I am assuming that the 8 digits refer to the 8 pins on J5a/b and for an active pin you put a 1 in place? # EVENTs EVENT_AIN id= 1 type=CC chn= 1 cc= 16 range= 0:127 It works but i get double figures in mios studio when i move the fader such as Chn# 1 CC# 16 = 22 Chn# 1 CC# 16 = 22 Chn# 1 CC# 16 = 23 Chn# 1 CC# 16 = 23 Is this a bit resolution that i need to add into the ngc code to prevent the doubling up on the fader movement into mios studio? Thanks I need some zzz now so will test the code tomorrow
  20. Yes i understand the "bank" setup and hw id's, it was just finding an example of setting up the fader on j5a as the only other time i have used it is with an ainser64 and i dont need one of those right now. sat going through the ngc info again to see whats what, there is so much missing info wise that was never added along with the solution to having multiple ssd1306 but it still refers to j28 on the lpc pcb and nothing for the stfm pcbs. it would be good to get some of these updated as others have had to edit mios rather than configuring the ngc which is easier for users.
  21. We need the site admins to check in with the hosts to see whats going on as the forum is having daily errors now. tonight along with the internal server error 500 that most get I am now getting the nginx error page and this is constantly every couple of mins.
  22. Question: I want to test the bank code i have written, I am going to assign in to a fader connected to j5a on the stfm core. Would i use the EVENT_AIN function for this? I just want to connect a fader directly to j5a, so how would i implement this rather than using an ainser8 or ainser64? thanks
  23. yes this is what is in the git hub, i am thinking of two buttons, -bank and +bank, i am still reading things and writing bits down to work on this week Thanks for the info Thomas @totoRaymond
  24. I am looking at the banks and other functions today. I am sure I have seen this discussed somewhere ( having a forum search to find it) can you have multiple control parameters on a fader, potentiometer or encoder from a button press So if you want one fader to control ADSR features. on its 1st function its cc16 assigned to the amplitude press a button and then its second function is cc17 assigned to decay press again third function is cc18 assigned to sustain.. and so on Would this be a combination of mapping and radio buttons? I am playing around with the code today seeing if i can make a happy accident. I am currently reading the enc_banks on teh git hub https://github.com/midibox/mios32/blob/master/apps/controllers/midibox_ng_v1/cfg/tests/encbanks.ngc Tx
  • Create New...