philetaylor

Thanks, I knew it would be something stupid that I had done... I even remember you mentioning that in the FatFS thread but I just didn't notice... I also had to declare the tmp_buffer outside the fuction for the same reason :) Performance isn't bad considering the amount of work it has to do :) [3041271.692] Mounting SD Card... [3041271.696] SUCCESS: SD Card mounted! [3041277.446] dir [3041277.449] Volume in Drive 0 [3041277.449] Directory of 0:/ [3041277.449] [......a] 03/04/10 11:11:30 AM 13094673 HP-3D.zip [3041277.449] 3967488 KB total disk space. [3041277.450] 3967056 KB available on the disk. [3041288.163] copy hp-3d.zip test.zip [3041366.618] Copying /hp-3d.zip to /test.zip [3041366.619] Copied 13094673 bytes in 78 seconds (163 KB/s)!

Here is a .hex file to try, all functions should work except copy. TK: could you look at the copy code if you get a chance? It is just hanging on f_open and I can't work out why???? Cheers Phil project.hex

The updated app is in the trunk/apps/troubleshooting/sdcard_tools directory of svn. If you don't have the build environment setup, please let me know and I will send you the hex file. It uses the MIOS_Studio 2.0 console to send simple commands to sdcard_tools which allow dir, cd, mkdir, rename and format. Please be aware that the format doesn't currently ask for ANY confirmation, it just does it! I am working on the file copy routine at the moment, it should be completed later todaym :) Cheers Phil

Try reformatting using this program http://www.sdcard.or...mers/formatter/ It should reformat the card correctly... If possible I would connect the card directly to the PC (or through a USB adapter) rather than using it via mbseq. EDIT: Make sure you turn on "FORMAT SIZE ADJUSTMENT" !

Good spot, I missed that it was FAT12 :) DOSFS is supposed to support FAT12/16 and 32 but as you say I have never tried it with FAT12 either.... If it doesn't work, it should be posible to reformat the disk as FAT32 I suppose? Cheers Phil

Interesting..... Can you tell us exactly what make/model/type the 16MB card is please? I guess that there is something strange about that card. It appears that it isn't being initialized properly. There can be various causes of this, the MIOS32 driver attempts to initialize as per the SD spec but some cards deviate from the spec. I know that MicroSD cards don't "have" to support SPI mode (which is what we use) but all other cards "should" work :) Cheers Phil

The CORE8 module has 3 'layers' of software. Bootloader: Only knows how to send an upload request and program the flash if it receives a response. If no response, it starts MIOS if it exists, or reboots if not. MIOS: Handles all communication with all devices but not very useful on it's own (displays READY on an LCD !!) Application: This is the bit that tells MIOS what it wants to do. Once you have the bootloader on your PIC then MIOS and the application can be uploaded over MIDI (use MIOS Studio or MIOS Studio v2 to do this) http://www.ucapps.de/mios_download.html has downloads for all of TK's completed applications. There are other apps available as well that people have created for other projects. Take a look at the wiki for more information on these. The advantage of an LCD should be fairly self-evident. It lets you see what is going on :) Cheers Phil

I think that the extra fixing points that wilba indicated on the wiki entry are not necessarilly needed. I am using just the standard fixing points that are on wilba's original panel (with hex stand-offs epoxied into the 2mm blinds) and it is rock solid. As Julian has pointed out (a few times now) it isn't that easy for him to create threaded blinds and being only 2mm deep, you will not get much of a thread anyway :) If I get excited and press too hard on one of the buttons, there is a slight flex of the PCB but no more than I have seen in "professional" equipment. Cheers Phil

Yes I noticed that... Have you thought about moving to FatFs? http://elm-chan.org/fsw/ff/00index_e.html It seems to be a pretty complete FAT12/16/32 implementation including LFN support :) Cheers Phil

I suppose it depends how they are connected to the PC. If it is by USB then each CORE32 would appear as a seperate MIDI port on your PC. You would probably want to give each one a unique name in mios32_config.h though The PIC ID is really only useful when you have x CORE8's connected together (using MIDIbox link/MIDIbox Network) but only a single MIDI connection to the PC exists. This situation is unlikely to occur with the CORE32 Cheers Phil

I think that is a safe bet as the OP hasn't posted on the forum since September last year ..... Phil

They are a sort of bluey green...... I am perfectly happy with the white, I don't want to take it to bits "again" :) Phil

