Zam

Members
  • Content count

    610
  • Joined

  • Last visited

Everything posted by Zam

  1. Threshold calibration for Ainser64 module

    Hello Can't say for MIDIO128... but for MB_NG it's in the .ngc parameter file. Best Zam
  2. MidiBox DAW Controller

    Hello Thomas Look promising ! Best Zam
  3. Upcoming MBHP_MF_NG module

    It was both, EMI not acceptable regarding technical performance I requested then, with that particularity that I have low level audio signal just across the digital circuit, which is not a question/issue for 99% of pple using MF_NG. As acoustic noise that can't match the quality standard at user side I was searching for, in a quiet as possible "high-end" control room I can't work with a bunch of printer like sound, unfortunately a fader automation is not a tool that you can put in the machine room In a way both noises are linked. Best Zam
  4. Upcoming MBHP_MF_NG module

    Hey Thomas As you notice I take another route long time ago, I'm not able to help you much about PWM handling I think I publish all my tries around PWM by that time, and there is probably other options to test today, including increasing frequency of the PWM (over audio range). IIRC mios8 on the pic can't do this ? Do you know how is handled the motor in the D-com ? Best Zam
  5. Upcoming MBHP_MF_NG module

    Hello     I'm not sure you do wrong, this is probably intrinsically related to PWM driver Best Zam
  6. motorfaders

    Nice catch ! Whit this I think we can definitely say this is a digital encoder implementation around a P&G "blank" fader The fader is just use as mechanical device to translate rotary to linear actuation We have here a 256 steps/turn version. Can't say how many steps it translate to the linear movement, this is defined by pulleys/axis diameter ratio, but we can expect more than one motor turn for a fader full travel. Best Zam  
  7. motorfaders

    Hello 6 wire to the motor...should be a step/rotary counter... The OP just say there is no resistive element in the fader, and you can see there is no wire going to the fader ! You won't find any taper resistance here nor touch sens.   This is probably a rotary encoder/counter technology embeded in the motor Stagetec do broadcast console, I suppose there is no automation on it but recall and fader flip function where the encoder is enough to send fader at visual position (this is a remote) As there is probably a calibration routine at startup with such advanced digital desk, the drift or miss count of motor turn for precise fader position is not a issue.   As is it seem complicated to use this with midibox HW What you can try maybe is wiring pin 3-4 and 5-6 (assuming 1-2 is motor...) to a DIN in encoder mode and at least know how many count you have for a full travel, that data will give you fader accuracy and position. Then find a solution to use this data in place of analog input (from a resistive passive element) to handle data that will tell the motor what to do.   Best Zam  
  8. MB 6582 PCBs

    Off topic... J'avais oublié... ca pique fort quand même Zam
  9. Threshold calibration for Ainser64 module

    Hello AINSER modules have pinrange option which is basically used to add dead band at start and end of a pot. It can be considered as a threshold if you set value high. MAP definitions can also be used to achieve threshold functions. There is sensor mode too, but not used to it, so you have to look by yourself Best    
  10. IncBank DecBank Trouble

    Hello Micha To understand the whole mechanism we need to know what do section 1 as you call it at the end of the section 2... Also your sender 4043 have key definition which is not relevant due to type=meta What about the buttons that select banks ? Do they forward to receiver 4042/4043 ? Best Zam  
  11. SysEx STREAM_MAX_SIZE / timeout problem

    Hello Baudrate setting is a mios32_uart.h But you obviously need to change this at both side of the wire, so won't work if you have a hardware synth where you can't change this setting. (31250 is a midi compliance) Only useful if you hook two midibox devices and you want to gain some data speed/density   Have you try to change optocoupler ? I have vague memory to read around some issue with. But don't remember the context.   I also notice timeout error in my early mios experimentations when the core is really busy. like lot of data IO stream, which can be exponential if you have the debug on at the same time Have you tryed sending/receiving the sysex message with minimal activity around (no other midi message, no event value change, no NGR script runing)   Just another guess, but what is the data a your pos 52 ? maybe it's a conflict with some MIOS terminal command ?   Best Zam  
  12. SysEx STREAM_MAX_SIZE / timeout problem

    Hello Micha Not a direct answer, but some observation at my side. I'm used to this time out message when in the past I play around with midi baudrate speed (for multicore direct connection in a project) what is sure is you need same RX/TX speed at both side of the midi wire, I suppose that's not your issue, but I also notice that wire length can have impact, in other hand the TX/RX quality and potential data lose. In your case I suppose you have optocoupler, investigating that side of hardware and data integrity might be an option. Best Zam
  13. Hello You can load files with LOAD command in .NGR And you can call the section with load command via an event in .NGC (meta=runsection) which can be a button. Now if you use let say an encoder with value change or a radiogroup button you can define a value to a dummy LED (NGC), value that can be the condition for each config you want to load. if value =1 load X if value =2 load Y You'll have to do this at all .NGC/.NGR you'll hypothetically load, to be able to "navigate" from and to each config files Best Zam  
  14. Hello For some dedicated purpose I'll like to activate a DOUT pin depending of some midi activity. In fact lit a led if there is no incoming pitchbend data since 1 second, an turn it off as soon as new incoming data happen I think I can do this with NGR script, but as the script will run all time it's not an viable option (I have other run section in my NGC), I'll give it a try and see if I can accept script interruption. I don't see right now how it's possible with NGC only as I need a delay/timer, if someone have an idea ? Best Zam  
  15. Hello I'm not sure to understand what logic/function you want to achieve by reading your NGC code. Can you describe the user level logic you need ? (I see CC definitions type=cc, but without number definition: cc= ) Best Zam
  16. Upcoming MBHP_MF_NG module

    Use the material you want for the visual finish you want ! row alu is ugly for front panel and easy to scratch... I'm just saying this in the manner that you should anticipate your enclosure design and be sure all metal part have good electrical connection between them, a recessed screw or countersunk head screw that fix front panel to frame should be enough (as milling will remove the surface anodization ) "basically" your pcb 0V should be hooked at one (and only one) solid screw at the frame (common ground), preferably close to the main entry, where you also connect the safety earth ground from the (close) main connector. In your particular usecase I think fader screw mount (countersunk) will do the job to connect fader metal can to common ground. Your fader 0V audio should not share the fader box common ground, it's already connected at console rack module via trace, pcb and local chassis common ground. Try to imagine the audio part of the fader as an isolated extension from outside the fader box. Best Zam
  17. Upcoming MBHP_MF_NG module

    Hello Zeke Good you find solutions to your problem It seem (I can be wrong) that you misunderstood  the concept of ground, the thickness of a case have noting to do with it, I suspect in your fist attempt you just connect together your Vref (0V here), fader can and metal case, without path to safety/earth ground, meaning everything stay floating. As soon as you connect all this to rack frame you create a path via rail and other equipments, I suggest your fader rack get it's own path to main ground to not interfere with other equipment (otherwise parasitic current might flow trough them) technical note: powder coating as anodization (surface only) are non conductive ! for example you have to mask before coating or scratch surface after, if you want proper conduction between metal part in rack assembly. Best Zam  
  18. Upcoming MBHP_MF_NG module

    OK, to be more constructive... I just have close (zoom) look at your last picture with all the faders Be sure to not share fader 0V at your sub25... each fader should have it's own ref closest as possible to buffer ref Are the fader actually connected to console ? you should reduce at maximum the wire length I suspect the whole digital side (MF_NG) is currently floating ? I'll definitely put a path to chassis ground/earth. 100n across motor leg should improve a little current peak.   As a global rules, as it is for console integration, I'll suggest to build the thing as close as possible to final integration, to minimise bad surprise at the end as loosing time to fix issue that will not happen in the proper frame/mechanical integration. Best Zam
  19. Upcoming MBHP_MF_NG module

    yes.. for this you have to go one programming layer lower in the system ... as for the great map/table that @TK. add by the time for the PIC/MIOS8, which offer possibility to "match" DAW fader value to real fader attenuation Best Zam  
  20. Upcoming MBHP_MF_NG module

    Somewhere in the code, but I don't remember where, it was long time ago
  21. Upcoming MBHP_MF_NG module

    Hello Zeke So...lot to say...welcome to the real world of digital electronic... Have a search here, I talk a lot about this 4 or 5 years ago, that's why I give up the PWM driver and design an analogue PID motor driver. You'll have to try to chassis ground fader metal part to minimize EMI leaking and motor sparkle IIRC the SR scan at 1kHz for the touch detection also give me ugly noise at audio side, I partially solve this by lowering the refresh scan to 30 or 50Hz (which still fast enough for most situation) Fader construction might also have impact of digital lines leaking to audio trace/wire. As how 0v audio is hooked at fader buffer side (that's another whole topic and maybe not the good place here to talk about)   Your recorded noise look like PSU hum and harmonics ?   Noisy supply + noisy digital lines + fast H-bridge switching + Motor EMI emission. This is lot of tricky topic to solve if you want to put all this in analogue desk.   Best Zam
  22. Upcoming MBHP_MF_NG module

    Hello Zeke Again check ref (servo) voltage stability, what voltage do you send to the board ? IIRC vref is 5V standard regulator, you need 3 more V to ensure "proper" regulation and minimum ripple What happen if you disconnect motor (EMI suppression) ? With HUI protocol, there is a constant call to ensure device is connected, C2 might be this ? Don't remember how the upload to the PIC is done in MIOS studio. Best Zam  
  23. Upcoming MBHP_MF_NG module

    Hello Seem you have Vref and servo track instability/jitter. Check servo voltage. What is your fader ? how it is connected ? did you hook the motor ? if yes did the physical fader jump too ? Not sure 100% how it is handled at MF_NG code, but IIRC data transmission should run only when fader touched (for obvious reason). No touch connected might cause issue ? Best Zam  
  24. Upcoming MBHP_MF_NG module

    Hello and welcome here I don't remember well but I think it's connected to a pic output, so should show some activity.   Have a search, @TK. work on a wireless PIC replacement for this board , also @Antichambre have a super small STM32 board with PIC pinout compatibility IIRC should not be that complicated (for those who know how to) to make this MIOS8 app running on MIOS32 Best Zam
  25. Help needed with MF_NG

    Hello     Not expert at all for the question, but I find this: http://ww1.microchip.com/downloads/en/DeviceDoc/39647a.pdf I suspect it deserve a read Best Zam