MUFF WIGGLER Forum Index
 FAQ & Terms of UseFAQ & Terms Of Use   Wiggler RadioMW Radio   Muff Wiggler TwitterTwitter   Support the site @ PatreonPatreon 
 SearchSearch   RegisterSign up   Log inLog in 
WIGGLING 'LITE' IN GUEST MODE

The open source Jupiter-8-4-ALL project
MUFF WIGGLER Forum Index -> Music Tech DIY Goto page 1, 2  Next [all]
Author The open source Jupiter-8-4-ALL project
dikkietrom
Through the courtesy of

- Mr Ikutaro Kakehashi, Roland
- Grenoble Institute of Technology, http://kicad-pcb.org/
- Alfons Wirtz, freerouter.net
- Jack Damery, An in depth look at the Roland Jupiter 8's VCO
- Open music labs, open source ba662
- Tiergrinder, DIY Jupiter 8
- https://jup8restoration.wordpress.com/about/

I started this project https://gitlab.com/anatal/JP8-4-ALL

The purpose is also to offer an open poly synth platform with a solid reference implementation. Current state is that the voice board schematic is drawn in kicad and the board is routed with freerouter. I am doing this for the sake of the best possible outcome and to give back.

Impression

Jarno
Nice work!
StillNotWorking
dikkietrom wrote:
The purpose is also to offer an open poly synth platform with a solid reference implementation.

This sentence makes me warm and fuzzy inside. Also love the way you credits those before you working this topic. thumbs up

Best of luck going forward. Only wish I had time get involved with this now.

btw, do this project have an active discussion somewhere?
devinw1
Very cool! Will be following!
dikkietrom
Thanks for reactions, that keeps me motivated. I will discuss here everything, it is the right place I think.

I finalized the proto system architecture roughly. It sticks to the original architecture but the digital aspect is implemented with Arduino.
Basically done drawing for the first protobuild. There will be midi to gate signals and pot panel control for basic control while testing. The pots I will put on breadboard or carton or whatever. The voice will go straight on pcb. The original has 2 voices on 1 board but I will start with one voice. One voice (2 x vco,vcf,2 x adsr,vca) has 484 components and I started of wrong by not specifying straight away the resistor types so I have to carefully check them all. Fortunately kicad makes that somewhat easy. I had mixed feelings while replicating the scheme, it was stressfull but also mesmerizing. The service manual itself is a masterpiece, I am very impressed by it.

I am not looking forward to soldering all the discrete parts. The board is now ca 400x200 with 1661 holes. Minimum order at elecrow is 5 pieces for $12 each so I don't care about optimizing space now. Assembly is another story, the bom shows 100 different parts but it will probably be more if I specified them all correctly, lets say 150. That can be assembled for $687 at 1 piece. That's not really an option, the sweet spot is at 100 pieces, then it is $43 for a fully assembled THT board. Smd $18 dollar.

Anyways first things first. I will start with an original ir3109 just to check quickly if the board works. I cannot find an IR3R01, if someone spots one please let me know. It will be great if the board proves to be correct asap, then the hunt for the right sound can begin, can't wait.
whoop_john
dikkietrom wrote:
I will start with an original ir3109

Don't know if this is legit or not on Aliexpress:
IR3R01 click on last item.
Sebo
Wow!!! Nice project!
Thanks for sharing smile
home_listening
Hey, that is a very odd format... System design is the big challenge with a project like this.

I couldn't recommend using an autorouter for anything.

I poked around at cloning the Jupiter 8 a few years ago, this is where I left it. Far, far, far from finished.

I think a poly format in the eurorack rack format (Not eurorack synth format, the real one) with all trimpots on the rear and a direct out jack for each voice perhaps would be pretty neat.

flts
home_listening wrote:
I think a poly format in the eurorack rack format (Not eurorack synth format, the real one) with all trimpots on the rear and a direct out jack for each voice perhaps would be pretty neat.


I think Jürgen Haible (rest in peace) did some of his stuff like that - at least one of the Moog PS clones seemed to have all of the dozens of voice cards installed in an Eurocard frame. Not sure if he used a backplane or just the frame though.

