>
YAMAHA
STRINGS
SS-30
RACK-MOUNTED WITH MIDI
MIDI STRINGS

Wednesday, September 24, 2014

Tone Generation

Whilst looking for some clues on the key switching problem I came across this.

https://archive.org/details/synthmanual-yamaha-ic-guide-book

https://archive.org/download/synthmanual-yamaha-ic-guide-book/yamahaicguidebook.pdf


The Internet Archive has a mission to provide "universal access to all knowledge". Amen to that!

The document seems to have come from here : http://www.loscha.com/scans
which has a number of other interesting synth related documents, including another version of the IC guide book.




The manual contains details of the two chips used on each tone generator board. Ten years ago (blimey) I wrote about the polyphony. I mentioned in passing that the SS30 has two oscillators per note. This post expands on that and, although it still isn't the whole story of how the sounds are generated in the SS30, it is where it all starts.

The SS30 tones start with a pair of oscillator circuits built from discrete parts. These are free-running VCOs with control for the pitch and detune. They share a common master tune and vibrato input and one also has the detune control input . The output frequency of these VCOs is much higher than what you will end up hearing though.They both produce 500 KHz signals.

These two signals are then feed to a pair of YM25400 Digital Tone Generator chips as the master clock input.



Each cascades of these Digital Tone Generators output a divided down clock which is passed on to next generator board for further division. 500KHz - 250KHz - 125KHz - 62.5KHz

The YM25400 derives 13 tones (an octave + 1, C0 - C1) from the master input clock. Each YM25400 then feeds a further pair of LM3211 frequency divider chips.



In summary: the G (tone generator) boards convert a pair of master clock inputs into to a pair identical octaves from two YM25400s. These octaves are then divided down further by a two pairs of LM3211s. This creates another identical pair of octaves one octave lower than the first pair. You end up with two groups of 26 semi-tones (2 x 13).Only G1 uses the extra semi-tone to give octave  + 1, the other boards discard the extra C tone and just output an octave.

The two octaves are named using the eight-foot-pitch naming convention. The initial octave direct from the YM25400's at the 8' and the one below is the 16'.

By now you may be thinking we're going to end up with not with 49 tones for the 49 keys but more like two hundred tones! And we do, but not all at once. Firstly the outputs of the YM25400s and LM3211s are mixed in pairs. Each tone that come out of the G boards is a combination of two square waves - and quite a strange combination too, which I will cover in a later post. If I can actually figure out what is going on!

So, there are actually half that number, but still double the number of keys. The reason for that is the G boards generate Violin, Viola and Cello tones. The various outputs of the G boards are split, switched in and out and combined in various ways to provide the various options selectable from the front panel. At it's simplest you can play the bottom octave, the G1 board, as violin/viola or Cello. When playing as Violin/Viola you only use one half of the G1 boards output. And when you change the split and play Cello you use the other half of the G1 board. It becomes more complicated on the other boards. G2 is split twice, so you get Cello half way through an octave at F as well as at C, and G3 and G4 don't out put any Cello. It gets very confusing in the schematic but is quite simple in the end.






Friday, September 12, 2014

Five years - and then an oscilloscope

Five years is long time between posts. I'm not going to try and explain that gap. Life has it's own priorities and this project wasn't one of them, I guess. I mean, I have done other things with my time beyond work, family, home-life and friends. In fact I have done a bit of work on the project in that period, but I didn't post about it. I can't really explain why but I do know that I get interested in something, spend a lot of time on it and then lose momentum suddenly. Or more accurately, I get distracted by something more important or interested in something else.

However, this project was always intended to be long-term. It took me years to go from a pile of bits to getting a case and thinking seriously about how to progress it. So, a bit of a gap is no great concern to me, although every year I don't have the finished article is another year I could have been using it.

On the other hand I'll be forty next year and if I aim to finish this project by then it would give me a date to work towards. As I type I have around 11 months to go, so it's attainable. Finishing would also free me up to do something else. I can't think what that would be though. 

Anyway, enough of this introspection.

