Alasdair Moon

  • Content count

  • Joined

  • Last visited

Everything posted by Alasdair Moon

  1. LoopA in Action

  2. AOUT + Line Driver HELP needed, no CV

    Hi all,   finally I finished the breakout for my +-15V Synth. Midibox  recognises the AOUT and DOUTx4, Gates /Clocks and triggers work perfect, but I get no CV signals. I already measured every connection on the AOUT -- all seems to be fine. LED is on when connected to the Receiver. The PINs 4 and 11 of the TL074 have the correct 15v. The PINs of the DAC are all soldered good and checked, that they have connection to the corrsponding PINs of TL074. I struggle a bit with the connection between the Line Driver Receiver and the AOUT. The PINs on the Receivers JAOUT are named SC / SO / CS / Vd / Vs the INs on J1 of the AOUT are named SCLK / DIN / FS / Vc / Vs Are the first 3 connected directly or do I need to twist cable there?    
  3. Panel Angle Question

    Hi Justin,   I build mine with a simple rectangular box, but .. I shortly started to notice, that some angeled sidepanels suit me better .. much easier to handle that way .. but it all depends on where you install your MBseq ..
  4. is the STM32F4 EOL?

    Perfect ... new Controllerboard for the Sequencer .. and I take the old one for other projects ;)  
  5. is the STM32F4 EOL?

    @Hawkeye .. now this is good news :D
  6. is the STM32F4 EOL?

    @FantomXR ... 26 Weeks delivery .. autsch ...
  7. is the STM32F4 EOL?

    STM32F407G Mouser => availability .. ZERO, since some months Didigey => availability .. ZERO .. since some months Conrad .. ZERO WattenRott .. ZERO I hope we still find some or the next generation of the boards soon .. 
  8. The Hexboard

    Now this iiiiis cool,  @TAG  do you have more buildocs or some of the code you used for this project?
  9. AOUT + Line Driver HELP needed, no CV

    @bemerritt .... nice idea to check the board too ... I will do it this weekend (the big fun of debugging )   ... new AOUT_NG Board ordered yesterday, now I still need that nice little TLV .. again .... :D Core schematics of the STM32F4 Core say, that J19 is connected to IC1 ( 74HCT541  legs 15-18) and PB4 of the STM32F4Discovery (which took quit a while to find)
  10. AOUT + Line Driver HELP needed, no CV

    Do you use a Linedriver or connect directly to the Core? If you use a Linedriver, try connecting the J19 of the receiver to J19 of the board OR connect directly from the board J19 to J1 of the AOUT_NG (with the special cable)
  11. AOUT + Line Driver HELP needed, no CV

    O.k., a little update on the AOUT_CV. I desoldered the TLV today, reconnected the board and did some measuring on the SMDpads to see if there are other errors. All OUT's except OUTB and OUTG have -13.78 Volts ???? OUTB and OUTG have 0.13Volts ... J1 Pin5 (SC) has connections to pads 1-2 and 3 of the SMD-field. I know shit can happen and I know my soldering is not always perfect, but if there was no production-fault on my AOUT_NG board (which can alway happen) there is one now ..... So .. restarting at zero ... buying a new AOUT_NG board and all new components .... savest way
  12. You could make a midi-dump from your electribe and then import it to your Midibox.
  13. Programming MBHP_IIC_MIDI

    You will need a pic-burner .... there are some, not that expensive via amazon. I got a wingoneer and it worked just fine.
  14. AOUT + Line Driver HELP needed, no CV

    I connected the AOUT via the Linedriver to see what happens Results from the testaoutpin via mios terminal J1 of AOUT_NG between Pin 1 and Pin 2 I have 4.8 Volt testaoutpin cs 0 => pin 3 => 0,13 V testaoutpin cs 1 => pin 3 => 3,67 V testaoutpin si 0 => pin 4 => 0,13 V testaoutpin si 1 => pin 4 => 3,66 V testaoutpin sc 0 => pin 5 => 0,13 V testaoutpin sc 1 => pin 5 => 3,64 V so all seems like it should be BUT ... PIN 13 (OUTB) of the TLV5630 gives 2,16V permanently .... so ... solderissue there ... somewhere ... or TLV damaged like latigid_on said ..... so, luckily I have to place another mouser order next days ... wheeeee ....
  15. AOUT + Line Driver HELP needed, no CV

    JAOUT is connected to J1 I removed the ICs, but with or without ... same results ...
  16. AOUT + Line Driver HELP needed, no CV

    Receiver PCB JAOUT to AOUT_NG J direct 1:1 soldered .... Pin1 and Pin measure correct 5V on J1   I also tested without Printercable and connected J19 of the STM32F4 board directly to  J19 of the receiverboard  .... JAOUT of receiver_board and J1_AOUT_NG stay connected ( I didn't want to desolder everything to test it with the special-cable you describe in the AOUT-Wiki)  
  17. AOUT + Line Driver HELP needed, no CV

    I pre-checked every path to ensure those are correct. the TLV does not get hot and has the right voltage at the Vcc and Vdd pins ... same is for the TL074
  18. AOUT + Line Driver HELP needed, no CV

    Yes I did, AOUT is selected and was written to the GC.HW4 config file I will test the "testaoutpin" tomorrow and report then. (my Linux Mint does not support the right juice-stuff, so MIOS terminal will crash )
  19. AOUT + Line Driver HELP needed, no CV

    AOUT_NG directly connected to J19 ... no matter what I do, or which channel I select, or try to calibrate ,....... CV channel 1:      0.08 Volt CV channel 2:      6.78 Volt CV channel 3:       2.75 Volt all other channels 0.02 Volt If I measure the voltage directly at the TLV pins ... it also does not change, no matter what I do .... something really is wrong here .... damn .... maybe buy a new PCB and Chip and start over again
  20. CV setup help

    I seem to have the same problem with my AOUT_NG and SeqV4 ... I will do some more testing and direct connection to J19 as proposed ...
  21. AOUT + Line Driver HELP needed, no CV

    I now have some voltage, but not the 5V on C3 that I expected. I triple-checked the whole connections and solderpoints of the AOUT_NG, all points of the DAC are at the right points, no bridges or something similar. The receivers JAOUT is connected matching to the J1 of the AOUT_NG. Jumper on transmitter is mounted like mentioned in the docs.
  22. AOUT + Line Driver HELP needed, no CV

    I think so ... I edited the MBSEQ_HW.V4 for the WILBA Panel for the STM32F4 where the SRs are set to 3, 4, 5 and 6, cause the wilba only uses 2 SRs for OUT, that part is working, Gates, Clocks and Triggers work with ~4.5 Volts. The thing that is not working is the CV row from the AOUT_NG. The MBSEQ_GC.V4 is on the SD card and I configured the AOUT via the Midibox. Type is set to 3 (AOUT_IF_TLV5630), which should be the right type for the AOUT_NG.
  23. Yes, it is the Juce in Linux Mint ..... did the update via a windows 7 and all worked smooth.
  24. Hi all, I tried to update my midibox today from 4.090 to 4.092 on STM32F4-Discovery I connected the micro usb and started the mios32 under my Linux Mint. (I have a 5v power-supply connected) USB Ports of my midibox seq are scanned and loaded ... QUERY gives the correct values Filebrowser can access SD-card If I send infos from my midibox to mios32 all works perfect When I tried to upload the new hex-file I get the ERROR .... FILE DOES NOT EXIST and that's it ... the "start" Button of MIOS32 stays grey What could it be? Only weird thing I see in the Infopage is the CPU-load that says 234%   Greetings, Sascha  
  25. O.k., I maybe found the solution. Mios Studio 2 as well as CTRLR use Juce. Both Apps have problems opening files on my Linux Mint, and this might be cause by a Non-KDE Desktop Env. Will test this later this evening.