stryd_one

Sounds like one of the address lines to the multiplexer is not connected/shorted.

1) You say only the last 4 of 8 are working...So the first 4 are not working... Define "not working"? 2) Did you try a different encoder type?

Sooo........ 1 or 127 should work then?

Short answer: No Long answer: Search, this has been asked before :)

Bzzzzt I'm sorry that's incorrect but thanks for playing! ;) The correct answer was "What is the k64?" You should be able to mash together the ASM scan matrix code and the seq... Make sure it's light on the processor though, you don't wanna mess with that lovely tight timing :)

Those are speed holes, those make it go faster ;D (Simpsons joke) I think you can do what you like with those. My guess is that it's easier to just make a whole lot of 10pin DIL socketed cables than to make a different cable type for all the jumpers? Uhm... Anyone?

BUMP!! That's awesome.

Yaknow I've always wondered that myself... The signal should just be a clock, it can be square or pulse, it's supposedly a timing signal... But of course it's analog, and I think the timing signal is fed through a voltage comparison to create the raw square waveform, so I guess you could feed it all kinds of things and see what triggers it off. I imagine that the results will fall cleanly into one of two categories: Totally awesome, or totally useless :)

I like this method but autocad is way expensive :(

Mine are like, 15, and have been resting quietly in tubes, so I reckon they should last me well into the 50's. If I live that long I'll be about 70, and probably a bit old for this sh*t ;D I do wonder how this oxygen is supposed to come into contact with the silicone though...

1) Click DokuWIKI link 2) Go to encoders page (easily found in table of contents: Parts...Encoders) 3) Go to encoder types page 4) Do like pictures do 5) Enjoy your midibox :) I feel like a microwave cookbook heheh

Totally that's what I started doing, until I saw TK's trick above in some of his code and started doing it that way. It's much nicer for bitfields as he mentioned. It's not slow though, that's a #define, so it all gets converted to hex before compile time and long before run time :)

That's because you're mental! hehehehe I was telling Wilba during his planning phases that people would go crazy over this thing... As much as the commenters on his blog drive me away, I do like the way CR said it: Coincidentally I had spent that morning poring/drooling over a neighbour's DB9 and I agree. It's the attention to details that does it. 8 SIDs is hot enough. but it's all the little things that Wilba considered along the way that make it really something. It's the same thing that makes the firmware so awesome - lots of people could write a SID synth, but to do it like TK has, is truly incredible. Everything TK does is like a how-to. It's combined well with Wilba's skills with layouts and CAD work and the result is a monster!

Even if you search the forum for posts, the first hit for Doc (not doch or document*) is him signing off. It's the 9th hit. Of course we all make mistakes but the moral of this story is: Search first, then ask :) Or maybe it's: Ignore Doc at your peril ;D

Archived ;) Thanks mun!

What are you trying to do mate?

Sounds relative to me - 1=down 127=up. And what kind of MIDI message does it expect as an up/down?

Well I don't know about the other stuff but I do spend a lot of time here. I use these forums as a quick recreational break when I'm working at the PC; which is pretty much always, between my day job and the midibox coding :) Nah...you can't be blamed.. blame Wilba, while he's not here to defend himself. ;D

Well I have long since worked around this, but today I stumbled across the answer...doh! Thought I'd share it for future reference anyway: You use defines to pre-processor convert your binary to hex. #define BIN(x) \ ( ((0x##x##L & 0x00000001L) ? 0x01 : 0) \ | ((0x##x##L & 0x00000010L) ? 0x02 : 0) \ | ((0x##x##L & 0x00000100L) ? 0x04 : 0) \ | ((0x##x##L & 0x00001000L) ? 0x08 : 0) \ | ((0x##x##L & 0x00010000L) ? 0x10 : 0) \ | ((0x##x##L & 0x00100000L) ? 0x20 : 0) \ | ((0x##x##L & 0x01000000L) ? 0x40 : 0) \ | ((0x##x##L & 0x10000000L) ? 0x80 : 0)) T2CON = BIN(00110100); via: http://sourceforge.net/tracker/index.php?func=detail&aid=882215&group_id=599&atid=350599

Hah I remember getting beaten up in school for playing techno, now it gets you an A+! LOL Congrats on the marks and thanks for posting the vid for us :)

Google is your Friend ;)

(Finally got around to watching the vid) Uhm... That's sick. :D

Jeez don't congratulate me, I just watched and cheered from the sidelines! It's a heck of a show though ;)

The CAN bus is partially implemented in hardware and so the pins for CAN are restricted to the ones being used. </short version> ;) The display driver works best on the normal LCD pins, but using other pins creates a minimal performance loss (so small that you don't notice it) This is because the LCD connector uses a whole 8-pin port, which means you can write a whole byte to the screen in one go. If you use other pins, you have to drive those special pins individually...but we're talking about a few instructions, like 1/1000000ths of a second, it's no big deal. The CAN bus uses hardware built into the PIC that takes care of lots of stuff that would take up a great deal of uP cycles, in fact I think it would be too fast for software to drive it. That's page 275 of the data sheet, it's a 70 page chunk of geekyness that I couldn't explain much better :) TK has a significant amount of work being done in software to make it easier to use for us mortals, so not all of the datasheet applies...

Re: MIOS Upload fails.... The LF should behave the same way as the F.... Weird...