FWIW especially with a complex project like this, I agree that autorouting is a bit scary regarding how well the circuit will perform / function. Then again, I don't want to discourage anyone with a cool project like this, and if worst comes to worst and there are issues with the layout, it's always possible to reroute everything as the project is open.
home_listening
Yeah, I think it was his PS3300 Clone.

I'd hate to be discouraging too, just throwing my 2c in!

flts wrote:
home_listening wrote:
I think a poly format in the eurorack rack format (Not eurorack synth format, the real one) with all trimpots on the rear and a direct out jack for each voice perhaps would be pretty neat.


I think Jürgen Haible (rest in peace) did some of his stuff like that - at least one of the Moog PS clones seemed to have all of the dozens of voice cards installed in an Eurocard frame. Not sure if he used a backplane or just the frame though.

FWIW especially with a complex project like this, I agree that autorouting is a bit scary regarding how well the circuit will perform / function. Then again, I don't want to discourage anyone with a cool project like this, and if worst comes to worst and there are issues with the layout, it's always possible to reroute everything as the project is open.
home_listening
Re: Autoroute

With both the Pro One clone and SEM clone I did, after dumb mistakes from transcribing the schematics were sorted out, most of the hard work was finessing the layout to eliminate crosstalk. This was particularly hard on the Pro One where the mod bus was running signals 40cm from the ADSR over to the other side where the mod matrix is then back over to the filter modulation.
flts
home_listening wrote:
With both the Pro One clone and SEM clone I did, after dumb mistakes from transcribing the schematics were sorted out, most of the hard work was finessing the layout to eliminate crosstalk. This was particularly hard on the Pro One where the mod bus was running signals 40cm from the ADSR over to the other side where the mod matrix is then back over to the filter modulation.


Yeah, I suppose in this case eg. getting the bypass caps close to where they need to be, routing the multitude of signals in a way that one avoids serious crosstalk, keeping the layout of VCO (core) tight and sane enough to keep it
as stable as possible, etc. contribute quite greatly to the end result.

But in any case, I suppose this just serves as a sort of a warning that if things won't work as intended in first prototypes (they never do), there's much to be gained by careful manual rerouting.

Very interested in seeing what becomes of this smile
StillNotWorking
Not designing for production simple wire runs are a valid option I think. Modularize also keep troubleshooting simpler and makes for modular build process where new ideas easily can be inserted.

Last 5-7 years many sdiy projects has become obsessed with everything has to be soldered to a pcb. seriously, i just don't get it
dikkietrom
whoop_john wrote:
dikkietrom wrote:
I will start with an original ir3109

Don't know if this is legit or not on Aliexpress:
IR3R01 click on last item.


Someone tried that on the anafrog forum and it does not seem to be ok. The pics that tiergrinder uses arived yesterday, will use that for now with an adapter.
dikkietrom
Re autoroute

The board layout is also in the service notes, if some cares to map that I will certainly go with it. For proving the sceme is correctly implemented it is not really relevant is my exeperience, therefore I prefer progress for now.
I also use auto placement but it spreads per subsheet it seems, was surprised about that. In the rules you can specify track width and spacing, that guards somewhat against crosstalk. I will space out long running parallels, thanks for the input.
dikkietrom
StillNotWorking wrote:
Not designing for production simple wire runs are a valid option I think. Modularize also keep troubleshooting simpler and makes for modular build process where new ideas easily can be inserted.

Last 5-7 years many sdiy projects has become obsessed with everything has to be soldered to a pcb. seriously, i just don't get it


Point 1 is spot on, subsheets can be used as components which makes it very easy to maintain. It is the only way I am able do take this on with joy.

Point 2 not so much (for me) You are in despair cause others like to work with fixed boards? I totally don't get your point. DIY is relative, I am sure you are not into DIY metal mining. There is probably a correlation between the costs of board manufacturing and your observations IMHO
StillNotWorking
dikkietrom wrote:

Point 2 not so much (for me) You are in despair cause others like to work with fixed boards? I totally don't get your point. DIY is relative, I am sure you are not into DIY metal mining. There is probably a correlation between the costs of board manufacturing and your observations IMHO

