audiocommander

Hi Luca, first of all, it is no problem that you don't answer at once, on contrary: it is better to try, test and think about and then return with your results. So you're behaving fine :) I have no in-depth knowledge about all the sysEx error code messages, so here is one more suggestion: -> if you started your project 5 months ago, it is most likely you have the old bootloader v1.1 or v1.1b. MIOS v1.9 needs the bootloader v.1.2. so: what hex-file are you trying to upload? it should fit to your PIC ->

That would be (hypothetically ;D ) more than delicious! 8) Unfortunately I never created a PCB design, but maybe someone else here likes the idea? Just in case, here is the link to the original pcb for these button pads: http://www.sparkfun.com/commerce/product_info.php?products_id=8033

Hi, no need to ask ;) ...quote from the site: I'd be really interested, but I think 16$ (if we ever get > 100) + PCB + shipping to Europe would be... well... I'd have to think about it, but in general I'd be interested! Would you also buy the PCBs or would you organize these seperately (maybe bulk order at some PCB-service?) Regards, Michael

hey, this sounds great... maybe I should dig out my old PC :-\ ... ;D however, I also stumbled recently upon a tool, that's also available for Mac / Linux, called RvCad: http://www.robotvision2.com/Softwares/RvCAD/RvCAD.html It's a (freeware, but no oss) realtime video processing software similar to QuartzComposer*, but focussed on robotics, motion-/object-detection, head-tracker and (I haven't tried, but the website says) extendable by plugins... Cheers! Michael * ahh, of course, there's the Kineme plugin pack available now for QuartzComposer on the Mac. It contains a Midi-Out plugin... As far as I am aware no motion detection possible (no way to get numbers out of pictures), but anyway, maybe useful...

just delete the &sessionID=... from the link http://rswww.com/cgi-bin/bv/rswww/searchBrowseAction.do?Nr=avl%3auk&N=4294763100&callingPage=/jsp/browse/browse.jsp&Ntt=illuminated&Ntk=I18NAll&D=illuminated&obs=sObs cheers, Michael

huh, that solder seems to make 'em quite hot :-[ ;D (sorry, can't give credit, don't know who did this, found these one morning in my mailbox ::) ;D )

wenn du jetzt noch den counter wieder auf 0 zurücksetzt, dann geht auch alles wieder von vorne los ;) grüße, ac

ist aber der einzige weg sowas zu machen, wie es Wild_Weasel beschrieben hat. das programm muss ja irgendwie wissen, ob du das erste oder zweite mal drückst; also muss der "ready-status" deines buttons in einer variable gesetzt und dann abgefragt werden... grüße, AC

http://www.sparkfun.com/commerce/product_info.php?products_id=8033 ;) (thanks for the link, btw) cheers, Michael

Hello Luca. Welcome to the Forums. Sorry, I don't understand what you mean by: ??? To answer some of your questions: - When you upload files via Serges SysEx Loader, you have to send .syx files. You cannot send .hex files - When you convert MIOS to syx with the hex2syx.pl script, you have to force -os-upload. If this troubles you, just use MIOSStudio. You can upload the .hex file without need for converting it - IMHO the MB64 Application should need no change. A .syx-file should be in the zip-package. Just upload this one as long as you don't have no customized settings. - As long as you don't have multiple Cores linked together, the device ID should not matter (don't know how it is for serge's syx-loader). Maybe you should try uploading the .hex-files with MIOSStudio and see if that solves your problems. Best regards, Michael

Hi Robin, Yes, I think so. MIOSStudio provides two very good helps: First, you have an MIDI I/O Monitor, that means you see what goes in and you see what comes out (similar to MidiOx). In that case, where you're experiencing strange behavior of Midi_ox, it would be ideal to test wheather it's the software or not. Second, MIOSStudio has a very good implementation of MIOS Function Calls. You just have to select the function, type a parameter and press Send. Then you'll see the return values. (Of course you first have to setup the In- and Out-Midi Port, but that's all that has to be done to get this program running). So, in your case, you could separately check where the problem is. Send a single MIOS_DIN_PinGet(6) Function call and see what happens. If everything works, you'll know for sure, that it's in your code, then we'll see what to do next... Very strange behavior like this could be also a buffer overflow. Any variable storing a too high value for its datatype (eg. an unsigned char wants to store the number 1024, but unsigned chars are 8bit and therefor can only store values up to 255), puts the 3bit overhead-value just somewhere. And that's pretty unpredictable where the garbled data goes... In other words: think of filling 2 cans of water in a coffe machine that only can hold 1 can of water. The additional 1 can if flowing over. If it flows into the power-plug: BANG! However, when you change the code and the result is every time exactly the same, it is more likely to be another kind of error, because the overflow would happen somewhere else. All right, let's summarize: - the MIOS application crashes, the pic reboots if you press button 6 and (some button from 19 to 25) - DIN_PinGet(6) is working in some other parts, but no in DIN_Notify() - the MIOS app does not crash when pressing only pin 6 - the MIOS app does not crash when pressing any pin between 19 and 25 - the MIOS app crash shows in rebooting the pic and sending a sysEx string by the 2nd level bootloader right? I would first check MIOS_DIN_PinGet(x) with MIOSStudio. If this reveals no new insights, you should post a bit more of your code... I hope this helps, Best regards, Michael

