TK.

ok, should be reliable (ah: and very good - I've a tester for the most recent app_lcd updates - could you please also test a selfbuilt binary based on the latest SVN revision? :)) The effect that you notice would happen, if the D7 feedback input line isn't working correctly. You can test it - together with the remaining LCD control/data outputs - with the new "testlcdpin" command from the MIOS Terminal (also only available when you compile the latest sources by yourself) Best Regards, Thorsten.

Are you using a released binary, or did you build the application by yourself? (just to doublecheck, because I did some changes on the universal LCD driver in the last days) Best Regards, Thorsten.

Please read the hints under "TEST MIDI2" at this page: http://www.ucapps.de/howto_debug_midi.html It also links to a schematic which exactly shows what you have to do for this test. It's clear why you won't get a loopback as long as the PIC is connected... this test requires a direct hardware loopback, therefore the PIC has to be removed from the socket. It could also make sense to read the whole page in order to get a better understanding about the test procedure - maybe it wasn't required to buy a new optocoupler if you would have done this test before... Best Regards, Thorsten.

You are almost through! :) J28:SDA and J28:SC are the right pins. The behaviour that you noticed when the CS lines are connected to J5 is the same, as if they would be connected to ground (of course, because J5 isn't activated) And this indicates, that your GLCD has low-active CS inputs. And this requires the usage of "lcd_type 0x82" (KS0108_INVCS) Best Regards, Thorsten.

With a defective optocoupler the loopback issue would be perfectly explained. Is the new one working better? If not: check your MIDI connections: - MIDI IN of your Mac to MIDI OUT of the sammichSID - MIDI OUT of your Mac to MIDI IN of the sammichSID (for the case this isn't obvious to you) Best Regards, Thorsten.

Btw.: I don't agree that Teensy is the better hardware. Also the statement "alot of help in theory and even pre written codes that will work fine" is odd when you consider that with MIOS32 a complete, reliable, well documented operating system for MIDI applications with many examples exists - and it's open source. With MIDIbox NG you even wouldn't have to do any coding for your project. Also your price comparison is not correct, probably you haven't read the MBHP_CORE_LPC17 page completely - e.g. the "Minimal Circuit to get USB running" part. The LPCXPRESSO is available in german shops as well... However, I guess you will learn it while you are having fun with this 8bit chip. Of course, for your usecase it will be sufficient, therefore nothing against your plans... But you won't save money by using it - instead you will lose flexibility. And you will notice the power supply issues that I mentioned, because the analog voltage domain isn't properly shielded on the Teensy PCB. Expecting the same robustness against jittering analog values for such a cheap development board compared to a professional designed PCB of a MIDI Controller like from NI is nonsense - remember my words... ;-) Best Regards, Thorsten.

:) Best Regards, Thorsten.

I haven't tested this yet, but up to 8 SSD1306 based GLCDs should already work with the latest sources which are in the SVN repository. I will add a J28 based CS extension for these displays as well. Best Regards, Thorsten.

Bad news: I can't find my spare KS0108 display anymore, and it would be too cumbersome to use the 240x64 GLCD instead (which is directly soldered to a MBHP_CORE_STM32 module - I will never do this again) But: I found in following application note: http://www.kronosrobotics.com/Anotes/GraphicLCD_AN.pdf that V0 has to be connected between ground and VEE via a trimpot (see Schematic 2)! This means, that you can't use the J15:V0 output of the MBHP_CORE_LPC17 module. Instead you've to use an external trimpot which is responsible for the display contrast. If you haven't tried this before, than it's very likely the reason why the LCD doesn't show any pixels. And while I was writing this, I found the same circuit in my own schematic: http://www.ucapps.de/mbhp/mbhp_lcd_ks0108_mios32.pdf :) Best Regards, Thorsten.

By default, the T6963C driver allocates some additional memory between 0x378..0x37f, see also: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fmodules%2Fapp_lcd%2Ft6963c_h%2Fapp_lcd.inc This clashes with the stack in C applications (I just notice, that this isn't properly documented!) Solution: either specify: GPASM_DEFINES += -DAPP_LCD_DONT_LOCATE_VARIABLES=1 in your Makefile, or change the stack locations there -- in your case (very good idea to use 0xe* for PIC18F4620!): MIOS_WRAPPER_DEFINES = -DSTACK_HEAD=0xeff -DSTACK_IRQ_HEAD=0xe80 Note that the linker file modification only reserves the stack memory. The defines do the actual initialisation. yes, this would also be ok No, they should never! (only a single thread should access the LCD) It really depends on your application... but usually the main program needs more stack than a IRQ routine Best Regards, Thorsten.

yes, only the LCD parameters have to be entered into the bootloader (inclusive the "store" command). If you reset the core thereafter (or power-cycle it), the LCD should already output a message even if the bootloader application is still installed. They are automatically activated. Only danger is, that a certain application (like MBSEQ) uses this port for other purposes. I will doublecheck the KS0108 driver with my GLCDs (inverted and non-inverted) this evening. I can at least confirm, that a 240x64 GLCD is still working on a MBHP_CORE_STM32, because it's part of my MBLC hardware. Best Regards, Thorsten.

Yes... BUT: in song mode, you can switch between A1/B1/C1/D1/E1/F1/G1/H1 as well with the same approach - in this case, the song should directly jump to the selected position, and it should continue to play. Best Regards, Thorsten.

The Multi-CLCD option is now fully implemented and will be released with V1.012! :smile: As long as "only" 6 CLCDs are used, the E inputs of the 4 additional CLCDs can be directly connected to J28 pins With more than 6 CLCDs shift register(s) will be required. Before the official release all the options and the configuration procedure will be documented properly at a new MBNG manual page (currently the only blocking point ;-)) Best Regards, Thorsten.