One thing that has held me back from continuing with the project is having a decent scope to work with. In my early twenties I spent around three years of my work-life with a scope or soldering iron in my hand. When I'm working on electronics it's a scope that I reach for to see what's happening. It's the right tool for the job. I say a decent scope because I do have a scope, a GBDSO - Elektor Gameboy Digital Sampling Oscilloscope. This project was fun to do and produces tolerably good results but it's also a far cry from the professional kit I'm used to and, whilst a bad workman might blame his tools, a bad workman usually has bad tools. The issue is that I need this to be a pleasurable experience and using the GBDSO can be frustrating. I also want to be able to see audio traces cleanly and even some fairly pricey and professional digital scopes do a poor job of that.
So I bought a second hand Philips PM 3050 60Mhz analogue scope instead.


As you can see it's dual-trace and there's a nifty LCD display to show you the current settings. The traces on screen in that photo are the square/pulse and sawtooth output of the CEM3340 voltage controlled oscillator chip on my Roland MC-202.

The 202 was modified by me with some CV inputs years ago and has always been a bit flaky. As part of a general sort out in my studio I resolved to do something about that. I also realised that an SH-101 that I have on loan from a friend isn't working any more. No, I didn't break it. Well, I don't think I did. It's hadn't been used for years so I'm not sure what happened to it. So, I'd like to repair that too. It was these repairs that set me thinking about a scope again and how annoying the GBDSO was to use.

I've fixed the 202 now. The main issues were actually to do with removing some of the battery circuitry and disconnecting the internal sequencer. The sequencer was zapped when I did the mods originally so I decided to live without it but made a mess of the way the battery state is monitored and disconnected when the mains power is applied. I also fixed the filter audio input which never worked because I hadn't realised that the 1/4" headphone jack socket re-purposed to be the input was shorting the input to ground!

The 101 is next on the repair list and then - back to the SS30-M.


Wednesday, April 01, 2009

How are you to switch negative voltages?

I've been wrestling with the problem of key switching again. Because the key driver circuits switch a negative voltage to ground it creates a bit of a problem.

When I first looked at the j-Omega MPT8 I thought it could switch negative voltages but after thinking again and e-mailing then it seems not.

What's all the fuss about though? I can use a solid-state relay, optocoupler or CMOS switch package right? You don't even have to think to hard to get it working. The issue here is that I have 49 keys and very limited space. I'd really just like a transistor and maybe one or two resistors per switch. CMOS switches only come in quad packages at most so I'd need 12 and all the trracking back and across each other to get everything wired. If I must have a PCB at least I'd like it to be simple.

Generally switching negative voltages to ground is not something you get a lot of talk about when looking up these things. Everything is geared to positive voltages and how to bias your transistor that way. It's not impossible just less usual and if you wan to use a simple +nv/0V logic level your options are limited.

The reason for this is not that you can't do it (just switch from n-channel to p-channel FET) but that transistors that switch negative voltages themselves need a negative voltage to switch. which takes you back to square one.

Well, If a CMOS switch can switch a negative oltage with just a +nV power rail how does it do it? I've been wondering.

Google books have a Modern CMOS Circuits Manual online and chapter four has the answers

Wednesday, March 18, 2009

External Power Supply Unit

I'm thinking life would be much easier if the power came from an external unit, rather than having the PSU inside the chassis. Space is really at a premium and that's before squeezing in the Midi converter and switch circuits.

There are six lines (rails) coming from the PSU so if I had an external uni I'd need a six-way connector.

These ones from Rapid look good... http://www.rapidonline.com/Cables-Connectors/Connectors-Multipole/Circular-Connectors/Circular-locking-multipole-connectors/66501

I powered up the PSU last night it looks good but I am worried about the extra cutrrrent draw when I add the new modules. It's all on a 0.5A fuse which seems quite low. Might have to do a bit of measuring...

Saturday, March 14, 2009

PCBs

Is it practical to get a custom made PCB built up?

These UK company's do a custom service:

pcbpanel.co.uk

pcbtrain.co.uk


They both accept Gerber and Excellon format files.

pcb train recommend using Easy PCB for layouts but that runs to hundreds of pounds.

Instead, I found KiCad which does the job and is GPL.

Thursday, March 12, 2009