Not exactly, more to the fact one lock users into panel design and components to use. Defeating some of the DIY aspect of it for others to explore. Also it often include an assembly scheme that hinder troubleshooting and mods to be done to the design.
home_listening
I personally consider every wire I strip and solder to be a failure on my part, but then again I only build my own projects with my own PCBs so I'm not locked into anyone else's design - I make the design.



StillNotWorking wrote:
dikkietrom wrote:

Point 2 not so much (for me) You are in despair cause others like to work with fixed boards? I totally don't get your point. DIY is relative, I am sure you are not into DIY metal mining. There is probably a correlation between the costs of board manufacturing and your observations IMHO

Not exactly, more to the fact one lock users into panel design and components to use. Defeating some of the DIY aspect of it for others to explore. Also it often include an assembly scheme that hinder troubleshooting and mods to be done to the design.
flts
It's good to bear in mind that even with a "panel" PCB one can practically always manually wire the panel components if needed. It's especially easy if it's a separate control PCB that sandwiches to main board with headers that have a clear logical pin mapping so that one can use eg. .100" connectors for wiring.

But not vice versa.
dikkietrom
StillNotWorking wrote:

Not exactly, more to the fact one lock users into panel design and components to use. Defeating some of the DIY aspect of it for others to explore. Also it often include an assembly scheme that hinder troubleshooting and mods to be done to the design.


I don't think I used providers that have the restrictions you mention. In the context of my personal capabilities it is more efficient to work with a fixed proto board. I start with complete THT for the sake of flexibility. With small concepts I use wire-wrapping but that is not really an option now.
dikkietrom
Checked all component values, found a handfull wrong ones and a missing wire. Will check it one more time and if nothing found then consider it ok. Replaced direct BA662, IR3R01 and IR3109 implementaions with original footprints. Implementation is either original or something adapted.

I have been thinking about the autorouting and placement comments, especially regarding the decoupling caps and decided to replicate the placement from the service manual for the proto board. That has to happen anyway so as might well do it now. It will add another few days.
dhaillant
Interesting project!
Autorouting is, IMO, unnecessary, adds complexity, errors, and a lot of work in the end.
dikkietrom
It depends which autorouter you use and how you use it. My experience is that it mainly helps a lot with optimizing placement. It's not a black and white thing. Also you can use it to route just parts of the board that are no brainers. With freerouter you can manually push and shove a lot better than with kicad. It's a fine tool. I totally agree that one should not blindly autoroute a final board.

I am halfway annotating the scheme analog to the service notes scheme (no pun). The automated annotations were not so convinient for the board replication. A scheme trip takes about a full day, just one voice that is. Glad I did not already draw the controller like the voice, without the component numbers and types.

A controller per voice would be nice, then any split is possible. 1/7,3/5,4/4 or 4x2 and so on. Depends on how much sample and hold leak one dac can handle or if an affordable dac will do.

I have a 32 channel dac chip but too expensive to use 1 channel per cv. A voice needs 32 cv signals and 1 gate. If one channel can serve 32 sample and holds then it is another story, that would mean a potential jp32.
StillNotWorking
dikkietrom wrote:
Depends on how much sample and hold leak one dac can handle or if an affordable dac will do.

Could S&H of the original hold some artefacts that would add to the analog fluctuating? At least that would simplify the search for a DAC hihi
dikkietrom
I am somewhat surprised and confused about the dac's, I always thought memory was 12bit or 14bit but it is 8bit on the controller for pot data and 12/14bit on the interface for key cv. The 8 bit is a discrete ladder.

Btw it is not 32 sh but "only" 23 per dac throug 3x8-channel multiplexers, I have no clue about the s&h refresh rate, the z80 has 8mhz clock.

Anyways the voice scheme is annotated with original references now, the original scheme has some missing references but that can be recalled from the board layout. Found one more wrong junction in the kicad scheme. In hindsight it was not so bad that I had to go over it a few times cause I found mistakes that otherwise might have been unnoticed.
I am going to take a little break. Looking forward to replicate the component placement.
MUFF WIGGLER Forum Index -> Music Tech DIY Goto page 1, 2  Next [all]
Page 1 of 2
Powered by phpBB © phpBB Group