audiocommander

this is looking awsome :o (and besides I love Flash Gorden Retro-SciFi-Style ;D ) I see, the switch seems perfect for your needs and it should be easy to wire. You want to take a look into "mios_pin_list.txt" (it's also in the download section of uCApps.de). It contains valueable information on the pins of the core and if you can use them - so to speak you are free to use nearly any free pin, not only remaining AIN-pins (=> possible future upgrades?) Besides, this list contains the IDs (eg. "RC5"), that we need to refer later on by code. It's much easier with a DIN-board, but it's not really more complicated without. I will help you, if your application is written in C. If you use an assembler application or an assembler based ready project, I have to pass (though I'm sure, someone else can help in this case ;) However (for MIOS-C-Applications): When using a DIN-module, you have a function called [tt]void DIN_NotifyToggle(unsigned char pin, unsigned char pin_value)[/tt], it notifies you automatically whenever a DIN-state changes. When using no DIN-module, you have to check the state by yourself. The basic concept is to set up a timer with [tt]MIOS_TIMER_Init(4,10000);[/tt] (please anyone correct the value if inappropriate :-[). In the function [tt]void Timer(void)[/tt] you have to check the pin states by yourself (for example: [tt]if(PORTDbits.RD4) { ... }[/tt] checks if S0 from J10 of the Core is selected. Additionally we need to have a variable that stores the last state, to prevent any looping unnecessary executions. That's all. If I know the application you're using, I may add a WIKI tutorial on how to connect and use pins as DIN. Regards, Michael ...and don't forget the resistors, when connecting the pins to the switch :)

well, apparently I've not gone this far. The speakJet sais R-E-A-D-Y (lucky me it does not say E-X-T-E-R-M-I-N-A-T-E ;D), but apart from that, the lowPass filter as described in the manual seems to pass out the whole signal and I go no luck sending serial data yet, not even succeeded to exit the demo mode yet (neither by RS232 nor via IIC). hummm, I think I'll have to take a break and then check my breadboard again. :'( I think the lowPass filter is really needed because there is a steady noise in the low frequencies (if I listen closely to the mini-loudspeaker) @stryd_one: I got the feeling it's better to run a few test, before revealing what I'm trying to do... but my head is full of nice sensoric ideas about glibberish yodling voices apparently gone crazy ;D

Yeah, I'm the speediest typer ever ;D Don't mess with the man who types faster than it's own shadow ;D ;D hehe...

So are you going measuring analogue voltages with an AIN or switching digital with a DIN? If you're sticking to analogue, I can't help you further, 'cause I can't see any advantage about that proceeding? - if you meant, you now have a standard 3-pole-switch connected to 3 digital input pins (DIN or Core), here are some questions: Are you using an DIN-Board and if not, what exactly what Pins on the Core do you use? Have you found the PDF where connection of switches (and one resistor for each) are described and did you follow that? We first have to make sure, the hardware is connected right, before proceeding to software! ;) Regards, Michael

May I ask what you are trying to archive? Why do you want to encode MIDI Messages? When you split faders and pots over multiple Midiboxes, I think you don't have different cases but two Core Modules in the same housing. So you need a Core-to-Core-Link as described in the link I posted above. You can send every message you like from Core1 to Core2. MIOS is taking care for marking the messages, so they do not leave the last Core! Or am i missing something ???

That clearly depends: Tick() is called every tick (as the name sais), so this will be quite often, so to speak a lot more often than AIN_Receive Display_Tick() depends on how often it's called. If you call it every time AIN changes, it will be the same as in AIN. So except having unordered code no gain. Timer() would be suitable if set up right, but: the question really remains: Why not sending CCs? => http://www.ucapps.de/midibox_link.html "(...) not only common MIDI events, but also other informations can be transmitted without reaching the host software at the end of the chain" Regards, Michael

I had also voltage-problems when using two batteries, but then I remembered, I once measured much more voltage from a cheap power supply than expected; so I tested all my supplies and got lucky with the second one! Although it says max 12V I can measure 18V!!! (The cheapest one from Reichelt btw). So, before going out and buying an expensive 15V power supply, it might be worth testing the ones already lying around. The PicBurner went very well without batties ;)

henrygr, have you looked at the links I posted above? The main information is contained in an example from the download section, so the code is there, waiting to be read. I don't know about your project and I'm not used to organs, but I assume if you don't have no DIN-module, you're not using one of the precompiled applications, but trying to customize your own thing, right? It might be worth reading this article if you haven't done so: http://www.midibox.org/dokuwiki/doku.php?id=application_development You need to install SDCC, GPUtils and all the other things described at uCApps. Then load the C-Skeleton from the uCApps-Download-Page. You just have to add a couple of lines to the NotifyDIN-Functions ("pseudo-C": if DIN1 do this and that; else if DIN2 do this; else if DIN3 do this). Of course you might also code ASM, but I wouldn't recommend if you don't know it. The hex-file is the result of compiling the application code, so changing lines there is no good idea (except you speak machine code ;D ) Regards, Michael