Switch circuits

I will need 6x SPDT, 2x DPDT and 2x SPST switches.

The 4066 contains four SPSTs which can be connected as required to make SPDTs and DPSTs.

2 x SPSTs = 1 SPDT
4 x SPSTs = 1 DPDT

So, I will need (6 x 2) + (2 x4) + 2 = 22 SPSTs in total. So, I'll need 6 4066s in total giving me 24 SPSTs to use.

It would be simplest to make a single circuit board up with all 6 switches on but you also need to accomodate the logic invertors. The 40106 invertors have 8 not-gates per package and you need two per switch (irrespective of what type you're making) which makes 20 gates or three hex invertors.

In total thats 9 x 14 pin ICS so in a single strip there'd be at least 63 rows on the board or in other words it'll be about 9 x 20mm = 180 mm. Which is okay, as Maplin do an 81 strip board 213 mm long .

Switches cont...

After looking around at switches I can see that there's alot of choice but it get's quite limited when you start narrowing down to DPDT types. This is another reason for looking at the switch IC idea.

I want to choose switches that will look nice and the biggest choice is in SPST.

Like this one from Rapid Electronics which has built it LED. Not blue though :-).

















Switches

I'm going to need ten switches plus the power switch.


Orchestra:

Speed - SPDT
Cello - DPDT
Violin - DPDT

Cello:

Attack - SPST
Cello 1 - SPDT
Cello 2 - SPDT

Violin:

Attack - SPST
Viola - SPDT
Violin 1 - SPDT
Violin 2 - SPDT

So, that's 6x SPDT, 2x DPDT and 2x SPST.


When I breifly worked in pro-audio I noticed that they almost never had audio signal going through the actual mechnical switch. The switch was usually controlling a DG201 or DG211 audio swicth IC. This was high-end gear designed for the live use so I suppose there was a concern that meachical switches would degrade over time geting damaged or dirty. You don't really want audio going through anything that might colour the sound or produce noisey clunks on switching.

The original switches are all mechanical though, so why worry? Partly because I won't be using the same kind of switch and partly because there may be a way to improve on the original.

This guy calling himself The Tone God has a design called Wicked Switches that uses 4066 analogue switch ICs. He also explains how to add debounce and LED indicators.

Wednesday, March 11, 2009

Spec reset.

Over the years, I've been thinking I should really make this project easier to finish.

The two main issues have been the awkward meachnics of fitting the original switches and knobs and the challenge of conjouring up a 49 output, velocity sensitive MIDI decoder.

The meachnics iossue could be resolved at stroke by moving to a set of new off the shelf compoenents.

Similarly there are several polyphonic MIDI decoders available from one company or another.

Therefore, I will continue this project on a simplest is best principle in order to finish it sooner rather than never.



j-Omega Electronics make a reasonabley priced MIDI decoder that will meer my needs.

j-Omega Electronics MPT8

The MPT8 has 64 outputs in an open-collector 'pull-down' arrangement. I'll be pulling up, from -7V, but to ground which is okay.

Tuesday, March 10, 2009

Matrix synth comments.

I added some comments to Matrix Synth:

"some sources describe this synth as a duphonic/ multiphonic ,others describe it as a 4 voice polyphonic. I have a feeling it is a 4 voice polyphonic but the 4 voices are split between cello (two tones) and violin (2 tones) . It then uses divide down chips enabling all keys to be played at once)"

Nearly. It has two master oscillators which are both dived down to give you the full set of notes, twice.

You need two waveforms to get a stringy effect so the same note outputs of the dividers are mixed.

When you press a key you're switching in a mix of two divided down oscillators.

The detune affects both oscillators but not equally hence you can detune one against the other and get to the good old thick sound but more importantly set the PWM type character you need for strings.

The outputs of these mixed waveforms are sent to either the Violin, Viola, or Cello mixers. In some cases the outputs can be sent to either one or the other mixer as set by the split selector switch.

The cello, viola or violin character is set by filters after each mixer. Violin 1 & 2 just are different (1st order) filters fed from the mixer, so when you switch them in you're just mixing and matching different filtered outputs of the same thing. the same goes for Cello 1 & 2.

