New guy <--

Hi there all. I just discovered ktechlab yesterday as an option to
install into a Ubuntu system.

This looks like... it has a TON of promise. I love the real-time
oscilloscope and the simple way of dragging a component and hooking it up.

I've been reading the archives and I'm glad it's been resurrected from
the dead. I *also* want to get vacuum tube / valve diodes, triodes, and
pentodes implemented ;) I'm pursuing simulation of analog audio circuits
and while I realize that this is not the main thrust of ktechlab, this
is the easiest to use program I've run across yet. It's worth expanding
and developing.. who knows? It could become the standard in the future
once it's been refactored, ported to the relevant architectures, freed
up from hard-coded components, extensibility has been added, etc. The
rest of the EDA stuff on GNU/Linux systems, like gEDA, are a nasty pain
to use.

I've got some C++ background mostly in QT3, a bit of OGL, and I'm a
professional tech doc writer for a living who is very impatient with
software so I tend to simplify the interfaces I write to the bare
minimum while remaining complete. I'd love to contribute; this is a
sweet-looking project.

So the question is, what should I do and where should I start?

Incidentally, would there be any plans to implement free-rotation, so
that the diodes in my bridge rectifier can actually be placed in the way
they are normally drawn on a schem? gschem doesn't do it and I think
qucs doesn't either.

Re: New guy <--

Hey Glen,
nice to hear, that you're interested in helping out on KTechLab.

On Thursday 06 November 2008 16:26:05 Glen wrote:
> This looks like... it has a TON of promise. I love the real-time
> oscilloscope and the simple way of dragging a component and hooking it up.
Yes, I also like the UI very much, that was also what attracted me some years 
ago. And I'm quite sure, we can even make it better.

> I've got some C++ background mostly in QT3, a bit of OGL, and I'm a
> professional tech doc writer for a living who is very impatient with
> software so I tend to simplify the interfaces I write to the bare
> minimum while remaining complete. I'd love to contribute; this is a
> sweet-looking project.
>
> So the question is, what should I do and where should I start?
Well, you said you want new compontents to be implemented ;) Why not start 
working on the simulator? I really think this one needs some love, too. Zoltan 
and Alan did some work on it during the last weeks. Zoltan did some 
refactoring and Alan is more into the "functional"-part. What do you think? Is 
the simulator an interesting part for you?

> Incidentally, would there be any plans to implement free-rotation, so
> that the diodes in my bridge rectifier can actually be placed in the way
> they are normally drawn on a schem? gschem doesn't do it and I think
> qucs doesn't either.
I am currently working on all that. I haven't fully decided a way to got, yet. 
But I know that we will make use of QGraphicsView in some form or another. 
This makes every kind of graphics-manipulation very easy and fast and 
everything ;) (including free-rotation) The problems I see here is how to 

Re: New guy <--

>> So the question is, what should I do and where should I start?

> Well, you said you want new compontents to be implemented ;) Why not start 
> working on the simulator? I really think this one needs some love, too. Zoltan 
> and Alan did some work on it during the last weeks. Zoltan did some 
> refactoring and Alan is more into the "functional"-part. What do you think? Is 
> the simulator an interesting part for you?
> 

Sure.. I'm gonna need to get up to speed with current vs. outside
industry techniques. I'm gonna need to co the code first, probably after
work today and play with breaking the models.

>> Incidentally, would there be any plans to implement free-rotation, so
>> that the diodes in my bridge rectifier can actually be placed in the way
>> they are normally drawn on a schem? gschem doesn't do it and I think
>> qucs doesn't either.
> I am currently working on all that. I haven't fully decided a way to got, yet. 
> But I know that we will make use of QGraphicsView in some form or another. 
> This makes every kind of graphics-manipulation very easy and fast and 
> everything ;) (including free-rotation) The problems I see here is how to 
> handle the routing of our "wires", but I guess there is some way to do it.
> 
> At the moment I'm working on refactoring and porting the whole 
> ProjectManagment-part to use KDE4 libraries. I got quite some stuff working 
> now, I hope, I can get something ready till the weekend. After being able to 
> load projects, I want to do some experiments with the QGraphicsView and so 
> find out a good way how to display our circuits.

Re: New guy <--

I should probably ask.. is anyone else in the simulator?

--Glen

Re: New guy <--

On Thursday 06 November 2008 17:52:26 Glen wrote:
> >> So the question is, what should I do and where should I start?
> >
> > Well, you said you want new compontents to be implemented ;) Why not
> > start working on the simulator? I really think this one needs some love,
> > too. Zoltan and Alan did some work on it during the last weeks. Zoltan
> > did some refactoring and Alan is more into the "functional"-part. What do
> > you think? Is the simulator an interesting part for you?
>
> Sure.. I'm gonna need to get up to speed with current vs. outside
> industry techniques. I'm gonna need to co the code first, probably after
> work today and play with breaking the models.