I'm not sure if I understand your question right, because I don't know what an "analogue switch" should look like... ??? If you're searching for a hint on how to connect one or more buttons to a DIN or directly to the Core, see here: http://www.midibox.org/forum/index.php?topic=6717.msg42619#msg42619 and here: http://www.midibox.org/forum/index.php?topic=6528.msg40953#msg40953 You might also connect a multistate-button (DIP-switch, 3-state-slide-switch, radio-button-matrix ....) to more than one input (eg. you need 3 DIN-Pins for one 3-state-button), that seems a bit easier and more relyable than defining an analogue pot-range, esp. if you're not used to programming. If you have additional questions, feel free to ask ;) regards, Michael

actually I was referring to my FSR-sensor, which I adore. Though somewhat unspectacular, they are very well playable - good responsiveness; and with a proper tested load-restor-value astonishingly accurate to control - altough they also return to the inital state on release (but it's easy to store and retain the last value by code if necessary). It has instrumental qualities since I learned how to finecontrol my finger pressure :) I have mixed feelings about the spectral distance resistors. :-\ They are quite impossible to order here in germany, so I have only some samples. Some of them (8cm, 10k) are very good to use, one 360° round pot makes troubles, because it creates a short on one special point, the other one does not show this behavior. Using them as "encoders" needs some lines of code. I don't know yet if it's worth the pain, because: All of them need to much pressure for my taste and that makes it difficult to get a smooth response. The touch-distance-pot as seen in the Electribes has a much better responsiveness (threshold), but I have no clue where to get them. :-\ I have also one with 15cm legth, that must be damaged, because it keeps snapping back to a middle value on release, wich makes it unuseable. First I wanted to use them as volume-controllers (along with LED-Levelmeters as state indicators) but for absolute or visual controlling they are not suitable. For pitch or modulation / intuitive audible controlling purposes they are ok. I thought they were cheaper and cooler than motorfaders, but the spectra stuff is really expensive for small amounts, too. Because most of them don't have 10k but rather 8k or 47k, I need these load resistors, otherwise the AIN-measures go crazy; and it's true, now that I know it, I can see a slight nonlinear behavior. But it's tolerable, because they're not made for accuracy anyway and artistically spoken, I'm more interested in making music "controlled by ear" and therefore try to reduce the visual interface as much as possible. ;) Michael

Hallo puddingbrumsel, willkommen an Bord. vielleicht solltest Du dir mal im Wiki die ersten drei General-Einträge durchlesen, das gibt einen guten Überblick. Prinzipiell: machbar ist alles, es ist eben nur eine Frage des Aufwandes und deines Ehrgeizes. Bei digitalen Controllern musst du erst rausfinden, wie die technisch aufgebaut sind. Solange du einen digitales (AN/AUS) Signal empfängst, ein PS/2 Signal oder aber einen 10k Potentionmeter-Wert, kannst du das Zeug direkt an ein Modul bzw. direkt an ein Core hängen. Wenn nicht, dann könnte es komplizierter werden. Wenn du nur CC's senden möchtest, ist es ziemlich einfach, sich eine Anwendung in C für MIOS zu programmieren. (Siehe hierzu 'Application Development' im Wiki!) Genaueres kann man aber wohl erst sagen, wenn du die Teile mal aufgeschraubt und untersucht hast. :)

Ahh, I see! As I'm working with sensors most of the time, I haven't noticed this, because it's hard to measure the linearity of my own finger pressure ;D Kewl to know that.. Thanks, Michael

here ya go: http://www.midibox.org/forum/index.php?topic=6506.0 try an additional load resistor of ~7k and tell us if you got it going... ;) Isn't every standard AIN-10k-Pot connected parallel? Or does this apply only to non-10k-resistors? ??? Michael

