Durisian

cool. yeah, it's right on the edge of code space. LED's should work fine. It's just the Digits that can't be enabled.

... image seems to have been lost. I posted it right before the move. It's on my ... ehem ... work computer, So it'll have to wait a few days.

Hi Flo Hope i'm not cutting any toes here... I've whipped up an fx bypass schematic for part of pedal box. It should suit your project as well.

great! that's the channel issue I mentioned. Both master and device are set at the same channel. If you set your fbv custom channel to 16 you should see the appropriate text for your hd147 The master bankstick channel is pretty much irrelevant for pedal board, it's more for use with pedal box. But it comes first in the recieve chain, so it will override any device bankstick on the same channel. hmm... It will also be hindering you pod amp settings being recieved properly. If the pod is indeed sending them out

ah well, worth a shot you should be able to test if midi in is working if you change some settings on the pod. they should show up on the lcd (like amp or cab type)

It looks like amp settings to me... All that needs to happen is to enable midi input for pedal board. I can attempt to enable the midi input yep - Try this pbx2beta2aDEV Don't enable LED Digits, it won't complie do to lack of memory damn I'm having a bit of trouble following the scematic, but I understand the concpt. I like it. Actually... yeah - flo is working on something like this. Although his method will mean it won't be directly compatible. But will be a good source of info

It seems like an output midi port issue... (whether it's something in your computer or my software I don't know) Does the LCD say a bankstick is being updated? What's your computer spec? Could you try sending the upload to midiox. Midi Yoke can allow you to do this. If you tell midiox to recive a manual sysex dump, And start the upload (without using feedback) it should recieve something like 38000 bytes. Yep , i'd say that's it. The edit buffer command Now here's the really hard part, I need to know what that message is. I'm sure line 6 arn't going to be very helpful, i'll see. How many messages?? (approx) Not sure what you mean, tell me more. I was going with replace the switch in the stompbox with a PB relay (I have some stomp boxes I can't live without). That way making them controllable with rig control. A more common use for the relays would be amp channel switching. no problem ;D

pc editor fixed yeah! Some devices have a request controls command, which will ask it to spit out all its current settings (the pic18f4620 version of pb will support midi in for pedal board). This is something I intend to implement, This command would be sent straight after a program change. But in the line 6 midi chart I can't see a command that would do this. So I think your stuck with the hard way :( Which is to use Rig Control to do the program change and to turn anything on or off - I found another cool bug in the editor that was stopping patch steps being enabled, so you'll need the new version ;D

.... wha ... sorry, I think I've uploaded the wrong version of the pc editor. That bug was the last thing I fixed... Will fix it in the morning Error 24# is Bankstick Magic Number mismatch on bankstick# - So that would be expected if you can't open your device file in the new editor to upload it

Pedal Board Updated - added bankstick magic numbers There has been a slight change in the way data is stored on the bankstick. The updated PC Editor will update old files to the new format When I get a pic18f4620 and have more code space, yes.

ok... first I thing I see is that both are set to channel 1. This could be an issue. ..hmmm... ahhh.... Maybe the fixed button issue is remnat of an old bug. Try wiggling your pot a few a times first, then press the buttons. As a work around you could try setting the relevant cc's to Meter with on/off instead of on/off only. It will have the same effect your after. -------------WAIT I think you've mis-interpreted the momentary/toggle option. It doesn't mean what the hardware switch is (they must be momentary) When set momentary - when your foot is down it will be on, when you remove your foot it will go off. When set Toggle - when you foot goes down, the switch will change from it's previous state to the other. When you remove your foot there will be no change. Try setting your buttons to toggle (it makes no difference with program changes) ----------------- No grounding required for unused pins on DOUT's LED's on bank buttons - I could make that happen, I guess so when the button is down the led lights up?

I pulled a core from one of my other projects and loaded it up with PB. Everything is working, including the pc editor upload. My guess with pc editor is a pc output midi port problem. Just make sure you select the right one, and that no other programs are using it. I realised today that a big error occurs when another program has hold of a midi port your trying to use, but the editor won't tell you, it just won't work. ok - need to check your pbx file Hardware Setup looks fine... I'm not sure what your asking..? The file thats created with the big 'save' button. It saves everything in one file (a .pbx file).

FoneBone Sweet - coming along nicely Now that you've got this far i'll get my arse into gear and order a new core today so I can fix up any issues you find. Indicators: Things to try Set the number_of_srio to 4 Set relay SR's to 2 and 3 Seems you found an oversight on my behalf. There is no way to disable relays. Also try testing the LED's with dout_buttons - available in the ucapps download section under troubleshooting. This will make sure the LEDs are actually hooked up right. Buttons - So they never turn on?? Do they send midi? what about banked buttons? Can you pm me your pbx file Also a map of which button is connected to which pin My problems came from losing power half way through an upload (dogey power connection on my testing core). In my lazyness I would just repower without stopping MIOS studio, it had some interesting effects. The pedal board pc editor doesn't have a 'wait for upload request' option. As it only works with banksticks I didn't feel it necessary... I should add it in just to be safe.