hm, that's strange; can you post some relevant lines of the generated .asm file? we could check there if the result is software based – a reset of the box should not happen to my understanding. Here's another suggestion: If you have MIOSStudio running, you could setup your Midi-Connections and then go to the debug-window and call the MIOS_DOUT_PinGet(pin) function with pin 6. What happens? Does the box reboot? What happens if you poll other pins? Also rebooting? If yes, it is most likely there's a wiring-error on the DOUT-module. If it reboots only on pin 6, it's likely there's a wiring error only on that pin. If both pins are polled and no reboot happens, we know at least, that the problem is software based. Best regards, Michael

AFAIR the Application Icon jumped a few times in the Dock, then it quitted. No splash screen has been visible. As everything works now with JSE2 5.0, it's too late to check for any errors; maybe cimo can provide us with some more informations: can you tell us, if there are any entries in the Console (-> Console.app in Programs/Utilities) -> console.log ? Michael Edit: okay, I'm sorry I looked up my original post: http://www.midibox.org/forum/index.php?topic=5230.msg36441#msg36441 My memory did fool me. It started well, but did not work correctly; sorry about that confusion!!! ;D

I tried (see one of my first postings). MIOSStudio does not start at all with Java 1.4.x on the Mac, even with Plumstone installed. Best regards, Michael

no cable is required. As you can see from the screenshot, one card provides the master sync clock. I never noticed any issue; until now this worked great. But I'm not the one who recognizes 20 ms delays, so if you're cheesy with things like these, you should get another opinion :) btw: leopard (10.5.) is announced for spring 2007 ;)

It can be found in the "Audio Midi Setup.app" (Utilities in the Program Folder), Menu -> Audio; but I really think it's just possible since 10.4. (see img) I'd really do a search in the Apple Forums about Java for OSX 10.3. and GPASM is just a command line tool to compile .asm-files to .hex-files. it surely can be used within Xcode, as Xcode also supports asm. :) best regards, Michael

Hi Robin, it's me, the bracketizer, again ;D I could imagine, that SDCC is not at all capable of differenciating between deeply nested logical structures. To investigate this behavior in depth, one should take a look in the generated .asm file, located in the "_output"-folder. However, as we had strange issues in the past with brackets (such as [tt]myFunction[x+y][/tt] is not working whereas [tt]myFunction[(x+y)][/tt] is working) , I would suggest to express this line as followed: [tt] if( ((pin >= 19) && (pin <= 25)) && (! MIOS_DOUT_PinGet(6)) ) { group = 3; } [/tt] Does this help? If not, what sais the generated .asm file? Best regards, Michael Edit: and one more question: - is this the first time you're accessing the DOUT-module? just a thought, maybe it's hardware-related...

I fear that Java SE2 5.0 is not available for Panther (10.3.) Do you have the option of upgrading your mac? Tiger (10.4.) is a wonderful system with a bunch of new innovation, I wouldn't miss (Dashboard, Spotlight, Intelligent Folders... not sure if MIDI over Network and virtual Soundcards by chaining real devices were also part of the 10.4. upgrade... maybe you could ask in the apple.com/support forums? I think there must be some solution to get it running on < 10.4. Anyway, there's always the option of using SysExLibrarian from snoize: http://www.snoize.com/SysExLibrarian/ to upload the .syx files... IMHO still better than invoking VPC :-\ ...and you know that you can use gpasm instead of mplab? ...and you know that you can use Xcode for MIOS-C-programs? I've written a tutorial and step-by-step-instructions in the Wiki (->appDevelopment) You just need a PC to burn the bootloader; all the rest can be done with your Mac ;) Best regards, Michael Edit: uh, I just saw that this topic is a bit older; have you actually tried to install the referenced Version (link above)? Is the installer denying the install?

