Durisian

Awesome work tashikoma!! Can you post details on the box and other hardware - what you used? where you got it? how you made it? any problems you came across and solutions... Cheers!!!

Hi bagong Most of my parts come from Rockby Electronics in Melbourne. However most of the parts are available at Jaycar at a higher price. PIC's are hard to find. I recommend getting parts kits from Smash TV's store in the US. You need to order the PCB's from here anyway - so you may as well save some time and hassle. LCD's I get from a few places - Rockby, Futurlec (I have had no probs with futurlec over 20 or so orders, but a few people here have reported very bad service - lost shipments etc). And a local importer of displays to get a large character display, but I can't remeber who that was. Some harder to find parts (ULN2803 IC's for instance) I had to buy from Mouser in the US. $60 to deliver, but was here the next day. Awesome footswitches can be found at Banzai Music in Germany. (Delivery was much more reasonable here) There are some great soldiering guides in the wiki, along with connections and information about what each module does and how it connects - It's the same for all midibox projects. If you need a DIN module for a project, it hooks up the same in every project. Smash TV's site also has PCB layouts and jumper descriptions, so you can find where plug each module in You need to do a lots of reading, and plan it all out on paper - then you can ask questions as you get stuck, before you blow a whole lot of money on parts you don't need

All round update 2.6beta1 Fixed critcal rig control bugFixed lagging with MIDI input while in Pedal Board mode. (May have wrecked led indicators in the process though)Relays can now be labeled and polarity set from the PB Editor softwareReduced max cuelists to 20Added MIDI as AIN feature - allows a recieved CC to be translated as if it were an analogue inputAdded PedalSwap feature - temporarily change the settings of expression pedal Pedal Board Editor 2 Software has been completed (including MIDI upload support) and is now safe and stable. The old java PB editor is no longer 100% compatable. But it can be used PROVIDED - you don't use more than 20 cueslists, you don't use relays and you don't want to use PedalSwap. I've also whipped up a more complete usage manual All downloads can be found in the wiki - http://www.midibox.o...al_box#download

got it going unsigned int extended_MIOS_EEPROM_Read(unsigned int address) { EEADRH = address >> 8; // set eeprom address high byte return MIOS_EEPROM_Read(address & 0xFF); } void extended_MIOS_EEPROM_Read(unsigned int address, unsigned char data) { EEADRH = address >> 8; // set eeprom address high byte MIOS_EEPROM_Write(address & 0xFF, data); }

Hey Guys! I'm trying to read and write to the internal eeprom of a pic18f4620 I seem to be only able to access the first 256 bytes Basic run down: Init - for (i=0;i<0x100;i++) MIOS_EEPROM_Write(i, 0x41); // letter A for (i=0;i<0x100;i++) MIOS_EEPROM_Write(i + 0x100, 0x42); // letter B for (i=0;i<0x100;i++) MIOS_EEPROM_Write(i + 0x200, 0x43); // letter C display_tick MIOS_LCD_CursorSet(0x00); for (i=0;i<0xf;i++) MIOS_EEPROM_Read(i); Shows CCCCCCCCCCCCCCCC I expected AAAAAAAAAAAAAAAA also display_tick MIOS_LCD_CursorSet(0x00); for (i=0;i<0xf;i++) MIOS_EEPROM_Read(i + 0x100); also shows CCCCCCCCCCCCCCCC Is there an issue thats not letting me go over address over 256?... or more likely - am I just a retard

Alpha version of the new pc editor available OUTDATED No midi support as yet - but you can load and save pbx, syx, and rbs files For getting data to your box you can either load up your saved files into the currerent pc editor. Or use syx files with midiox or MIOS Studio 2 Still a bit of work to do - namely MIDI support and simpler device value map authoring This is alpha - better keep a backup of any save files just in case Enjoy! edit by nILS: I attached the file, offsite doco bad... edit: thanks nILS - all uploaded to wiki now PBEditor2_v0.8a.zip

Finally got a new PSU for my PC today with it i've got some updated software http://www.midibox.org/dokuwiki/lib/exe/fetch.php?media=pedal_box:pbx_2.5b3.zip Fixed critcal analogue input bug Fixed startup display giberish Added better relay support (hard code only - pbx_relay_config.h) - Virtual polarity (on when off, off when on option) - Relays can be named - When relays switch - can display something meaningful (like Input 1, Input 2 instead of just on, off Probably some other stuff - I just can't remember

Thanks qwasq. All my midibox stuff is in pieces - and development PC is still dead. I'll download my code from the wiki during the week and try to get a fix asap (it's most likely something very simple) As another test - can you wiggle a pot (any but number one) and then access the setup mode - i want to know if it says your configuring the correct input. Sorry guys edit: I checked the code for finding the right info - at a glance it reads as though it should work Could be the PC editor dumping the same info for every pedal onto the bankstick! A good test would be to export a sysex file of the master bankstick, and then import it back into the editor and see if all pedals are changed to the same as the first OK - think I got it! even if it doesn't fix the problem it's definately wrong (trying to pump a number thats to too big into an unsigned char - which is the all important value that points to the start address of the desired pedals settings) Try this - pbx.h line 30 void fill_found_control_info(unsigned short int offset, unsigned char master_entry, unsigned char master_entry_length, unsigned char skip_name_bytes, unsigned char sub_entry, unsigned char sub_entry_length); Replace with: void fill_found_control_info(unsigned short int offset, unsigned short int master_entry, unsigned char master_entry_length, unsigned char skip_name_bytes, unsigned char sub_entry, unsigned char sub_entry_length); and pbx.c line 467 void fill_found_control_info(unsigned short int offset, unsigned char master_entry, unsigned char master_entry_length, unsigned char skip_name_bytes, unsigned char sub_entry, unsigned char sub_entry_length) Replace with: void fill_found_control_info(unsigned short int offset, unsigned short int master_entry, unsigned char master_entry_length, unsigned char skip_name_bytes, unsigned char sub_entry, unsigned char sub_entry_length)

