Jump to content

mr_DK

Members
  • Posts

    48
  • Joined

  • Last visited

Everything posted by mr_DK

  1. That's what I needed to know, I order some more chips soon. Thanks! H
  2. Thanks for the replies, I indeed need only Outputs on one computer (Linux system running ardour for tests) and Inputs on the other computer (win XP system, running VSTs). The GM5 looks like a perfect option because it's very difficult to connect these 2 OS's with MIDI. The GM5 works fine on both, that's why he's so interesting for me. Is it possible to adapt the EEPROM in such a way that I can make an input out of every output? (I know I need some hardware adaptations as well in this case, but this is OK) I just did some testing but It seems not possible.... Any suggestions, or is it always max 5 Inputs/GM5. Thanks for all the help again! Hans
  3. Thanks for the reply TK, The purpose of this 10 In and 10 Out setup is that I'm building (for my thesis at school) a big console for "sample controlling". This table will control ardour because this software is completely open source. So I need one computer with Linux (with 10 MIDI outputs) and another running Windows for the use of VST instruments (10 Midi Inputs) because VST is not good supported by Linux. So that's why I wanted this 10 In and 10 Out divided. But as I read, the configuration I took gives me only one Input? Is there some way I can change the configuration and create 10 Inputs for one module and 10 Outs for another? I was thinking of Using the EEPROM for this setup. Sorry for being a "difficult customer" (like we say in belgium) Thanks! Hans
  4. Hello, I'm trying to get my GM5 modules up and working, but something weird is happening... I want to build 2 GM5's (1 x 10 Inputs, 1 x 10 Outputs) I have ordered the small PCBs so I have to build the breakout board. I soldered the small PCB and destroyed J1 and J2 as said in the GM5 PDF file. In this PCB there's no J8 jet so nothing I can do there. What happens when I connect this module to several PCs, I only see one input port instead of 10 and I don't know where to look honestly (I used MIDIOX for checking)... Anybody who can help? Thanks! Hans
  5. Hello, You should try to select "Wait for upload request before starting upload" In Mios Studio in the sending panel. I always work this way. You switch off the MB core module, then you start Mios Studio, Start the Upload. Then MiosStudio says something like "Waiting for upload request". Then you power up your Midibox, then the transmission will start. Hope this helps? Grtz
  6. Congrats Sebo, Fantastic result! Great design! Hopefully any sound demos on the way? Best Hans
  7. still thinking about the organisation of the software, I've also been thinking a lot about the structure of the menus. I just need a little bit more time to sort that out. Now there's nothing programmed yet. I'll post it, from the moment it's finished. best Hans
  8. Awesome :D Amazing how you can create very fun designs with something everybody else throws away... Very cool!! Congrats! Best Hans
  9. Thanks for the compliments! Gives a nice feeling that all the work I did is appreciated. The whole router was designed in Cinema 4D so I had a complete overlook of everything, so I knew from before that everything should fit perfectly (the lasertran print design was made by illustrator and also tested in cinema 4D, as well as the wholes had to fit perfectly as wel) The 3 blue PCBs are indeed custom made, 2 in the front panel with the leds connected (they're all made by a good friend of mine), and the third mini PCB is LED driver derived from the LTC midi module, which handles the core TxRx LEDs. The glued busses to the front panel are from conrad: http://www1.conrad.be/scripts/wgate/zcop_be3/~flNlc3Npb249UDkwX0JFX0IyQzpDX0FHQVRFMDU6MDAwMC4wMGIyLjU2NmI0NjdjJn5odHRwX2NvbnRlbnRfY2hhcnNldD1pc28tODg1OS0xJn5TdGF0ZT0xNjkwMDMzMTE1====?~template=PCAT_AREA_S_BROWSE&mfhelp=&p_selected_area=%24ROOT&p_selected_area_fh=&perform_special_action=&glb_user_js=Y&shop=BE&vgl_artikel_in_index=&product_show_id=&p_page_to_display=DirektSearch&~cookies=1&zhmmh_lfo=&zhmmh_area_kz=&s_haupt_kategorie=&p_searchstring=afstandsbout&p_searchstring_artnr=&p_searchstring_manufac_artnr=&p_search_category=alle&fh_directcall=&r3_matn=&insert_kz=&gvlon=&area_s_url=&brand=&amount=&new_item_quantity=&area_url=&direkt_aufriss_area=&p_countdown=&p_80=&p_80_category=&p_80_article=&p_next_template_after_login=&mindestbestellwert=&login=&password=&bpemail=&bpid=&url=&show_wk=&use_search=3&p_back_template=&template=&kat_save=&updatestr=&vgl_artikel_in_vgl=&titel=&darsteller=&regisseur=&anbieter=&genre=&fsk=&jahr=&jahr2=&dvd_error=X&dvd_empty_error=X&dvd_year_error=&call_dvd=&kna_news=&p_status_scenario=&documentselector=&aktiv=&gewinnspiel=&p_load_area=$ROOT&p_artikelbilder_mode=&p_sortopt=&page=&p_catalog_max_results=20 They are glued with dual component glue, which is very strong. This way I didn't had to make wholes in the front panel. The panels are screwed onto the busses, so they can always be removed. Best Hans
  10. Another picture here about the technical side. I may be have to mount an EEPROM IC to be able to save presets on filters and routing schematics... best! hans DSC_4376.JPG DSC_4376.JPG
  11. Hello, I'm proud to present after some months of hard labour. My first MIDI router! (As you can see, I'm still waiting for my buttons to be delivered 8). After this I can start programming, it will be a combination of a router (LED's on the left to select which IN ports goes to which OUT ports), and a MIDI filter to filter or change data on each out port (mostly controlled with the buttons). The LEDS on the right are the status leds (used the ltc module for the core status leds. I'm just curious for all kinds of opinions about design, concept... good or bad... Thanks, Best Hans DSC_4374.JPG DSC_4374.JPG
  12. Hey Glitched, I read the PDF's carefully, and I think I can help you out with most things... First of all let me give you a little hint on how I work, this way I avoided a lot of trouble like you're having now... Get cinema 4D or wathever 3D designing program you can find and draw the whole thing. Just by drawing it this way you will notice another bunch of problems. I've added a design for my GM5 rack module so you can check what I mean. By this way I could check up everything in a 3D way, if there was enough room, does this button looks good,.... after the design steps I just had to enter the sizes and coordinates of the wholes into FPD and order it. (it was the same for the printing on the panel) About the LCD, I guess you'll have to look up the "viewable" size of the display and get one of those "LCD windows" which you mount on the device, reichelt sells those things: http://www.reichelt.de/?;ACTION=3;LA=4;GROUP=A529;GROUPID=3013;ARTICLE=42813;START=0;SORT=artnr;OFFSET=16;SID=284OSzYKwQARwAAARwQyo6b637ae9ad41be5f570bbb0f1a2e4130 Then you just have to check up the datasheet of the window to know how to drill the wholes. In the attachment is a front panel file of my router, which also has a 2*20 lcd with a window, I cut out the window (with the two balancing wholes! and fit the lcd on the other side. About the tactile switches, I would take +0.3mm to be sure (front panel designer is pretty precise ;) ) Then the Standoffs, they look good but on the other hand, I use just standerd "distance busses" I don't know the exact word but they use it to mount several PCB's on the sam distance (they cost like nothing, and use just standard M3 screws). You can glue those to the front panel from one side and screw the LCD in, on this manner you don't have any screws on your front panel which makes it looking real professional I will now make a post in "Design Concepts" about my new router who's almost finished, almost everything I told in here will be visible on the photographs (the LCD window, the mounting to the front board, etc...) I hope this was a little bit helpful... If there are some more problems, just let me know, Best, Hans MIDI Router 2.fpd MIDI Router 2.fpd
  13. mr_DK

    screenkeys

    Hey nsunier, Sorry for the late reply, I'm not familiar with the Xilinx system (I know what it is, but that's where it ends...) I would rather try to fit it in MidiBox... So I think I'm not really able to help, you probably know much more about Xilinx then I do ;) Sorry, and good luck! Best
  14. mr_DK

    screenkeys

    Hello, I was also thinking of using some of those nice screenkeys. I was wondering if there's any progression on this matter? If there's anything I can try to help with? Best!
  15. Nice, The fonts work very fine! Thanks Best
  16. Indeed you're right, Sorry for the late reply! So here's the problem, the code is as follows: void DISPLAY_Init(void) __wparam { MIOS_LCD_Clear(); MIOS_GLCD_FontInit(MIOS_GLCD_FONT); MIOS_GLCD_GCursorSet( 10,6); MIOS_LCD_PrintCString("Sample Controller"); MIOS_GLCD_GCursorSet(10,10); MIOS_LCD_PrintCString(" Powered by "); // switch to big font (part of glcd_font package) MIOS_GLCD_FontInit(GLCD_FONT_BIG); MIOS_GLCD_GCursorSet(33,15); MIOS_LCD_PrintCString("MIOS"); MIOS_GLCD_FontInit(GLCD_FONT_SMALL); MIOS_GLCD_GCursorSet(20,28); MIOS_LCD_PrintCString("Hans Cornelis"); } and the make result is as follows: rm -rf _output/* rm -rf _output rm -rf *.cod *.map *.lst rm -rf *.hex mkdir -p _output sh d:\midibox\mios_base_v1_0b\mios_base_v1_0b\bin/mios-gpasm -c -p p18f452 -I./s rc -I d:\midibox\mios_base_v1_0b\mios_base_v1_0b/include/asm -I d:\midibox\mios_ base_v1_0b\mios_base_v1_0b/include/share -I d:\midibox\mios_base_v1_0b\mios_base _v1_0b/modules/app_lcd/t6963c_v -I d:\midibox\mios_base_v1_0b\mios_base_v1_0b/mo dules/glcd_font -DDEBUG_MODE=0 -DSTACK_HEAD=0x37f -DSTACK_IRQ_HEAD=0x33f -I d:\ midibox\mios_base_v1_0b\mios_base_v1_0b/modules/mios_wrapper d:\midibox\mios_bas e_v1_0b\mios_base_v1_0b/modules/mios_wrapper/mios_wrapper.asm -o _output/mios_w rapper.o sh d:\midibox\mios_base_v1_0b\mios_base_v1_0b\bin/mios-gpasm -c -p p18f452 -I./s rc -I d:\midibox\mios_base_v1_0b\mios_base_v1_0b/include/asm -I d:\midibox\mios_ base_v1_0b\mios_base_v1_0b/include/share -I d:\midibox\mios_base_v1_0b\mios_base _v1_0b/modules/app_lcd/t6963c_v -I d:\midibox\mios_base_v1_0b\mios_base_v1_0b/mo dules/glcd_font -DDEBUG_MODE=0 d:\midibox\mios_base_v1_0b\mios_base_v1_0b/modu les/app_lcd/t6963c_v/app_lcd.asm -o _output/app_lcd.o sh d:\midibox\mios_base_v1_0b\mios_base_v1_0b\bin/mios-sdcc -c -mpic16 -p18f452 --fommit-frame-pointer --optimize-goto --optimize-cmp --disable-warning 85 --oba nksel=2 -I./src -I d:\midibox\mios_base_v1_0b\mios_base_v1_0b/include/c -I d:\m idibox\mios_base_v1_0b\mios_base_v1_0b/include/share -I d:\midibox\mios_base_v1_ 0b\mios_base_v1_0b/modules/glcd_font -DDEBUG_MODE=0 main.c -o _output/main.o d:\midibox\mios_base_v1_0b\mios_base_v1_0b\bin/mios-gpasm modifies _output/main. asm, result in _output/main__mios-gpasm-tmp.asm sh d:\midibox\mios_base_v1_0b\mios_base_v1_0b\bin/mios-gpasm -c -p p18f452 -I./s rc -I d:\midibox\mios_base_v1_0b\mios_base_v1_0b/include/asm -I d:\midibox\mios_ base_v1_0b\mios_base_v1_0b/include/share -I d:\midibox\mios_base_v1_0b\mios_base _v1_0b/modules/app_lcd/t6963c_v -I d:\midibox\mios_base_v1_0b\mios_base_v1_0b/mo dules/glcd_font -DDEBUG_MODE=0 d:\midibox\mios_base_v1_0b\mios_base_v1_0b/modu les/glcd_font/glcd_font_big.asm -o _output/glcd_font_big.o sh d:\midibox\mios_base_v1_0b\mios_base_v1_0b\bin/mios-gpasm -c -p p18f452 -I./s rc -I d:\midibox\mios_base_v1_0b\mios_base_v1_0b/include/asm -I d:\midibox\mios_ base_v1_0b\mios_base_v1_0b/include/share -I d:\midibox\mios_base_v1_0b\mios_base _v1_0b/modules/app_lcd/t6963c_v -I d:\midibox\mios_base_v1_0b\mios_base_v1_0b/mo dules/glcd_font -DDEBUG_MODE=0 d:\midibox\mios_base_v1_0b\mios_base_v1_0b/modu les/glcd_font/glcd_font_knob_icons.asm -o _output/glcd_font_knob_icons.o gplink -s d:\midibox\mios_base_v1_0b\mios_base_v1_0b/etc/lkr/p18f452.lkr -m -o p roject.hex d:\midibox\mios_base_v1_0b\mios_base_v1_0b/lib/libsdcc.lib d:\midibo x\mios_base_v1_0b\mios_base_v1_0b/lib/pic18f452.lib _output/mios_wrapper.o _outp ut/app_lcd.o _output/main.o _output/glcd_font_big.o _output/glcd_font_knob_icons .o error: missing definition for symbol "_GLCD_FONT_SMALL", required by "_output/ma in.o" make: *** [project.hex] Error 1 I know it's a lot of directories, sorry for that. It's just so strange that it takes the MIOS_GLCD_FONT, the _GLCD_FONT_SMALL and all the other fonts give me an error. Best! Hans
  17. And the one in Portrait mode btw, I only seem to have a small problem using GLCD_FONT_NORMAL or GLCD_FONT_SMALL I tried it in this piece of code: MIOS_GLCD_FontInit(MIOS_GLCD_FONT); MIOS_GLCD_GCursorSet( 4, 5); MIOS_LCD_PrintCString(" Sample controller "); MIOS_GLCD_GCursorSet( 50,9); MIOS_LCD_PrintCString(" powered by "); // switch to big font (part of glcd_font package) MIOS_GLCD_FontInit(GLCD_FONT_BIG); MIOS_GLCD_GCursorSet(128, 8); MIOS_LCD_PrintCString("MIOS"); When I tried to change the GLCD_FONT_BIG into the small or normall, my make process gave an error.... I hope I'll find that out soon... Best! DSC_4277.JPG DSC_4277.JPG
  18. Hey again, I did some changes to the horizontal driver as well, and it also seems to work very nice. There is a SMD controller available from electronic assembly (my LCD is from them) which takes all the mathematical work on itself, it's designed to work with the T6963 and it gives some nice graphical possibilities. Maybe in the future I can experiment with it a little and may be integrate it in the Midibox so that the core modules do what they do best (working with MIDI) and the EA IC does the graphical work for optimal speed of both components. The dataSheet of this IC can be found at: http://www.lcd-module.com/eng/pdf/grafik/ic6963e.pdf But that's some future music, I'll first try to get my project set up and see how it reacts. Another thanks to Stryd_one and Philtaylor for their extreme good help! Enjoy the pictures! BTW it's still much nicer than on the illustrations 8) what a hot blue it is... DSC_4275.JPG DSC_4275.JPG
  19. I know what you're talking about, Allthough my Router project and my 2 GM5 modules are evolving very well, I just recieved the front panels I ordered at chaeffer. I hope to get them finilized in a few months. Best and very good luck!
  20. Thanks that explained a lot 8) This is my first (probably a very small and with lots and lots of help) contribution to the MidiBox project, It now supports a GLCD up to 240*128 pixels!!! :D The code needs to be set as follows: USER_LCD_ClearInnerLoop movlw 0x00 rcall USER_LCD_Data movlw 0xc0 ; write and increment rcall USER_LCD_Cmd incf MIOS_GLCD_GCURSOR_X, F, BANKED BRA_IFCLR MIOS_GLCD_GCURSOR_X, 7, BANKED, USER_LCD_ClearInnerLoop clrf MIOS_GLCD_GCURSOR_X, BANKED incf MIOS_GLCD_GCURSOR_Y, F, BANKED BRA_IFCLR MIOS_GLCD_GCURSOR_Y, 7, BANKED, USER_LCD_ClearOuterLoop both BRA_IFCLR functions not to be set at 7 and then it clears out the whole screen. I don't have words to thank you for your help, it gives a very satisfactional feeling. Regards
  21. Life can sometimes be easy 8) windows put them there when you use the Tab key to enter long directory names. The GLCD takes every place very nice, I tried to give some othe positions and it works very nice. I looked at the clear_LCD function in app_lcd.inc, I think were I need to change things, I experimented with some other numbers and I saw changes in the snow area. But it only got smaller :P ;; clear the first 32*64 bytes ;; use MIOS_GLCD_GCURSOR_X and _Y as counter register SET_BSR MIOS_GLCD_GCURSOR_Y ; 64 lines to clear clrf MIOS_GLCD_GCURSOR_Y, BANKED USER_LCD_ClearOuterLoop SET_BSR MIOS_GLCD_GCURSOR_X ; 32 bytes to clear clrf MIOS_GLCD_GCURSOR_X, BANKED USER_LCD_ClearInnerLoop movlw 0x00 rcall USER_LCD_Data movlw 0xc0 ; write and increment rcall USER_LCD_Cmd incf MIOS_GLCD_GCURSOR_X, F, BANKED BRA_IFCLR MIOS_GLCD_GCURSOR_X, 5, BANKED, USER_LCD_ClearInnerLoop clrf MIOS_GLCD_GCURSOR_X, BANKED incf MIOS_GLCD_GCURSOR_Y, F, BANKED BRA_IFCLR MIOS_GLCD_GCURSOR_Y, 6, BANKED, USER_LCD_ClearOuterLoop I changed the second flag of both BRA_IFCLR functions. But to be real honest I'm not really sure what this step does. Any hints? Thanks, we're almost there
  22. [b]sh --version[/b] GNU bash, version 2.04.0(1)-release (i686-pc-msys) Copyright 1999 Free Software Foundation, Inc. [b]make --version[/b] GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i386-pc-mingw32 [b]sed --version[/b] GNU sed version 3.02 Copyright (C) 1998 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE, to the extent permitted by law. [b]sdcc --version[/b] SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.6.0 #4 309 (Jul 28 2006) (MINGW32) The set MIOS has a positive result, but I have to be really honest with you, I installed the msys and minGW into the program files and the base package of mios is in the directory d:\midibox\mios_base_v1_0b/mios_base_v1_0b C:\Documents and Settings\Hans Cornelis>set MIOS MIOS_BIN_PATH=d:\midibox\mios_base_v1_0b\mios_base_v1_0b\bin MIOS_PATH=d:\midibox\mios_base_v1_0b\mios_base_v1_0b C:\Documents and Settings\Hans Cornelis>set path Path="c:\Program Files\msys\1.0\bin";"c:\Program Files\MinGW\bin";"c:\Program Fi les\gputils\bin";"c:\Program Files\gputils\bin";"c:\Program Files\SDCC"\bin PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH I hope it's a version problem, otherwise I must reinstall all the software. Sorry I didn't install it in the standard directory, I like a little order on my computer and I always set directories of software into the program files... I did not concerned the consequences Best
  23. when I want to execute a make, my cmd section always says: sh is not recognized as a internal or external program, batchfile,... (Sorry in my cmd it's in dutch, so I tried to translate the message) I'm pretty sure all the PATH references are done well, I have the sh.exe file in the bin directory of the msys so It's installed correctly... Thanks, Hans
  24. Hello again! Sorry for the late reply, I had a some busy times. This will sound rather stupid but for the first time I had problems with the SDCC builder, because the files are in other directories and so (Until now the SDCC skeleton contained everything I need and worked very fine). I read about the new toolchain on the Wiki http://www.midibox.org/dokuwiki/windows_toolchain_quickstart Still having some trouble with building hex files, but I will figure this out I guess, I just need some more time. Regards
  25. Sure I respect your choices, If you're sure what you need then go for it! good luck
×
×
  • Create New...