I tried with Eagle but failed and because X11 is sooo ugly on the mac :-X , I switched to the program I know best (what doesn't keep me from hating it ;D) it's FreeHand. As I cannot etch anyway - and fh supports symbols and layers - it's just perfect for designing and printing... If anyone wants to have the .fh or .eps, pm me! Michael

I worked on a breadboard layout of the mbhp_iic_speakjet_v1_0 layout incl. LowPass filter. Maybe someone wants to take a look? http://www.audiocommander.de/pics/sonst/mbhp_iic_speakjet_05.board.printout.pdf (Edit: this link is outdated, see later postings!) It's not yet tested, I hope I can build and test it this weekend, Regards, Michael

Yeah! I had the luck to play with it; it's really a great piece of work. The controller seems to do a good job for musical control. I just have taken a look at the small video of the website and noticed that there is no sound. The exhibition piece is more a musical sequencing tool than a plain visualizer. ;)

led's as touch sensors http://www.midibox.org/forum/index.php?topic=5709.0 LEDs as optical detectors http://www.sensorsynergy.com/helpfulhints.htm LED Touch Sensing http://mrl.nyu.edu/~jhan/ledtouch/index.html justDIY » LED Sensors http://projects.dimension-x.net/archives/35 LED Sensor Array http://forums.linear1.org/index.php/topic,469.15.html Keep in mind, that these LED faders would also return the Z-index, so they could be used for a lot more than just fading (eg. choose and confirm, level+modulation and so on...) :)

actually, I've been exhibiting recently and there's also been an artist named Julian Oliver (see Fjiuu), that made a really nice piece using a PS2-Controller and just OSS (I haven't checked yet, but he told me they'd release their software)... It's exhibited in London until 20th May: http://www.cybersonica.org/artists At Cybersonica you'll also find a PSP-Controller and an iScratch (iPod that can scratch)... but that's for the ones with a few more bucks in the pocket ;D rgds, Michael

don't worry stryd_one, I don't get it either. Although it's interesting having read that such a possibility exists, I would leave my fingers from it. This sounds really dangerous, because it contains several traps to step into if you're changing smth later... If you really need more than 256 array elements, it might be of wiser to group the items and use some #defines (Besides 256 AINs? 256 LED's? No... maybe 256 DIN's? Man, that seems like button-hell ;D I just counted 110 keys on my computer's keyboard... )

I don't know if it's different in other contries: in Germany you can do it the "hard way" only if you insisted on an insured and ID-tracked shipment. Only then you can go to lawyers or the police. The risk is always on your side from that moment on, the item has been (or claimed it has been) given to the postal service agency. If you own a tracking-ID, you can prove that it hasn't been delivered. That's the only chance. With expensive goods, it's best to quickly open the package, if the postman is still around ... he or she'll wait for a tip! ;) So for all bidders in Germany: don't try to spare 4 EUR on uninsured, untrackable items. If they get lost: no chance, no help, just gone forever... (That also applies for every kind of online shoppings, not just ebay!) Regards, Michael

..and there are also sometimes threads like "High quality 3 axis trackball assemblys with TTL output on ebay", started with an ebay link only - but now contain informations of a lot more value than a temporary link. (although I must admit that an info "Chap 2x16 LCD on eBay" is really quite useless ;D ) Michael

I agree too. It's good having some docs reserved to be filled with information. I was just about filling the application-docs and added a graphic about MIOS to prevent common postings like "can I do this and that with midibox". Maybe there's another one for MBHP following... I think, we just have to take a look at it from the pov of a newbie and at the same time from the pov of our needings to find infos quickly. I'd really like to see the two articles "what is a midibox" and "introduction to uCApps" a bit more expositioned, because I think they contain really useful infos (maybe I'm changing smth there the next days) It's only bugging me a bit, that the FAQs are too splitted, too long, have too much content and some don't really seem to be frequently asked. Maybe it would be useful to avoid filling the faq entries and instead put this information to the relevant sections and do a cleanup there... But all in all, I think we're on a good way The overall navigation has been really improved over the last few weeks. :D :) Michael

Woahoa!!! :o You're a star!! Thank you so much for that hint; I almost began to throw that damn thing in a corner. It's running now after setting both speeds to half! :D Michael

Quite interesting stuff you're working on ;D I'd like to get my hands on that LED-Input thingy, too... but unfortunately I'm to busy with other things right now. Controlling RGB LEDs seems to be one of my favorites, too :) At least you're getting nearer, so if you're dropping out totally from this community, I can give you a real kick ;D ;D Greetings from Nürnberg*, Michael * about 15 driving minutes from Erlangen ;D

uhm, I think I have similar problems with P18. I just burned successfully some PIC16F's (I couldn't try them, but they seem to be okay, no errors or whatsoever); but now I'm having trouble with burning PIC18F's. I passed all tests successfully, the burner is recognized, the chip detected, but I always get about 30 - 80 errors in PROGRAM, although there are no errors in ID or EEPROM. I tried to erase everything and then burning again, but this made no difference. I have a new parallel cable, highQuality IC-Sockets, the chip is sitting right and good in the socket, 18 V Power Adaptor (no batteries - exact 12.51 V at the Poti) and tried it with two different PICs, both produce the same errors when verifying (with Bootloader v1.2). That's very sad, because this programmer is a hell lot faster than ol' JDM. :( Maybe it's got to do with P18-Burner? PicBurner for the PIC16s seemed to have no problems... I'm trying other cables tomorrow. If it does not work, I have to go back to the JDM :( :( Keep you updated... Cheers, Michael