So far it's just a paraphonic organ but with two tones per key. However the SS30 rules over other string synths because it has an AR envelope generator per key. When you set a long attack each time you press a key it starts a new attack just for that key. same with Release.

There's no VCF per key but that's what we have Polymoogs and, err, GX1's for.

Monday, March 09, 2009

Also on MatrixSynth

Matrix synth entry

There's an eBay auction y'see

So these pictures and videos may be up for only short time.

"some sources describe this synth as a duphonic/ multiphonic ,others describe it as a 4 voice polyphonic. I have a feeling it is a 4 voice polyphonic but the 4 voices are split between cello (two tones) and violin (2 tones) . It then uses divide down chips enabling all keys to be played at once"

Well, I maintain this is a fully polyphonic keyboard keyboard. See here for more. Essentially each sound (Violins and Cellos) have their own voice board which are then switched to a key range.

"The outer pot adjusts the overall tuning and the inner pot detunes the voices against the pitch which can produce a wonderful thickening effect"

This is interesting as I hadn't thought about this and since I haven't played my in some years (sigh) I'd forgotten what it sounded like. I'll have to check this but if memory serves correctly each note is mix of two oscillators (that's how you get a stringy sound) so the detune is just off-setting the two.

Video demo.

A spiffing demo! From Synthopia via my good friend Barker


http://www.synthtopia.com/content/2009/03/08/yamaha-ss30-rare-string-synth/



Friday, May 16, 2008

Greetings MatrixSynth gawpers!

Sorry, I've been too busy to keep this up.

Don't give up hope though, I haven't.

Tuesday, September 12, 2006

Yeah, I'm lame. Okay, okay.

Here's some red hot videos from YouTube featuring the wonder of the SS30.

http://www.youtube.com/watch?v=eRIJW5bYWN4

http://www.youtube.com/watch?v=eRIJW5bYWN4

The first one is Simple Minds on the Old Grey Whistle Test which I remembered seeing the SS30 on a Best Of... program about 10-15 yeras ago and due to magic of YouTube (yes, it's magic) I was able to find. Umless there's another one and this is not the one I saw. The second one is Ultravox on TOTP.

Thursday, September 08, 2005

Front panel mock-up

As I mentioned I've been busy working on the front panel. The first fruits of this labour are now starting to show. Below is a screen grab from Schaeffer AG's Front Panel Designer program. You might need to zoom in to get a better look.




This has been laid out with all the original controls. I still need to add the power switch and indicator lamp as well as any other controls I might need such as MIDI channel settings. The biggest concern is getting everything to fit both in relation to each other on the panel and in relation to the internals of the case at the back of the panel. Rather than just send the design off to Schaeffer and hope I'd got it right I printed out a simplified version of the design and pasted onto a piece of card of the right dimensions. You can see the results below.




At this stage, just the switch banks are fitted. I have also laid out a design for the reverse of the panel. Schaeffer will fit either threaded bolts or bushes to the panel so I've positioned cavities on the reverse of the panel for these so that the switch and pot assemblies can be mounted without anything showing on the front. This design was also printed out and pasted to the back of the card. I then punched holes through so I could check that everything matched up. You can see the holes more clearly in the close-up below.




So were there any problems? Firstly I was a bit concerned about the holes for the switches. They seem big enough but cardboard is a bit more forgiving that 4mm aluminium so I may open these up by another millimetre on both dimensions just to be on the safe side. Secondly and more seriously I'd made an error of measurement for the height of the switch banks at the rear...







As you can see the top bank of switches protrude above the level of the case. The lid will hit the top of the PCB. I think the error was partly bad measuring but also a miscalculation of the usable area of the front panel. The panel protrudes above and below the level of the case and it's obviously wider so there's only a window on the panel which is usable. Because the switches bank up at such a steep angle I should have moved them down by around 10mm. There's barely 10mm between the bottom of the top switches and the top of the bottom switches. In order to allow a little wriggle room, I really need to move the bottom row down. But is there room? In fact, there are a few mm available if I cut a strip off the front of the base board. This means I can move the bottom row down by 5mm and the top row by 10mm leaving a good few mil' spare at the top. It's going to be tight, but it should work. I'll need to do a new mock-up to check it over but it that should be it.

Overall it's gone quite well. The basic dimensions are good and apart from needing to move everything down, it fits into the case.

Next time I promise a solution to the MIDI channel control issue and a finished front-panel design.

Monday, July 18, 2005

Re-comencement & front-panel design

Well, it been a long time since I've made an update and whilst there hasn't been much progress there has been some.

Back in March I was stating to try and choose the PIC and I had to make a decision about the method for selecting the MIDI channel. Clearly Omni mode is useless in a set-up with a few different MIDI instruments. Also, I didn't want to have a fixed channel as this too can cause complications. So I was trying to decide how best to make the channel selectable - would I have a rotary switch or a pushbutton and LED display arrangement. There was problems with both and I decided I needed to see what space was left on the front panel. I also wanted to get the mock-up front panel in place so that I could fix the PCBs in place.

I had decided to get an aluminium panel cut and engraved by Schaeffer (http://www.schaeffer-ag.de ) and so I set about laying out the panel using their excellent free program. I soon ran into problems though.

In order to produce a pleasing and profesional looking final panel I don't want to put screws through the front panel. Nor do I want to fix pots to the front panel. The correct way to do this is to have a sub-panel behind the front-panel with all the controls fixed to that and then the frontpanel is kept clear for all the text and markers. Schaeffer can fix bushes (clinch nuts) to the rear of the panel so I can fit the sub-panel(s) to the back of front panel. Great! Let's designing.

If you look at the pictures below you can see that the pot's are already fitted to sub-panels. This is how the SS30 was built and is another reason to go with the sub-panel idea. When I sat down to try and lay-out the front panel I had to ensure that the holes for the pots were kept in line with these sub-panels. Also the position of the bushes has to be lined up with the fixing holes. This was starting to get tricky as the positions had to be relative to each other. On top of this the space on the front panel is tight if I want to use the orignal chunky tablet switches so the placement of the sub panels and switches needed some fine tuning. I needed templates for the sub-panels that I could move around and line up. This a bit of stretch for Schaeffer's Front Panel Designer (FPD) program so I decided design templates for the subpanels in AutoCAD and then I could slide everything around till it fitted. Luckily my partner is a dab hand at AutoCAD and she had me up and running in no time.

It took some time but eventually I had all the SS30 sub-panels and switches placed. I could then take the co-ordinates of all the holes from AutoCAD and transfer them to FPD. Finally I put all the text and marker engravings on the design too, using teh original SS30 panel as a guide.

So this is where I've got to. I'd like to post up an image of the panel but I need to do a screen grab as you can't print to file or anything like that in FPD. Eventually I'll put up the screen grab and a link to the actual FPD file.

That all took me a couple of months but I've done nothing for the last two months owing to other things taking priority.

Next : I need to get a print out of the design from FPD then paste that onto a piece of MDF. I can then drill and cut all the holes to a) check the measurmenets and b) have a mock-up that I can use until I take the plunge and get the real panel made.

But what about the MIDI channel control? Is what room is there? Well, I'm 90% sure that I'm going to for a push-button and LED arrangement but I need to check whether the PIC has Non-volatile that can remeber the setting. If not, then it'll have to be some sort of mechanical switch.

Tuesday, March 22, 2005

The interface nitty-gritty

Okay, I'm a bit bored of all this mechanics talk. I'm still working on the case, but I thought I'd talk about the interface for a change.

To recap, the aim of the inteface is to provide a MIDI in port that will take note on/off and velocity data messages on a specified channel and not only individually switch the keys of the SS30 on and off but also individually set their amplitude from the velocity data.

I have found from experimenting that if instead of simply shorting the key inputs to ground (as with the original keyboard) place a 10K potentiometer between the input and ground you set the loudness of the note played by that key. I'd suspected this was the case previously as the volume of the keys across the keyboard wasn't uniform and I'd put this down to the dirty contacts creating an impedance where there should have been a zero ohm contact.

So, if I can set a resistance across the key inputs from a combination of the note on/off and velocity data then I'll have a velocity sensitive MIDI interface for the SS30!

There are severals way to do this but I think they boil down to these two:

1) Use a DAC to set the gate voltage to a JFET acting an amplifier with gain between 0 and 1
2) Use a dedicated digital potenetiometer.

