audiocommander

Wow! I need a thought screen helmet, too :o

Hi Gert, the response times of the QT160 and the QT113 are different: point 2.1.6. of the datasheet explains this for the QT160: Response time is fixed at 99ms at a 10 MHz clock. Response time cna be altered by changing the clock frequency. Doubling the recommended clock frequency to 20 MHz will halve the response time to 49ms. Response time will become slower if the total duration of all bursts is greater than 33 ms, i.e. an average of 5.5 ms per channel[/code] ...and the burst duration is to set by a cap. hehe... this is a special feature of the QT160 that's called AKS - Adjacent Key Supression, that's described on the first page of the datasheet: [code=QT160 Datasheet]The QT160 also offers the unique adjacent key suppression (AKS) which suppresses touch from weaker respnding keys and allows only a dominant key to detect, for example to solve the problem of large fingers on tightly spaced keys. So, that's the explanation, why only one input is working at a time! hmm... :-\ maybe you should invest some money in some single operated QT113's. The setup of the QT113 seems quite easy, see: The QT113's response time is highly dependent on burst length, which in turn is dependent on Cs and Cx. With increasing Cs, response time slows, while increasing levels of Cs reduce response time. Fig 4-3 shows the typical effects of Cs and Cx on response time.[/code] Best regards, Michael

I just experimented with a QT113 and found that it's a great chip to use touchDetection: I don't know why you experienced a slow response with the QT160 AFAICS it's the same as the QT113 but just multichannel (QT113: http://de.farnell.com/jsp/endecaSearch/partDetail.jsp?SKU=9775749 ). I checked it with an LED and cannot determine any slow behaviour... maybe you got the wrong Cap-Values? Best regards, Michael

Well, as you can read on the second page of the topic you are referring to, similar problems like yours occured. I bet it behaves exactly the same if JazzyPidjay would connect an LTC module! So I think it's rather a basic construction error: This all sounds like grounding/shielding issues. Normally the touch sensing pin J14 is used for motorfaders (see "Touch Sensors" on the MBHP MF page: http://www.ucapps.de/mbhp_mf.html ; there's also a very detailed explanation by TK here: http://www.midibox.org/forum/index.php?topic=1544.0 ). You don't need to ground yourself to get that working! So either the MB64 application is not configured to use that kind of feature (don't know that, 'cause I go no MB64) or there is a basic mistake about your implementation of the touchDetection. Why don't you use a normal button switch to test if your basic equipment is working; then you could resume experimenting with different touch detection circuits! J14 is not the only possibility to get that kind of feature... Best regards, Michael

so you connected it exactly like described here: http://www.ucapps.de/mbhp/mbhp_din_touchsensors.pdf ? And what kind of application are you using (eg MB64(e) ?) Does anyone know if J14 functionality is supported in all apps? Best regards, Michael

This will not work. And if it works, I'd be astonished. You need a capacity based touch sensor circuit (search for "Quantum QProx QT113") or if you want to stay connected while touching: a skin resistance circuit. Last one is probably the easiest: If you measure your skin resistance with a multimeter, you'll find out, that your skin as about 1 M to 20 M. If you look here: http://www.midibox.org/dokuwiki/doku.php?id=sensors and http://www.midibox.org/forum/index.php?topic=6506.0 you should be able to connect a basic skin restisance sensor. The topic was meant to be used on a AIN, but it's so easy, I think you'll be able to adapt it for a digital ON/OFF signal... However, I'd use a capacity based circuit, because you don't need to be wired. Just google around a bit and you should find plenty of touch circuits for switches! :) cheers, Michael

Okay, we're getting at it, I think everything is working fine: What exactly are you using as "Touch Sensor"?

hmm... I don't understand that part ;D I thought it works if the LTC is not connected (0 + 127): For a button, this would be the expected behaviour. Now when you connect the LTC you only get 127, is that right? That means the error should be at the LTC or the DIN-module or the optocoupler. The DINx4 modules have to be chained. That means: Core J9 --> J1 DIN#1 J2 --> J1 DIN#2 What I meant was to leave out the first DINx4 module to see if the error is located at the second DIN. Can you make a photo and attach it? In the meanwhile you could go through all the wirings and check them against the plans available @ uCApps.de; I think it sounds like a wiring issue... best regards, Michael

- if you have built an active LTC module, I expect you removed the optocoupler from the Core? - does it work if you leave out the full stuffed DINx4 board and connect only the board your touch-sensor is connected to? regards, Michael