>I should probably ask.. is anyone else in the simulator?
You can find the refactoring work, Zoltan has done, in the svn repository. 
Find it in /doc/devel/ in trunk. He did some work on the data model for the 
compontents. This is also the part, where the XML-representation of components 
will be settled. The main simulator just uses this model to calculate all 
currents and voltage stuff for each component. I can't be very precise here, 
because I haven't looked into this part very close. My english is also quite 
limited in the electronics area, but I try to get into it. ;)

> > At the moment I'm working on refactoring and porting the whole
> > ProjectManagment-part to use KDE4 libraries. I got quite some stuff
> > working now, I hope, I can get something ready till the weekend. After
> > being able to load projects, I want to do some experiments with the
> > QGraphicsView and so find out a good way how to display our circuits.
>
> You switching it over to an XML format?
I only work on the visual part, yet. The view doesn't care about components 

Italian translation

The wiki say that there's an italian translation. How can I get it?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: Italian translation

On Thursday 06 November 2008 19:03:16 Mariano MARINI wrote:
> The wiki say that there's an italian translation. How can I get it?
It ships with the source-code. (At least there is a it.po file in the svn 
trunk). So you should just tell KDE to use Italian as the main language. (Is 
there a "Switch Application Language..."-entry in the Help-menu in KDE3? I 
can't remember and I have no machine to test it.)

bye then
julian

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Ktechlab-devel mailing list
Ktechlab-devel@...
https://lists.sourceforge.net/lists/listinfo/ktechlab-devel

Help

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Ktechlab-devel mailing list
Ktechlab-devel@...
https://lists.sourceforge.net/lists/listinfo/ktechlab-devel

simulator

Is there any direction / ideas for what direction the simulator should
go? I have my own ideas, especially now since I've probed the code a
little bit, but what's really better for the project?

What would people like to see it do beyond what it does now?

--G

Re: New guy <--

Glen wrote:

> Hi there all. I just discovered ktechlab yesterday as an option to
> install into a Ubuntu system.

> This looks like... it has a TON of promise. I love the real-time
> oscilloscope and the simple way of dragging a component and hooking it up.

It's more of a chart recorder than a 'scope but it is fairly useful....

> I've been reading the archives and I'm glad it's been resurrected from
> the dead. I *also* want to get vacuum tube / valve diodes, triodes, and
> pentodes implemented ;) I'm pursuing simulation of analog audio circuits

I'm working on a class AB1 2A3 push-pull design. I've selected a design
based on the voltage gain and driver stage in Morgan Jones' Crystal
Palace amp.

Open problems in the design is the input stage... I want to support both
balanced and single ended input and there's also the problem of feedback
because I'll be pushing the output stage into AB1, I need to use
feedback to moderate the distortion...

>The rest of the EDA stuff on GNU/Linux systems, like gEDA, are a nasty pain
> to use.

;)

> I've got some C++ background mostly in QT3, a bit of OGL, and I'm a
> professional tech doc writer for a living who is very impatient with
> software so I tend to simplify the interfaces I write to the bare
> minimum while remaining complete. I'd love to contribute; this is a
> sweet-looking project.

Welcome aboard.

> So the question is, what should I do and where should I start?

here's the biggest bug I'm seeing on my machine...

I have this simulation of my father's Harman Kardon 430 (from 1974)...
The amp works (even though it doesn't seem to for the first few
minutes... the real amp takes about 30 seconds for the input
differential amp to un-clamp... =\

the problem is when I go to save it and load it, the entire circuit is
messed up. 2/3rds of the connectors are gone, there are a lot of
dangling junctions.... Undo/redo creates a similar effect. The problem
must be in the document heirarchy, It's all based on QT's DOM/XML engine.

On the simulation engine, an important issue is that temperature is
currently a constant. Temperature is an important variable in solid
state circuitry, my harman kardon sim, for example, can't simulate the
thermal diodes that are used to throttle the power stage. My idea was to
implement heatsink domains so that all components in that domain are
simulated at a temperature based on the total power dissipation in that
domain scaled by the heatsink coeficient...

In classic electronics, the issue is how emissive the cathode is... This
is an issue as the device warms up...

> Incidentally, would there be any plans to implement free-rotation, so
> that the diodes in my bridge rectifier can actually be placed in the way
> they are normally drawn on a schem? gschem doesn't do it and I think
> qucs doesn't either.

The most important issue right now is to implement multiple winding
inductors, IE transformers... That's a serious deficiency at present...

[later]

> Is there any direction / ideas for what direction the simulator should
> go?

I've made some proclamations, but those are only directed at people who
don't have their own ideas. ;)

> I have my own ideas, especially now since I've probed the code a
> little bit, but what's really better for the project?

Lay them on us!

What's best for the project is that you get hooked on tweaking stuff....

> What would people like to see it do beyond what it does now?

me need triode. ;)

Seriously, we need to implement a components database. The worst will be
configurable devices that might have variable numbers of grids (with
variable densities), and inductors with variable numbers of coils with
variable numbers of turns...

--

-- 
New president: Here we go again...
Chemistry.com: A total rip-off.
Powers are not rights.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/