wow, that sounds like a great product. but this version is nearly 40$ and the product sheet sais: but this one here ( http://www.sparkfun.com/commerce/product_info.php?products_id=7956 ) is just 12$ and sais: I would definitely wait for the IIC Feature. Communicating via serial protocol would mean having to build another PIC16 based module. IIC would be super-easy, as it's already implemented in MBHP/MIOS... best regards, Michael

I doubt, you can read/write raw data so easily without a file system on a computer. To gain access for "normal" applications when using with a cardreader, the medium has to be formatted to be accessible as a volume, so that the PC knows where to write it's raw-data! Else you have to use very specialized software to gain access; I don't know of any (for the mac) right now; and I think this might be also some work to program such software, because it would mean to handle some very basic low-level stuff, that might be as complicated as writing a FAT-(or other fs)-driver for the pic... I could think of reading/writing to the card via the mbhp-midi-device itself; so that your application (MIOS-application) has a "thru-mode" where you can access the data on the card via SPI protocol. However, I think a proper implementation with rw-access for computers would be the right way to go, esp. if you want to store MegaBytes of Data. There are plenty of mp3-DIY projects, finding the right sources for a driver should be a solveable problem.

great music. that's the right soundtrack for this evening. I love the spanish/moroccan style and the french voice is very beautiful... thanks for sharing this nfo :)

oh, I had that soo often too. This is a real beasty annoying warning. I remember I searched two days the first time I had such a warning; it can be really hard to track that down. "Conditional flow changed by optimizer" means that SDCC finds something that can be optimized and changes the logic flow. The second line about Evelyn and the modified dog has been inserted by some funny programmer, it's from a song-lyric :) Looking at the code you provided, I suggest it may be somewhere here: [tt] if ((pin >= 1) && (pin <= 5)) group = 1; if (pin == 7) group = 2; more code [/tt] Maybe the problem is with an if coming right after an if; maybe that's confusing... If it helped in the past, perhaps it helps here, setting brackets, too? [tt] if ((pin >= 1) && (pin <= 5)) { group = 1; } if (pin == 7) { group = 2; // more code } [/tt] If that does not help, I recommend you take a look into the generated asm file, that's located in the "_output/" folder and search for "warning". This gives you a good impression where the error is located exactly. Maybe this helps pointing towards the problem. And if this does not help either: Can you add the line-numbers or make a screenshot, so we can see the codesnippet with line-numberings as it is in your file? Good luck! Best regards, Michael

Hello Christian, here is a quick guess from someone who never worked with a PIC 18F4620: As GLCDs are rarely used with MIOS projects (CLCDs are a lot more common), I can imagine, that some instructions on updating the MIOS-Code are missing in the WikiPage. And even more uncommonly are two GLCDs on one core... -> As for MIOS_HELP_Dec2BCD is a changement in the wrapper required, I think maybe this may also be the case with some GLCD functions? -> I suppose you checked the wirings of the GLCDs and make sure, they work? -> And you took the original precompiled MIOS, now also available for the PIC18F4620? ...or a custom modified version? -> AFAIR there is a conversion flag in the hex2syx-script: the MEM64k-option; have you set that? Regards, Michael

Yes, you should ground all unused pins, including those from the core. If you have one AINx4-board hooked up, you should have A0 to A3 connected. So A4 to A7 are free and to be grounded. Check TK's reminder here: http://www.ucapps.de/mbhp/auaimbctg.pdf I'm sure your issue will go away when you ground the remaining AIN pins on the core ;) Best regards, Michael ps: When some random data is received, I made the experience that you cannot rely on the pin numbers the application gives you. So don't give too much on pins 15 and 16; the error can also be on any other pin before or after.

of course we're planing to take over the world! and we begin with taking over the number #2 of most-replied-threads in this forum! uups... now I revealed our secret plans :-X ;D well, bad jokes aside: I'm just giving some coding tipps from time to time, but MTE and Wild_Weasel are up to build a Traktor-Box /-Controller with Scratching Features and DJ-stuff (if I got that right, please correct me if I'm wrong, after 8 pages one tends to loose the oversight... ;) ) They both have set up Wiki-Pages; there's some info in English, too: http://www.midibox.org/dokuwiki/doku.php?id=midibox_traktor so, no world-domination until now (puhh, what a luck!) ;D cheers! Michael