oops, don't think i published the error codes yet... ;D 23# means the master bankstick has been uploaded to bankstick #. not 0 There is no format checking on the banksticks yet. So it seems it gives this error with new banksticks as well. The PC Editor is still very beta, and by no means complete. The problem is very strange though... Note: you shouldn't startup your midibox while your pc is half way through an upload - I've had to reload MIOS a few times because I did that. the 'Upload OK' could be a translation problem. I think it's actually saying "I'm ready for the next block". Which is also sent at startup i believe. Why it's not being recieved during upload I am unsure. ....hmmm... The only thing I changed after I fried my core was the LCD showing 'Bankstick (the number was supposed to here) UPDT'. This might be hindering the upload process. Try this: edit: link removed as it was not the problem I've removed the LCD update before upload. If it still plays up un-check 'use feedback from core'. And if it still doesn't work... I've got work to do ;D edit: added error codes to the manual in the wiki

Hi Levon Rockby - www.rockby.com.au Stock No. 13681 stryd - yeah - i'm in for at least 3, possibly more

Hi FoneBone I've just checked out the FX1 manual. I think what you want is when song number # (I call them patches in pedal baord) is activated. The buttons will change what midi events will be transmitted when pressed' date=' to match functions you would use for that song.- Pedal Board cannot do that. (it's a good idea and is something i've considered - but flash memory on the PIC has been the major limitation. Perhaps in the future I will add something like this. But don't count it any time soon). Instead when a song # is triggered, it sends out up to 32 standard midi messages (sysex is not supported) - See Rig Control in the Pedal box manual. However it can do this for expression pedals (cv pedals). Each input can be set to have a different midi message depending on the current patch.

... *wakes from hibernation* **thinks: damn my test core is still fried, hoped that would fix itself :( ** Hi Tel If I understand correctly, yes pedalboard will do it. I think the trick your after is the cue system (gig control) which allows the patches to be triggered in any order with next/prev 'buttons' The 'Pedals' can be set up to have different settings depending on the current patch. (i must admit i've never tested this when patch change is triggered by gig control) however the 'Buttons' can not. You have 16 buttons available and a futher virtual 128 that are banked under 16 buttons (usually these would be program changes, but if your using gig control to change patches you can set them to whatever message you want). I'm not sure why you want midi-clock (I assume you mean Midi Time Code) from a floorboard, pedalboard has no clock features. The tap tempo would only send a message to the o1v as a normal midi message, the o1v will then calculate the tempo bassed on time between recieving that message. Cheers!

yay, it works. Now onto transmit and recieve over the midi ports...

stryd: on the long drive home from work I realised that 1184 - 11 -2 is actually 1171.... ... ... typo + bad maths = stop thinking about midibox and get more sleep ;D I was trying to point out that I had obviously missed something because there wasn't enough bits in the sysex message by my calculations. As it turns out there is 5 to many, I would say this is where my algorithm (for both directions) goes wrong, it doesn't account for these extra bits. This is what i've been missing I didn't pick it up earlier because I was using mbasecalc for the math, where anything after the decimal point is ignored :-[. And also by cutting corners by only dealing a whole bankstick, rather than making it properly mios compatiable Hey wow, thanks AC. Now all I need is some time when my brain is switched on

hmmm, I had brain wave last night... Can someone help me out with this... when converting 7bit to 8bit, it should be 1024 hex bytes to a section, times 32 to get a full bankstick. From reading a sysex file in a hex viewer, there is 1182 bytes to a section. So minus the header and info (11 bytes), minus footer (2 bytes). Leaves 1170 bytes that make up the bankstick (in 7bit). Given that 8 bytes of syx are converted to 7 bytes hex. 1170 divided by 8 = 146.25 146.25 * 7 = 1023.75 what am I missing? ???

looks like the old max 256 bytes to an array in sram issue. Try using the 'const' keyword to store the array into flash memory rather than sram.

Nice work AC!! Have you had any success going back to sysex? I'm flat out at work for next 2 weeks. So I won't have time to work on it for a while. :(

I've had some success, but i've hit a brick wall I'm dealing with uploading/dowloading a whole 32k bankstick I've successfuly got the sysex message translated correctly to bankstick format. The initial method was skip the first 12 bytes, run the rest of the file through the algorithim. Then every 0x400 bytes I skip 12 bytes (i think it's was 12 anyway, might have been 8 or 10 :-[ my code is another computer). This worked great 100% accurate using a sysex file made with hex2syx.pl Getting it back to a sysex message has proved much more difficult. So to convert to sysex. it's 11 bytes of header and info. followed by 0x400 bytes of bankstick data (in bankstick format). Which should be 0x492 bytes of sysex data. followed by the checksum and 0xF7 Total 0x4A0 bytes. loop that 32 times but for some reason I fall 3 bytes short. Adding 3 blank bytes before the checksum almost worked. But my bankstick data ends up being offset +2 every 0x400 bytes. (using my sysex to bankstick code) So I go back to my sysex to bankstick conversion. To do it properly (hoping to find an answer). I take the header and info (11 bytes worth), convert the next 0x492 bytes (7-bit to 8-bit), get the checksum (to eventully compare it) and F7. Then loop the sequence 32 times to get the full bankstick. Taking the same sysex file I used earlier, The first loop works great, my first 0x400 bankstick bytes are correct, but as of the second loop the data is incorrect. I can relate to AC here... there has to be something obvious I'm missing. edit: added a bit more clarity

Hi organman Welcome to midibox community! it's easy to remember in hex 0x3c = C3 ;D which is midi note 60

haha, yeah I discovered that the hard way. :( my second attempt is to grab 1 bit at a time and place it directly in the correct byte, it's pretty ugly but works so far.