Jump to content

Zam

Members
  • Posts

    625
  • Joined

  • Last visited

  • Days Won

    26

Posts posted by Zam

  1. Hello Thorsten

    I have something like "MF_HD" in head since time but don't start because of no more real need for me (I have my motor driver)

    It's hybrid, between MF_NG and My 89MotioN, in all aspect probably (cost, quality and performance)

     

    Your two AD scan from fader servo seem to show improved noise at 200kHz.

     

    Best

    Zam

     

  2. 8 hours ago, TK. said:

    Depends on the desired resolution for the duty cycle. The timers are clocked at 80 MHz
    Means: with 20 kHz we could have 4000 different "speed levels" (but actually I'm currently only using 64 speed levels, which is sufficient)

    Ok ! don't know what is the agenda or if any major MFNG update is on the road (which I can help on by the way...)

    I suggest to factor at least 10 the clock in case of hybrid system (analog close to or in the fader...)

    let say 312.5kHz , which correspond to 256 speed level (you have room over 64...) also a value over 192kHz (HD audio)

    I mean If it's easy don't hesitate to change this...

    Best

    Zam

  3. On 14/12/2019 at 8:23 PM, TK. said:

    I'm now able to control motorfaders, and the accuracy is much better than ever before, because dedicated PWM outputs are used (which are normally intended to fade LEDs), clocked at non-audible 20kHz range

    Hello Thorsten

    That's interesting, what is the max possible clock speed ?

    Best

    Zam

  4. Hello

    Fader are just pot, 3 pin, you should find the pinout within 30 sec with a ohm meter...

    The pin that have variable resistance (across any two other) when moving the fader is the wiper

    The two pin that have fixed resistance when moving the fader are 0 and Vref

    The pin across the wiper which indicate low resistance when moving the fader down is the 0v

    The pin across the wiper which indicate low resistance when moving the fader up is the Vref

    Best

    Zam

  5. 1 hour ago, ssp said:

    let me know if this is correct

    event_button id=1 fwd_id=sender:1 range=0:127 button_mode=toggle

    event_sender hw_id=1 id=1000 fwd_id=led:1 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x10 0xf7" if_equal=0

    event_sender hw_id=1 id=1001 fwd_id=led:1 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x01 0xf7" if_equal=127

    ok so looking at this

    event_button id=1  #This is the event (button press) id=1 this is the first button on shift register 1=D0
     
    fwd_id=sender:1 #this forwards the event_button id  no!!! it forward the button value to the sender event with hw_id 1

    range=0:127 #midi value range

    button_mode=toggle #button type


    event_sender hw_id=1 #this is the event id that was forwarded to the sender NO this is the sender event with his ID

    id=1001  #this gives the event an id (could this be a number say 01 then the second 02?)

    Have a look at id= and hw_id= there is difference

    when using same hw_id you better use id out of the hardware range (1-256) to a avoid cross forwarding because an event without hw_id definition with take the id definition as hw_id too

    then it's up to your logic to choose a comprehensive patern

    fwd_id=led:1 this turns on the dout led 1 on shift register pin 1

    type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x01 0xf7"  # this is the transmitted sysex stream

    if_equal=127  # this is the on off state of the toggle button either off=0 or on=127

    This is the input condition for the sender to be active, meaning sending the sysex

    Best

    Zam

  6. Hello

    If you need more toggle steps use a map for value

    MAP 1 2 3 4

    in event button range=map1 the button value will toggle 1,2,3,4,1,2,3......

    and 4 sender with contitional if_equal=1.... if_equal=4

     

    i think i made a mistake you have to separate the fwd_id led (otherwise led will get the sysex and not the button value)


     

    event_button id=1 fwd_id=sender:1 range=0:127 button_mode=toggle
    
    event_sender hw_id=1 id=1000 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x10 0xf7" if_equal=0
    
    event_sender hw_id=1 id=1001 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x01 0xf7" if_equal=127
    
    event_sender hw_id=1 id=1002 fwd_id=led:1:0 if_equal=0
    
    event_sender hw_id=1 id=1003 fwd_id=led:1:1 if_equal=127

    Best

    Zam

  7. Hello

    You can do it this way:

    event_button id=1 fwd_id=sender:1 range=0:127 button_mode=toggle
    
    event_sender hw_id=1 id=1000 fwd_id=led:1 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x10 0xf7" if_equal=0
    
    event_sender hw_id=1 id=1001 fwd_id=led:1 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x01 0xf7" if_equal=127

    Best

    Zam

    • Like 1
  8. Hello

     

    Can't say... you have to try in your design

    Here I run aprox 35cm wire and trace from 10 to 25cm, with 3 connector in the path, from pot to AINSER input pin

    Vref have dedicated regulation.

    No jitter at 11bit

    Side note, I use AINSER8, no multiplexing, can't say what is the noise introduced by switching nor if there is some.

     

    IIRC you can chain AOUT up to 4 TLV (32 out) with a single RC line,

    so yes, 64in/16out is possible at J19

     

    Best

    Zam

     

  9. Hello

     You don't need a second one ! assuming you talk about midi resolution ?

    Set your AINSER module at 11bit in NG, and set event type= according to your requested resolution (7 or 14bit)

    NG should scale

    1 hour ago, macsaif said:

    but in that case I will have problem with jittering of all AINs

    With proper design and dedicated ref regulator you should go up to 11bit

    Best

    Zam

     

  10. 29 minutes ago, Thomasch said:

    My english is not the best, , so what means 15/100 error at tangent?

    sorry, I mean 15/100 millimeter, If you draw a (quarter) circle of 1mm diameter inside a 90° angle

    44 minutes ago, Thomasch said:

    Because of tolerances a little bit of gap between hole and LED might be necessary. Just enough, that it don't needs any force to slide the LEDs in.

    That's what I say, add 3/10 mm and you'll be fine for a soft mount, dust won't come in that much and aestheticly it's not noticeable

    Best

    Zam

  11. 42 minutes ago, piepermd said:

    So that is the actual app that you posted 8/30/17?

    yep... almost two years back :decayed: (thinking about one)

    but more precisely, this is not the app (.hex) but the change in code.

    You can copy/replace that at the correct place, IIRC the only change I made to "fake" raw dual CC as NRPN (note that standard NRPN won't work any more but HUI don't use it) I can also provide the compiled app which should be based on NG1.035 or 1.036 (don't remember what's up at that time), so not up to date regarding newer implementations.

    Best

    Zam

    ps: I sent you an email earlier today

     

     

×
×
  • Create New...