ohhh ... the datasheet :-[ Thanks Moebius :-* After reading the datasheet I think I'll stick to my normal 2 pin push buttons and be happy ... IIC would have been fine, but serial... :-\ Best regards everyone, Michael

I'd be interested to know how they will be programmed/interfaced with MIOS. Do you have to program them on a PC and then they remember the current picture? Or do they need to be connected like every other LCD? In my eyes it would be interesting to have buttons on a midibox that have the ability to reflect the current behaviour (which can change)... 40 $ is really expensive ~20 $ sounds good if it can be used with MBHP without having to solder an extra Core for driving the buttons ;) Cheers, Michael

but I'm right you'll sell the items via eBay? Or do you expect us to bid per PM and take it then off eBay ('cause the mx isn't there anymore?) regards, Michael

great! thanks for adding this hack... I knew the time would come to use my old ps2 mice :) cheers, Michael

ohoo... Mittelfranken :) Grüße aus Nürnberg! Übrigens gibt es http://www.frappr.com/midibox Da kann jeder seine Location eintragen! stehen schon ziemlich viele drin

:-X ;D Yeah, I really think this would be the best option, too. Maybe you'll find a fitting interface someday, but I fear you'd had to sell your shorts to be able to pay that... An mbhp-iic-router could be configured as merger or splitter, too. And if you don't have no need to record it all at once on your PC hrmhrm... Mac I mean, you could add mechanical switch buttons to send the signals along... cheers! Michael

cool... that would be a nice option, cause > 1000 U$D always seemed a bit much for my taste (and needs) :) Thanks, stryd!

I once damaged a nice blue backlight by wrong soldering, then I found a new orange +7.5V backlight. I finally managed it to get it behind the glass, but it was hell to get the pressure right on the LCD contact. The new backlight was about 0.5 mm thicker than the old one... this was definitely not the funniest thing to do. Unfortunately I doubt it won't help you, if I tell you I got it from pollin.de? => http://www.pollin.de/shop/detail.php?pg=NQ==&a=NDQ4OTc4OTk= Best regards, Michael

LOL, I just thought some head jewelry would suit your avatar very well!! ;D

how about one or more MBHP IIC-Midi Router(s)? ;D would that be an option? (I'm building mine hopefully soon, I am so tired of having to plug around all these Midi Cables and loosing oversight about what goes where...). That way you could stick to your 8 port interface but increase your I/Os... Cheers, Michael

Well, synthesizer is indeed a complicated word, it's not only hard to spell it's also hard to speak ;D I would tell everybody that you planned this writing from the beginning. This has become a very beautiful synth with a perfect hui, wouldn't mind that ;) Mr modnaR: LOL... I loved your xmas hat so much, I had to join you ;D merry christmas everyone...

ahh, that may be if you're searching the forum while you're in a sub-thread. Best is to click on "Home" here before searching or using the advanced Search... I forgot to mention this, but I remember I had these troubles in the beginning, too :) no bad feelings from my side, you're welcome ;) Cheers, Michael

http://www.midibox.org/dokuwiki/doku.php?id=how_to_select_a_pic_id_header ;) regards, Michael ps: you can report your own posting to the moderator if you want this one to be moved...

Hi zeh, these are some good questions: - I found the answer in the C function-listing: So only two AIN-modules can be connected to one Core. - You can find an explanation of the LINK concept here: http://www.ucapps.de/midibox_link.html basically, the two cores are interconnected and the midi stream gets "tunneled" so you only have one MIDI I/O. The downside of it is that I doubt linking is supported by any prewritten MB Midi-Controller application (like MB64/E), so you'd have to program your own app. But the linking-features are nearly all handled by MIOS, so if you got some minimal experience in programming, it shouldn't be a big problem... You may want to take a look at the function listing to get an impression: http://www.ucapps.de/cmios_fun.html As you could use the source of the "ain64_din128_dout128" application as starting point, I think it's a manageable task :) See C-Applications on bottom of the download page. - and I can't find anything about the NG, too. sorry :-\ hope this helps a bit ;) best regards, Michael

Ok, don't want to hold back anyone from searching - ...but I wonder why you don't want to search here: -> "PSU": 14 pages(!) of topics about PSUs -> "PSU Schematic": 4 pages A quick test and I found about three different schematics for various purposes. A look at your post-history revealed that you're interested in a SID and/or FM. As I've written before, it makes a big difference if you just need +9V (best is about +7.5V for the Core) or -/+12V as required for the FM for example. There are really lots of postings about SID PSU's - ...and on the OPL3 page (module for MB FM) is a PDF schematic and even a PCB layout for an FM optimized PSU. I know that the informations are a bit widespread on these three pages ucApps/forum/wiki, but it definitely does not hurt reading the MBHP module pages on ucApps for the modules you want to build. I thought you already got my hint on your LCD-question :-\ Regards, Michael

The main question is: for what? The main answer will be: please search the forums. Here are dozens of PSU schematics, esp. for SID and FM PSU's that require negative and/or higher voltages than 12V. For everything else (between +5 and +12V): get an universal PSU, with about 800 mA. They are so cheap that it will be more expensive to solder your own. And if you build yourself a PSU: be careful! 120V/220V may be deadly. This is definitely not a recommended project for electronic newbies! Michael