So which is better? The dedicted digital potenetiometers can be found in packages containing 6 pot's each. They would ceratinly make wiring easy and would keep the number of components low. I will err on the side of simplicity and persue these for now. If they become unworkable I may have to switch to the DAC-FETs solution.

So how am I to get the right MIDI data to these digital pots? I need a microcontoller to decode the MIDI data and then drive the pots and the simplest and most popular solutiuon with other people doing this kind of task is the range of 8-bit micros from Microchip Technology known as PICs (Programmable IC's) . I'm not going to say much more about them now but I will want one with an SPI (Serial Peripheral Interface) bus to drive the digital pot's.

Time for some maths! Hooray!

MIDI is transmitted at 31250 baud (31250 bits/s). Which means each bit's period is 1/31250 = 32us. Messages are transmitted in 10 bit packets with 8 data bits plus start and stop bits. So the message period is 320us.

Typical clock rate of a higher-end PIC is 40MHz (e.g. 18F458). This gives a clock period of 25 ns but a 100ns instruction cycle period with some assembler instructions (e.g. goto) taking 2 instruction cycles.

The SPI bus on a 40MHz PIC has a max clock rate (for 40MHz device) of 10Mbps. Which is 100ns per bit.

So what? Well, part of the key to this design is going to be the time avalibale to set a key after receiving a MIDI note message. The time avaliable would be 32us without a UART module in the PIC. Without a UART the program will have to be available every 32us to read the next bit but with a UART it only needs to read every byte which will arrive at the message rate of 320us.

320us is time to carry out 320 x 10e-6 / 100 x 10e-9 = 3200 single assmebler instructions or transmit as many bits on the SPI bus which should be plenty of time to decode the bytes and when neccessary update the digital pots for the 49 keys.

Analogue Devices make a 6 pot device, the AD5206 . The 5206 takes 11 data bits on the SPI bus, 3 to select the pot and 8 to set the postion of the wiper. So each pot is randomally accessable giving a fast access time. 9 of these could be used in parallel with a 4-16 line decoder selecting which device the data is for. This would give a write time in the region of a few micro seconds. With 9 AD5206’s daisy-chained (which might be easier to wire up) over 99 instructions would be needed per write but we're still well within the 3200 available.

But the PIC can only output a whole byte at a time so 11 bits will be tricky to manage.

The Maxim have a 6 pot packege DS1806 which clocks in 48 bits to set up the 6 pots. This equates to 4.8 us per device or 43.2 us for 9 devices in series which is still comfortably within the 320us. Good.

The only issue with the Ds1806 packge is that the resistance is linear and there are only 64 steps. If the key inputs respond in a logarithmic fashion, which I would expect, then I would have to re-scale the input velocity logarithmically. This can be done but as there are only 64 steps this may make the response a bit 'grainy'. The AD5206 is better in this respect as it has 256 steps but there remains the problem of writing 11 bits on the SPI bus.

An approximate log scale can be made from the linear taper by adding a resistor between the the wiper and ground as shown here. The flaw in this approach is that the 'pad' resistor is present even when the potentiometer is at zero ohms. More work needs to be done to see if this can be made to work.

That's enough for now...

Monday, March 14, 2005

Vinatge Synth Explorer & More Case Notes

Well, my comments have been added to the Vintage Synth Explorer site and perhaps even more excitingly this blog has been linked from that page. So, thanks to the guys over at VSE.

I've now ordered all the screws, nuts, washers and pillars I think I'll need to get the PCBs mounted. I've cut a piece of MDF for the base so all I'll need to do now is get the drill out. Previously I mentioned the four bushes fitted to the sides of the case. I postulated that they were for mounting something inside but if I'd read the data-sheet properly I would have seen that they are actually for fitting support rails to the sides of the case. Not to worry though as you can screw right through to the bushes and I can still use then for supports if I need to.

The next problem is wiring. You can see from the pictures that the wiring is something to behold and it's all been carefully tied into bunches with lengths of cotton. The looms were obviously laid out in the best arrangement for the keyboard case but now they're just making life difficult as I have a eleven PCBs all tied together and then all the front panel controls. All the moving about of boards and the years I've been fiddling with them have put a lot of stress on the wires and quite a few have come free. So in an effort to wrest control I've started to cut all the cotton ties and when I come to start fitting the PCBs to the base-board I'll undertake some resoldering and maybe desoldering and reattaching of various parts. Also, I think I'll disconnect all the front panel controls and get those wires loose until I'm ready with the temporary front panel.


I haven't thought much about the power supply lately (still need to consider the needs of the interface at some point) but once it's fitted into the case I'm going to have to put some sort of guard over the mains side of things. It'll probably just be some sort of cardboard box but I need something so that I can get my hands into the case when it's on and stay alive. I also need to get an RCD (Residual Current Device) to be on the safe side.

Thursday, March 10, 2005

SS30 on the web

I haven't looked for any SS30 stuff on the web for while and there's a couples of nuggets I've unearthed.

Firstly a discussion over on http://elists.resynthesize.com/analogue-heaven/2003/05/ threw this up...

From: Michael E. Caloroso ( [EMAIL REMOVED] )Date: May 7, 2003Subject: Re: [AH] yamaha SS30Jim Black wrote:
> Someone told me they were never available in the states - only sold
> in Canada and Europe. Considering their hybrid synth's came out at
> about the same time over here - that makes sense.
My guess is it was more that the SS30's ensemble FX was too close to the
patent ARP and Solina had on the ensemble FX used in their string
machines. They skirted the US patent system by restricting distribution.
This happens a lot in many industries.
MC

This lack of distribution in the U.S. may explains why the SS30 has remained relatively obscure.


Secondly there is now an entry for the SS30 at http://www.vintagesynth.org . I've already had word about putting it down as 4-voice polyphonic so we'll see if they change it. I've since noticed that they've also said there's no filter. Well the brilliance control could be considered a filter so I might mention that too.

Wednesday, March 09, 2005

PCB mounting

Here's a picture of the case!


I'm now worried I won't be able to get all the original switches to fit on the front panel.
I'm planning to make a mocked up front panel in MDF to see if it will all fit using the original switches.

So, now I have a case it's on to the mundane but vexed question of how I mount the PCBs in the case. I originally though about mount the PCBs vertically (along the long edges) as they were in the orignal case but the wiring terminals scattered around the edges make this difficult. So instead I'll stack the boards in horizontal layers. This still leaves one problem.

The case has a completely blank base (apart from an earthing point) so there's nowhere to fix anything to it without drilling through. If I drill though the base any nuts or bolts used to fasten into it will stand proud of the base and ultimately scrape the lid of whatever the case is resting on top of. As eth base is only 0.9 mm thick counter sunck screws won't pass muster here either.

I could drill holes and then fit bushes (AKA clinch nuts). These are nuts that are stamped into sheet metal and basically give you something to screew your bolts into. RS do bags of 50 for around £3.50 part number 827-625. Or they sell a 'nutsert' kit for abot £7.50 which has 100 pillars with threaded stubs which are also stamped into sheet metal like the bushes. You get a tool with kit too. This is a bit of scary option though and I'd rather not drill 30 or more holes into the base of my unit espescially when I'm a) not that experieced at metal work and b) new bases are expensive.

Fortunately the case already has bushes fitted on the inside of the side panels. There are two on each side about 1-2 cm above the base. You can just see the front two in the picture. I'm guessing that these are fitted for the purpose of mounting your own base plate and at present this is what intend to do. I can use a piece of MDF, around 5mm thick and then attach it to the side bushes with angle brackets. The MDF is easy and safe to drill and cut and I can fit counter sunk M3 bolts from the underside to fit M3 PCB pillars to on the top.

This is the next task then. I have to cut a piece of MDF to size and calculate how many nuts, bolts, washers, lock-washers, pcb-pillars I need and of what sizes. I also need to determine what size nuts the side bushes take and find suitable angle brakets to fix the MDF to the side bushes with.