Jump to content

jdutcher

Members
  • Posts

    146
  • Joined

  • Last visited

    Never

Posts posted by jdutcher

  1. I apoligize for the bad service i have delivered.

    Twin-X,

    i'm not sure why you are so easily discouraged about all of this.  if you read the above posts, you'll find that no one (with the possible exception of moebius) is at all unhappy with the service you've provided.  on the contrary, everyone is grateful for your help, and the server has been working perfectly for the most part.  please understand that your efforts are much appreciated, the server is GREAT, and everyone is HAPPY.

    now, enough bickering about this server stuff...jeez ::)  (not to say that your input wasn't appreciated though, smash... :))

  2. hi everybody,

    i'm hoping to control some analog synths that i have but i need a midi-cv unit first.  my question is: should i add the aout module to my finished seqv2 or should i build the standalone midi-cv module?  basically, i'm worried that i might not have much control over the output if it's hooked up to my seqv2.  i want to be able to play the synths using a midi keyboard.  can the seqv2 with aout only output sequenced notes or will i have the same flexibility as with the midi-cv unit?

    thanks!

    james

  3. I do expect a full report though......... ;D 

    Are these Hakko, or MPJA re-brand from another company?

    hey smash,

    well, some people (so i've read online, anyway) say that they are actually manufactured by hakko, while others say they just look like a hakko.  i'm assuming the latter is true, but you never know i guess.  anyway, i actually ended up ordering the analog version from circuit specialists (http://www.circuitspecialists.com/).  same unit though.  anyway, i will definitely post a full review once it's delivered (tuesday) and i've got enough time to take it for a spin (sometime next week, i'm sure).  i can answer any specific questions you may have also, arumblack.

    james

  4. moebius, you're completely right...sorry about that.  i finally got around to tailoring the code to fit my box and, sure enough, everything was detented2 except for the datawheel.  that's why only my datawheel was messed up.  switched the datawheel to detented2 and everything works just fine now.  therefore, smash, you should definitely make note of the "detented2" issue for the bourns encoders (although clearly you and moebius are five steps ahead of me  ::)) in addition to the pinning clarification that i posted before.

    thanks,

    james

  5. Last diagram is top down, shaft facing toward you/pins pointing away.

    ...

    I need to dig through some old emails, for more info about what to change on the encoder speed.....time for me to break out the iron and build some hardware.... ;D

    great, thanks smash!  yeah, that's what i had assumed when looking at the diagram, but moxi had me second guessing for a minute...

    also, as for the encoder speed issue, i'm not really sure what to think at this point...i mean, i guess it makes sense for me to finish up this weekend before posting about this, but the whole "detented2" has been floating around here and there.  in fact, in moebius' recent "encoder specifications" post (http://69.56.171.55/~midibox/forum/index.php?topic=3980.0), he states that "detented2" is the way to go.  as i've said in the past week or so, i'm only having an issue with the data wheel encoder on my SEQv2...all of the other bourns encoders on that box are functioning normally.  sorry to be potentially adding my confusion to all of this, but it seems strange that only the datawheel would be having this issue.  more importantly, i guess i should keep my mouth shut until i ACTUALLY get around to trying everything this weekend. ::)  anyway, thanks for the help smash!

    james

    P.S. moebius: i hope you end up reading this post...thanks for your "encoder specifications" thread....it's definitely helpful, but i think we might need to hammer out this "detented2" issue a little bit more before we list it as being the definitive answer.  i realize that it might have made more sense to post all of this in that thread, but i didn't want to clutter it with semi-tangential info. ;)

  6. so i decided to go with the knockoff hakko station that arumblack and i were talking about (*anticipating a grimace from smashtv*).  from what i've read online, it seems to work pretty well.  if people have any questions about it (if you're in the market for a new station or something...) let me know...

    james

  7. as for the complaining: i don't think anybody is really complaining...thorsten was looking for some feedback on how everything was holding up and that's what people (myself included) were providing.  there's no ill will here, just info.  i think everyone is happy about the new server, there were just a couple of kinks that people were bringing to thorsten's attention.

    hi twin-x,

    sorry, i guess i should clarify that i'm speaking for everyone except moebius in this statement.  as other people have recently stated, the new server is great!  everything is working super fast, thorsten doesn't have to pay any money, and the minor kinks are understandable and have been taken care of quickly.  thanks so much for your help twin-x!!!

    james

  8. hi smash,

    well, i think first we need to figure out this ambiguous diagram issue...in the last diagram, is the shaft facing towards us or away from us?  once that is clarified, i think simply adding a key to the diagram defining which pin goes where (i.e. "pin 'a' --> D1", etc...).  as for the mios encoder modes, i still haven't had a chance to try the fix that thorsten suggested.  i'll post my results sometime this weekend, hopefully.

    hi moxi,

    now that i take a closer look, you're right...it is difficult to see what position that last diagram is in.  my description refers to the 2nd to last diagram, with the pins facing towards you.  let me know if you need more info.

    james

  9. CLARIFICATION FOR ANYONE USING THE BOURNS ENCODERS FROM SMASHTV:

    (see http://avi.dezines.com/mbhp/images/encspecs17.gif for the diagram at smashTV's store)

    pin "A" goes to D1

    pin "C" goes to Vs

    pin "B" goes to D0

    this particular example is for J4 of the DINx4 module.  use the same format for other inputs.  for instance, the wiring for J3 of the DINx4 would be:

    pin "A" --> D5

    pin "C" --> Vs

    pin "B" --> D4

    this setup works in my SEQv2 box.  if any of this is unclear, let me know.  also, smash, if you read this maybe you can post this info somewhere on your site.

    EDIT:  P.S. I'm posting this info here because I had gotten the wrong impression from ludo (see above post) and, after finishing my box, the encoders were reversed.  I've sinced rewired everything to meet the specifications in this post and everything works fine now.

  10. thorsten: thanks for the tips.  i'll let you know how everything works out when i finish.

    moxi: the pinout for the bourns encoders i got from smashTV are as follows:

    (see http://avi.dezines.com/mbhp/images/encspecs17.gif for the diagram at smashTV's store)

    pin "A" goes to D1

    pin "C" goes to Vs

    pin "B" goes to D0

    this particular example is for J4 of the DINx4 module.  use the same format for other inputs.  for instance, the wiring for J3 of the DINx4 would be:

    pin "A" --> D5

    pin "C" --> Vs

    pin "B" --> D4

    this setup works in my SEQv2 box.  if any of this is unclear, let me know.  also, smash, if you read this maybe you can post this info somewhere on your site.

  11. A lot of people complain but i do not see any helpfull awnsers or idea's from them. I simply cannot guarrantee 100% online time of midibox.org. I depend on my host. Nobody is perfect. Perfect cost lots of money. For example you want a nice midibox you pay more. You simply want a functional one you pay less.  ;D

    hi twin-x

    thanks for the info and please do keep us informed.  as for the complaining: i don't think anybody is really complaining...thorsten was looking for some feedback on how everything was holding up and that's what people (myself included) were providing.  there's no ill will here, just info.  i think everyone is happy about the new server, there were just a couple of kinks that people were bringing to thorsten's attention.  obviously, we don't want thorsten to have to pay very much for hosting, so i think everyone is ultimately happy about the new host.

  12. ok,

    so i wired the regulator to a remote spot in my box that is well ventilated (and has a heatsink).  i also lowered the intensity of the backlights a little bit.  after running for about 15 minutes, the heatsink measures about 40 degrees C.  it's very warm, but i'm able to keep my finger on it for a while.  is this ok?  should i be worried about a short?  my guess is that everything is fine...i mean, i've got plenty of equipment that gets much MUCH hotter than that.

    also, any help with the encoder/datawheel issues mentioned above would be great.

    thanks,

    james

    EDIT: so the seq has been running for about 35 minutes now and the heatsink feels like it's at the same temp.  doesn't burn me but it's definitely hot.  seems like it's staying at a pretty level temp though.  i really think it's just because it's a pretty big load for the regulator.  as long as it stays steady and everything works perfectly though, there shouldn't be a problem, right?

  13. Hi everybody,

    so i finished my seq v2 tonight and it worked on the first try!!!! :D

    (thorsten, let me take a minute to thank you again for everything you've done.  the design of the seq is beautiful...not a single detail left unnoticed)

    there are a few (minor) kinks in my finished box, however.  first of all, the regulator is getting VERY hot, even with a heatsink.  in addition to the seq (exact setup as thorsten's), i'm running a small midi thru module and the negative voltage converter for the bg micro lcds.  even with the backlights turned down about halfway, the regulator is out of control.  the leds are pretty bright also, but i'm not ready to go and add resistors to the outputs at this point.  i'm not convinced that adding a second regulator to power the two extra modules will make much difference (they're not really consuming much current, i don't think.  any suggestions?  does thorsten's seq design generally heat up the regulator a good deal?

    second, i wired the bourns encoders from smashtv according to the info in this post:

    http://69.56.171.55/~midibox/forum/index.php?topic=3911.0

    perhaps i misunderstood, but now the encoders on my seq are reversed! :'(  is there any way to fix this in the mios code or do i need to rewire everything?

    finally, the data wheel is extremely sensitive.  in other words, moving one click left or right often moves the cursor 2 or 3 spaces in that direction.  it's virtually impossible to get to the item i want.  why is this happening?  all of the other encoders are working fine, it's just the datawheel that is having problems.  any ideas?

    thanks!

    james

    EDIT: I'm using a 9VDC 1A supply.

  14. i'll leave the mios question for someone else to answer, as i've never built a multi-sid box.  as for the voltage question:  those values are fine.  none of the voltages are going to be exact.  generally, if your meter reads within a few tenths of a volt or so you're ok.  certainly readings within .03 volts (as you mentioned) are totally fine.

  15. Is the C the common one to link to Vs on DIN board ?

    i hope so, because i wired all of mine that way!  (finishing up my seqv2)

    i'm a little unclear myself.  just to clarify, A goes to D0 and B goes to D1, right?

    sorry ludo, not an answer to your question...just an addition to it! ;)

×
×
  • Create New...