No, Phrase mode only executes A1/B1/C1/D1/E1/F1/G1/H1..8 until all positions have been executed which are not "time consuming". E.g., the first step could contain a tempo change, the second step could fire a mixer map, and the third step could finally change the pattern set. That's the intended usecase. Best Regards, Thorsten.

Wow! I'm definitely interested - please keep us updated! :smile: CCs can already be named "dynamically" by using conditional labels: http://www.ucapps.de/midibox_ng_manual_ngl.html Only useful if the MIDI Learn function is used, because otherwise you would change the event assignment manually in the .NGC file anyhow. And such a file can be quickly changed from MIOS Studio - much quicker than on the simple SCS interface. It needs some configuration in the .NGC and .NGL file, and it definitely won't be possible to do this from the SCS! But it's possible - and probably much more flexible than you noticed yet (or know from any other MIDI controller)! Note that multiple .NGC/NGL setups can be stored on SD Card. So, you could also use different setups for different synths. More discussions about such conceptional topics please not in this dedicated LCD thread, but in a separate thread. Best Regards, Thorsten.

It will be connected to J19: DATA IN to J19:SO CLK to J19:SC CS to J19:RC1 or RC2 (configurable) Best Regards, Thorsten.

This is indeed a nice display! How much does it cost? Yes, this requires two chained 74HC595 at J28 for the 14 additional E lines of the LCDs which can't be directly connected to J15A/B The hardware side will be properly documented once it has been tested by Duggle. From the software side in V1.011 only 2 CLCDs are supported, but with V1.012 up to 64 CLCDs will be accessible! There are some other constraints, (see my initial answer), but for 16 6x1 LCDs there won't be any issue. It could make sense to connect a 2x20 directly to J15A, so that you are able to access the SCS No problem, the messages are fully configurable. See also: http://www.ucapps.de/midibox_ng_manual_fs.html E.g. in order to write "ENV 0" ... "ENV127" to the first LCD, write: EVENT_ENC ... lcd_pos=1:1:1 "ENV%3d" In order to write this message to the 16th LCD, write: EVENT_ENC ... lcd_pos=16:1:1 "ENV%3d" Best Regards, Thorsten.

It's actually "Parameter Layer button B" (below the track selection buttons) Background: the original frontpanel has no group or trigger layer selection buttons - therefore it was just button B I added this detail to the manual. Best Regards, Thorsten.

Hi Pete, .inc sounds like the MIOS8 based project (svn://svnmios.midibox.org/mios) The MIOS32 based project is located in a different repository: svn://svnmios.midibox.org/mios32 It's required to download the whole trunk, because the sources are not only located under apps/controllers/midio128_v3, but also under mios32, modules, FreeRTOS, etc. Best Regards, Thorsten.

The PIC18F4685 Best Regards, Thorsten.

Looks good so far. Only observation: it makes sense to connect the grounds of J19/J5A/B/C together, so that the circuit is always grounded, independent from the plugs to the core. Best Regards, Thorsten.

Thanks for confirming, that a Xcode installation is still required just for the basic build environment (make) - I wasn't sure about this. Best Regards, Thorsten.

:thumbsup: We can give it a trial run this weekend. :) Best Regards, Thorsten.

Hi Eden, Teensy is available for US $24, a http://www.ucapps.de/mbhp_core_lpc17.html'>LPCXPRESSO is available for EUR 24 (only an USB socket has to be added externally to get the same basic feature set like Teensy) So, I don't see the point where you will save money, especially since you've to spent all the development effort by yourself (the fun starts once you are trying to get really stable analog conversion values from a device powered via USB ;-)). It would be a nice learning example of course... Best Regards, Thorsten.

Hi Zaphyrin, for the case that it helps: I got my acryl panel (premade) from http://frontplaten.net Richard (the owner of this website) built a MB808 as well: You could ask him for the design data of the panel that he created for me (it has some corrections) - or just order an Acryl panel from him, which is definitely less expensive than an aluminum based panel from Schaeffer. :) Best Regards, Thorsten.