Jump to content

latigid on

Frequent Writer
  • Posts

    2,516
  • Joined

  • Last visited

  • Days Won

    147

Posts posted by latigid on

  1. Hi Laurent,

    For euroceiver versions 1.5 or older there is a J0 jumper above J19, near the USB.

    There is a jumper on the line transmit board but it basically supplies power over the DB cable, which you don't really want as there is a big voltage drop.

    If grounding is not the issue then I would typically expect power supply (e.g. noisy USB), bad cabling or similar.

    At least you can test directly without the line drivers now the SEQ is open.

    Best,
    Andy

  2. It is important with older euroceiver boards that the J0 jumper is installed. This grounds the two systems. Is yours grounded? 

    To rule out the line drivers, you can bypass them but you'd have to open the SEQ case of course...

    Something else to try would be a different power supply e.g. the USB+5V instead of the regulator etc.

    Best,
    Andy

  3. It should press fit but Peter has a technique to use Scotch tape to hold it in place before lowering the case.

    For me, I slightly roughen the back powder coating (say 120-grit sandpaper) and apply drops of superglue to the corners, away from the edge. Then I carefully place the protector in. If you mess this up though, you'll get a nasty smear on the plastic, so tape is probably safer and sufficient.

  4. We have seen a case where trying to flash with the PA0 port left floating could lead to a corrupted bootloader. Hence the resistors R101 and R102 seem to be very important (that were not installed on your initial build).

    The footswitch/gate LEDs are driven by the buffer chip IC6, so it is expected that they don't illuminate with no inputs.

    Anyway, great that it seems to work well!

  5. If you think an available commercial device can fulfil your needs, then get one! DIY is a different thing. It is potentially more expensive and you have to put in the tools and effort to finish things, but the journey can be very rewarding and sometimes you can obtain tools that are not found elsewhere, often for the very reason that they would be impractical or uneconomical to produce in scale.

    • Like 1
  6. Sorry, the extent to which I could help is already in the posts above. If you have more specific questions there might be others who are more into code modification. But at the moment it is hard to know what step you are on. It sounds to me like you are stuck right at the beginning, and I think it is rather up to you to learn how to modify the code to get what you want out of it.

  7. Hi Frederik,

    2 hours ago, Meadow said:

    - I can connect two AIN64 modules to one core. But is this all the core can handle or is it possible to also connect other modules to the same core, like Din modules, or mf modules etc?

    Yes, most ports with specific functions can be used in parallel. 

    J8/9 is for SRIO i.e. input/output shift registers that chain in parallel (DIN/DOUT)
    J19 is for SPI with two chip selects (AINSER/AOUT)
    etc. 

    Check the STM32F4 Core details
     

    Quote

    - Is it possible to cascade button matrices? Or do I need a new Core for every new matrix?

    The SRIO chain extends in series parallel, no need for additional Cores generally.

    Regards,
    Andy

  8. https://github.com/midibox/mios32/blob/master/mios32/STM32F4xx/mios32_ain.c
    https://github.com/midibox/mios32/blob/master/modules/ainser/ainser.c

    https://github.com/midibox/mios32/tree/master/modules/aout

    Basic drivers/assignments:
    https://github.com/midibox/mios32/blob/master/mios32/STM32F4xx/mios32_spi.c
    https://github.com/midibox/mios32/blob/master/mios32/STM32F4xx/mios32_iic.c

     

    Maybe it would be easier for you to use the Arduino and output an analogue voltage to be read by the STM32F4 AIN? That way you can use your working system without much extra coding effort. MBIO supports AIN either on the MCU ports J5A/B or using the AINSER module (typically less noise on the signal).

  9. 13 hours ago, zaordsword said:

    Hi latigid !

    Thanks for your answear :)

    >>have you written a driver for it to be used with MIOS?


    No, I don't know how to wrote the driver working with MIOS, but I have a script for making it working with arduino and python.
    Do you have examples of drivers ? I have see nothing about this topic anywhere on ucapp or on wiki or documentation and forum ...

    As far as I know, there are no I2C peripherals that were coded into MIOS32. The closest thing that I am familiar with is the I2C MIDI modules, that according to TK. were not trivial to code for, and at that on very low-performance 16F PIC chips.

    All the MBHP framework gives you is a hardware port on the MCU. You could consider to compare your arduino sketch with a device running off an STM32F4 chip or similar.

    Alternatively, you might find more code examples of SPI devices. Maybe you can try to code a driver for a similar sensor with an SPI interface?

     

    13 hours ago, zaordsword said:

    The bmp280 is a pressure / temperature and humidity sensor manufactured by boch. I join the datasheet, my python and a arduino script. (c ++)

    Edit: I had upload server -200 error when I try to up the datasheet . It's a project exemple availble here. The datasheet is on le page or  datasheet



     >>How would you expect the velocity values to be modified?
    The sensor give the barometric pressure . I plan to save the atmospheric pressure at initialization as P0 and find the realtime surpressure like P_surpess= ( Press_sensor(t) - P0) 

    Then I would like to map a certain variation of pressure matching with the velocity from 0 ... 127

    >>Have you looked into the MBIO code?

    What is MBIO code ? If you talk about the code on github there is a lot of file and I don't know where to find the file where to modify or to put a driver.
    I did not find documentation of a list of the reference classes / function. 

    The uCapps project is here:
    http://ucapps.de/midio128.html -- it is more targeted towards general users who would like to use the project without writing code for it.

    The git project is here:
    https://github.com/midibox/mios32/tree/master/apps/controllers/midio128_v3

    You would need to modify the code to suit your needs. Note that the code is written in C, not python.

    You can find the documented functions and some examples here:
    http://www.midibox.org/mios32/manual
    http://ucapps.de/mios32_c.html
     

    Best of luck to you if you decide to follow this journey. Others will probably not write the software for you, but if you post your modifications and explain where you are having difficulty, some might be able to help.

  10. Hi Matt, wonder if it is a short circuit to 0V (ground) somewhere. 

    Test each board in turn for shorts on the +5V line. Easiest is across any 100nF cap. Did you solder in the Matias switches yet? Sounds like it is on the Base or Plate PCB?

    Please upload sharp photos of the PCBs.

    Some status LED illumination is expected if the audio jacks and PCB stack are disconnected.

    Best,
    Andy

×
×
  • Create New...