ok... I can assure you it used to work - its kind of the point of this project I'll try to get an older pc up and running in the next few days so I can re-configure my pedal box and confirm it still does (my pedal board is still in a 1000 pieces). Also try uploading and app like one http://ucapps.de/mios/ain64_din128_dout128_v2c.zip just to confirm its software related

Make sure AIN_NUMBER_INPUTS is 4 in pbx_config.h Also check that you are connected to the first 4 ain inputs (A0-A3), not the last (A4-A7)

mmmm... can you hook it up to midiox and check the message thats being sent (if at all)? A bit bizarrre... Please post your pbx_config.h file This is going to be guesswork for me... my pc fried last week

Hi Tash Nice and simple, I love it! pbx config is a bit weird, doesn't help that it's all screwed up in the wiki - i must fix that. I'm curious how you got the cutout for the LCD so neat - What's your secret? Cheers!

I have no idea. the switches should be fine, the expression pedals might more complicated - depends how they work. The physical space inside the J12 might pose a problem aswell. You'd have to crack it open and work out where you're going to mount the MB modules. Yep. I also suggest getting the kits so you don't have to shop around for all the parts.

Cheers David! Nope, it's for the display features and so you can get feedback - eg, some devices when you send a prog change will send a report of CCs, this allows the board to reflect those changes. Unnecessary in your case. PB supports up to 8 relays - as yet I haven't documented this stuff very well. I have an unreleased update to PB that has better handling of relays, but it's currently only editable in the source code - Finding the storage space in the mess of bankstick data I made is proving difficult. I also have a relay PCB that has 1 input switcher 4 fx loops and 3 basic switches. I built it about this time last year (just before my work became impossibly busy... and hasn't let up all year, which is why I havn't been around) I'll dig up the design if your interested. The one I had made had a critical error, linking 9v straight to ground... oops!... luckily - a quick bit of work with a knife and a new regulator - all works great! No, can't use buttons. However you can use the pc editor - way faster than trying to program directly on the board anyway. I'm also working a new pc editor (in VB.... i know, i know. But it's sooo easy!). But getting it to talk MIDI is proving very painful. While the app is a massive improvement - currently you need to use midiox to send the sysex files. It used to be, but now there is too much code to fit on the 18F452. So yes you need the 18F4620 Just for interest sake. My own Pedal Board is waiting on some cash (and time to do the CAD work) to have steel enclosure made. Aside from that - just a few footswitches to solder. oooo, and fitting the pedals, that parts going to suck.

I'd say your best bet is to gut it and put midibox modules in (unless you have some Johnson gear and need it for that). Probably the only thing you'll have left of of the J12 is the case, footswitches and pedals. Can't guarntee it's even possible though

Thanks TK. All of the above :) I used dout buttons app for confirmation. Been using a bank of 8 leds for testing (I've checked the connections a hundred times). Tried diffferent DOUT boards, different SR's. Always the same. It's been about 18 months since I tested with a multimeter though. I'll check it when I've got a few minutes to breathe again I've always just dealt with it, till now when I fkd up a custom pcb for relays. fixed by swapping pairs on the ribbon cable around, but it hit me that it didn't make much sense (nothing did 18 months ago :D).

This has been bugging me for a long time, On my DOUT boards from Smash, the pin assignment seems weird. When I activate Pin 0 { MIOS_DOUT_PinSet(0, 1); } J3 D6 is triggered, at pin 1 J3 D7 is triggered. going upward is D6, D7, D4, D5, D2, D3, D0, D1. Then it goes to SR 1 and repeats the order Is this correct, or is there something weird going on?

very well - restored

because it's pretty(er).... isn't 'home:project' the starting point for projects - that people browsing the wiki will come to?

sorry, i've been kind of thinking aloud by just doing - and then having to work so I get stuck before finishing (I'll try to curb this poor form) - ide's weren't meant to end up as one offs, just cross-platform compatible pages (but I didn't get that far) perhaps core toolchain needs to be changed to just 'toolchain' with a few options - toolchain:core toolchain:codeblocks toolchain:etc home:software ?

project namespace updated so they are not split stryd can you move the midi mapper images from this to the right place?

yehaa! Twinny - Is it possible to rename the actual root to something other than home - like midibox at the moment in 'You are here' we get Home >> home >> etc >> etc

There are no right answers... :) I thinks strydys preparation page needs to be broken up into more specific parts - rather than one generalisation. What goes where.... Give it a go, if we don't like it we'll change it later - a start is better than not at all. troubleshooting + skills - maybe the same as prep, needs to be broken up... mmm... not convincesd... pass. Both are too general to put in mbhp. soldering is a skill... maybe... [[.:skills:etching_pcbs]] [[.:mbhp:parts]] [[.:skills:preparation]] [[.:skills:soldering]] [[.:skills:constructing_enclosures]] [[.:troubleshooting:home]] [[.:troubleshooting:mios]] [[.:troubleshooting:mios32]] [[.:troubleshooting:midi]] [[.:troubleshooting:hardware]] [[.:troubleshooting:apps16]] [[.:troubleshooting:apps32]] ?? sorry phil - at work... maybe once the rehearsal gets under way... The point of having them in every module/project is so a newbie can start with the MB64 page and work their way through it - rather than having to find all the info first

It dawned on me last night that there no namespace for hardware type things, such as tools, enclosures, soldiering, etc... I thought :hardware... but doesn't really cover it. suggestions?

go from me too