PIC18's have an operating voltage range of 2 to 5.5v so you are within the maximum limit (just). On the basis that the PIC is the most important component there, you should be OK. You are outside of +/- 5% which is what is generally considered acceptable PSU tolerance though. The only concern I would have is if the voltage was originally closer to 5v, this could indicate possible failing components in the PSU (The .3v could be AC ripple if the regulator is on the way out) but I don't know the design of the C64 PSU so this could be normal? Cheers Phil

I found a sheet of 2mm perspex at the office but to be honest, cut with a dremel and stuck on with uhu they look a bit crap so that would be great if you could :) Cheers Phil

I like the green as well, it matches my EL backlight :) Phil

That sounds like you are not receiving MIDI back from the CORE/sammich, when you say: Did you also connect the MIDI OUT of the sammich to the MIDI IN of the UA-25? Midi is a one-way protocol so you need both in and out connections to receive feedback. This also explains why smart mode didn't work in MIOS Studio (manual mode should never be required if MIDI IN/OUT is working OK) EDIT: You say you got the upload request so the above may be nonsense..... Did you definately get the request? Cheers Phil

Yes they are.... Bit of an ordering mistake :) I managed to buy a cheap EL invertor though and I think they look pretty good! Cheers Phil

I think the point is that a MIDIbox is not just the MBHP_XXXX modules, in fact they are a fairly small part of it. The software that has been developed and refined by TK over the last 12 years, namely MIOS and the MB_SEQ (which the MB-808 is based on) is the biggest part. These are 100% developed in PIC assembly so it would not be that easy to port to another platform, TK first started the STM32 port over 18 months ago and although he has made massive progress, much of it is still "beta". The MB-SEQ/MB-808 are complex programs with thousands of lines of code and I really can't see why you would want to re-invent the wheel recreating it on something like the AVR which doesn't really offer much in functionality or performance over the PIC device. Cheers Phil

I'm sure there is but it is pretty straight forward. Many CC (control change) messages are actually 14 bit capable. For Example CC 0x0 (Bank Select) can just be the MSB of the bank select CC. Sending a CC 0x20 provides the LSB. The beauty of this type of implementation is that if just the LSB changes (a small move of a fader for example) then only the LSB needs to be sent. http://www.midi.org/...idimessages.php Gives a list of the available messages. Another option is to use the MSC (MIDI Show Control) protocol which is designed specifically for show cueing and uses System Exclusive (SysEx) messages: http://www.richmonds.../1992Summer.txt Cheers Phil

No problem MIDI already has provision for this, it is called 14 bit controller messages, it involves sending 2 messages, one for the MSB and one for the LSB. Cheers Phil

I really wish people would stop telling me about these toys Seppo..... I have just ordered a Micro VGA to play with Expect to see PICS of my MIDIbox projects using my 46" LCD TV as a display soon !!!! I don't have a problem using these commercial modules, rather than build my own MB-ETHernet module, I bought a commercial one..... Cheers Phil p.s. Got it from http://www.mcustore....ay_Adapter.html £29 inc VAT and delivery. EDIT: It also includes a PS/2 keyboard socket which is useful for naming scenes/chases etc....

TK found that once ported to C++, the new MB_SID application was actually smaller and slightly faster that the C version (which surprised us both at the time). The problem with VGA is always the framebuffer, a 640x480 mono screen requires 38400 bytes of buffer RAM (over half of the CORE32's RAM). It isn't impossible though, if you are only looking for a basic text screen (like used by many lighting boards) then an external charater generator/framebuffer would be an option but a full graphic screen is going to be difficult. Something like these from EA would be another option. They are quite expensive but they have simple commands for creating windows/icons etc. The maximum size is 480x272 so not exactly VGA..... My interest is also slightly selfish as I have been looking for another programmer to work with me on the MIDIboxDMX project :) Cheers Phil

I know that in todays modern world of Gigabit (or 10Gb) ethernet, 31250 baud sounds incredibly slow but each note is only 3 bytes so that means you can play over 1000 notes per second, which is more than you would ever need even for the most complex piece of music :) Even if you are sending lots of CC messages, you would not really saturate it. Of course MIDI over USB (as used by the CORE32) does not have this limitation...... Cheers Phil

To be honest, that was my motivation for starting the MIDIboxDMX project in the first place, I have used many different manual and programmable boards in the past (Strand, Zero 88 Avolites etc etc) and I always find them either too basic or too complicated and I wanted to create something that was somewhere in between Phil

That's only 2 DMX universes, no problem for the STM32 sine curves can be achieved with a simple lookup table so the amount of processing required is minimal. Don't forget, the STM32 runs at 72Mhz... I wouldn't dismiss it out of hand. EDIT: You can also write MIOS32 apps in C++ now, look at the MB_SID_V3 ! Cheers Phil