Jump to content

Skunk

Members
  • Posts

    121
  • Joined

  • Last visited

Everything posted by Skunk

  1. Hi Florian, this sounds very good for me and meets exactly my original imagination! It fully fits to my plan and you mentioned one thing that is important: you used the same board STM32F4 for both -- the NG as well as the KB software. Out of the KB threads I assumed for a long time that it can only be realized with the LPC17 board and somehow there were some inconistencies in Thorsten's documentation that confused me. I also had a look on your github page that finally convinced me that I'm on the right track! Now I can sleep much better again and proceed with the mechanical work... Thanks & and best regards to Toulouse (I was there last time 20 years ago for business -- you have nice restaurants over there, for instance the Caves de la Marechale ), Andreas
  2. Hi Famtom, thanks for the feedback! I was not aware of it. I have the STM32F4 Board already in place, so I guess the only chance to change to more than 16 velocity values is to change it somewhere in the NG software. Or is there any physical limitation for the 16 values instead of the 128 that can't be changed in the software? I didn't dig deep into the software yet... Right now I'm taking care about the mechanics, and as soon as this is done I'll take care about the software and electronics. My original goal was just to use what I have in place, and this is the TP/40WOOD and the STM32F407 board. Both I already got years ago, but didn't have the time to build a real master keyboard out of it. And now I have the time to build -- since my retirement approaches... Or do I really need the LPC17 core for the KB instead of the STM32F4? Thanks, Andreas
  3. Hi Florian,, I have now nearly the same project in front of me: Generating -- out of a naked TP40WOOD from Fatar that I got some years ago -- a MIDI Keyboard like the Doepfer LMK4+. Doepfer charges 1500€ for this, and the solution with MIDIbox is much, much cheaper, thanks to Thorsten! I'll use the STM32F4 on a MIDIbox NG baseboard plus DIO_Matrix plus MIDI_IO plus AINSER8 (for the wheels and Pots) plus a 2x40 LCD blue plus a MBHP_DIN for the 24 Keys. So the same functions as the LMK4+ and a very similar control panel. But much cheaper. Will see how it works... Next phase is the Mechanics for the whole thing, and then the Electronics and the SW. May be I'll contact you at a later stage if I have questions. Especially the SW development might be a pitfall... Cheers, Andreas
  4. Hi Thomasch, ist zwar auf den ersten Blick eine etwas abstruse Idee, ein USB3-SATA interface IC für einen MIDIswitch zu verwenden, aber die Idee ist nichtsdestotrotz gar nicht so abwegig, den SATA-Teil einfach tot liegen zu lassen und die 8 GPIOs mit dem CortexM3 Kern zu verwenden. Das KnowHow liegt letztendlich in dem externen SPI Memory für den M3, der Rest ist USB3 Standard-Interface Arbeit. Nicht dumm die Idee.... Mal abwarten was Ploytec daraus macht... VG, Andreas
  5. Hi Thorsten, what about the noise of the motors during movement, the accuracy and the speed? Same as before? Cheers, Andreas
  6. Hi Thorsten, which computer? an AMD motherboard with 2.4GHz Athlon (don't know the supplier) which operating system? WinXP SP2 which driver? Ploytek special, customer specific which HW variant? customer specific -- a special board connected via the GM5 to the motherboard and a second USB-to-Audio USB I/F with 480Mbit, also connected to the motherboard. If the 480MBit line fails, the 12MBit USB-to-MIDI line also fails sometimes In the meantime we found one possible problem for the failure: groundbouncing. During the initialization of the USB controller on the motherboard, looking for devices, a groundbounce shuts the device recognition down (it looks like that, but this is not yet proven). There seems to be no means in the GM -- only reset. Cheers, Andreas
  7. Hi, question to all: did anybody already test the part under full load on all MIDI channels at the same time? If yes, did it work properly? I have currently an issue with this GM5 in a customer specific equipment, and under some strange circumstances it hangs up from time to time -- communication on USB and also sometimes on the MIDI ports stops. Only Power-Down/Up solves it. Cheers, Skunk
  8. Hi Wilba, especially looking at the inside life of this great box: this is the most professional MIDIbox build I've seen! No spaghetti wiring (as seen in many other MIDIboxes), clean boards, cable minimization well adapted box outfit. Just professional. Congratulations! Cheers, Skunk
  9. This is by far the most professional MIDIbox design I've seen! Congratulations! This fit's into my understanding of professional work. Cheers, Skunk
  10. Right Roger, it doesn't make much sense to invent the weel twice! Look at the motorfaders from ALPS. They are just perfect and deliver an excellent quality for a reasonable price (-> cost-performance issue). Cheers, Skunk
  11. Hot! A totally new view of the story! I'll pick it up again. Cheers, Skunk
  12. Very professional work! Congratulations!!! Cheers, Skunk
  13. I'd try to turn the ICs and move the JPs. It might need two or three trials. Such a simple design should be possible without bridges... Cheers, Skunk
  14. Hi Roger, typical swiss approach! ;D Welcome back! Cheers, Skunk
  15. Any experience about (signal & frequency) stability over temperature range? A 555 is not a very stable device... passive components direct the frequency and behaviour over temp. Try at 0°C and 70°C and look for the results and signal behavior. Cheers, Skunk
  16. What do you mean? There is no IC socket for a display... Cheers, Skunk
  17. Are you sure it#s really obsolete respectively on Last Time Buy? I just double checked the Microchip web site, and it just says <<not recommended for new designs>> -- which is different to a Last Time Buy since the 452 is still available. Can you refer to the Microchip statement that you mentioned? LTB page or something similar? Cheers, Andreas
  18. Just Buffering. The gate delay can be ignored since it's in the nanosecond range Cheers, Skunk
  19. Hi Roger, you won't beleive it or not, but your connectors are packed now. Just waiting for the post office to open after christmas so that I can bring it on the way. Looking forward to see you soon... 8) Cheers & happy holidays, Skunk
  20. Hi Jack, interesting forum link. Just went through it. Regarding OLED dispaly size: I think it's just in the right range for channel strips (beyond 40mm width). And a pixel format of 96x64 RGB or single color is more than enough to replace scribble stips, encoder displays, plugin displays etc. etc. Watch out for a good example at Fairlight DREAM Constellation XT. They use Osram OLED displays already. This is exactly the application I'm thinking about for OLEDs. Not as a replacement for the bigger standard character/graphics LCDs used in the MIDIbox applications. In my own planning for a modular console design I mix large 12" TFTs per 8 channel strips with a few small Osram OLED displays per 1 channel strip (i.e. 7pcs per channel strip for 1 fader and six VPOTs. Every 8channel module controlled by a PowerPC running Embedded Linux. So I need to write my own drivers unfortunately... :P Long way to go, I suggest to expand the 24hours a day to 48 hours -- or to wait for my retirement... 8) Cheers, Skunk
  21. Hi Jack, good idea. Got a similar one already some time ago, but with the Osram OLED displays. Everything is a question of the drivers, but the Kranz solution is a starter to add further display types. I'll check to get an OLED display sample (I know Roger, I'd see you loughing already ;D, but did you ever see the quality of an OLED display compared to standard LCDs? :P). Cheers, Skunk
  22. But don't eat too much cake. The MIDIbox community needs a healthy TK. ;D Congratulations!!! Cheers, Skunk
  23. Very professional! And when did you sleep in the 1,5 years??? ;D Can you supply something like a block schematics of the whole system -- just to get a better feeling which unit is doing what. Cheers, Skunk
  24. Also Jungs, worauf wartet Ihr??? Wann ist das 20x20 "merging-full-matrix-MIDI-Interface mit null Latenzzeit und für 99 Euro" fertig? Ein einziges großes FPGA tut den Job... ;D ;D ;D Cheers, Skunk
  25. I totally agree to Thorsten. Don't underestimate the time you need to get into all this new ARM stuff. I have two Evalboards for a Freescale MPC5200 and a Fujitsu Coral-P grafics controller as well as a nice 12" TFT, and to be honest: I even didn't find the time yet to implement everything in an Embedded Linux GUI for a MIDIbox looking console -- due to other projects. I'll finally start this chrismas, but with a one year delay!!! Regarding ARM: in my job I'm confronted with a lot of different micro architectures. After some comparison of ARMs with other architectures I got back to the following four: PICs and AVRs for the fast and efficient things like MIDIbox etc, and the Freescale PowerPCs and ColdFires for the higher level functions, running with Linux. ARM7 is cheap and well known in the electronics market, I agree, but not that powerful as many people believe. ARM9 or even future ARM11 architecture micros might be an interesting alternative as long as you are able to program them in an optimized and efficient way. Beside that, don't forget how long a dedicated ARM microcontroller is in the market before it dies again. A few years, then it's obsolete. But PowerPCs, ColdFires, PICs and AVRs have a long lifetime (due to their typical industrial usage) -- usually more then ten years. No real problems with obsolescence. Just some thoughts... Cheers, Skunk
×
×
  • Create New...