• WARNING: Tube/Valve amplifiers use potentially LETHAL HIGH VOLTAGES.
    Building, troubleshooting and testing of these amplifiers should only be
    performed by someone who is thoroughly familiar with
    the safety precautions around high voltages.

Triode/Pentode Loadline Calculator

I added it to the list of REQUESTED!!! tubes (required by the simulator users), not to the simulator. There are two lists - tubes included in simulator and tubes waiting to be added. The list of requested tubes grows faster than the list of simulated tubes for the reason I mentioned in the previous post. Sorry for the misunderstanding.
 
Last edited:
6N9S is the equivalent of 6SL7 which is already on the list.

It occurs to me that, if you wanted, you could have entries in the dropdown list that are "proxies" for other tubes. That way you could list equivalent (or differently named versions) of tubes (say ECC83 and 12AX7) and instead of having a separate entry (I'm thinking of the tube data in the code) for each tube, the 12AX7 entry in the dropdown list would simply point to the ECC83 data. That way people don't need to know which tubes are equivalent to which.
 
It occurs to me that, if you wanted, you could have entries in the dropdown list that are "proxies" for other tubes. That way you could list equivalent (or differently named versions) of tubes (say ECC83 and 12AX7) and instead of having a separate entry (I'm thinking of the tube data in the code) for each tube, the 12AX7 entry in the dropdown list would simply point to the ECC83 data. That way people don't need to know which tubes are equivalent to which.

I will try to implement your idea in the next version 🙂

any chance of adding the 10 (or 10Y, which is the only form of the 10 currently findable

I have added this tube to the list of the Loadline Simulator.

For interested in Spice simulations below is it's Spice model:

**********************************************
.SUBCKT TUBEMODEL 1 2 3; A G C;
* Triode Simulator v.1.0
* Model created: Thu Jun 04 2015 20:21:32 GMT+0200
X1 1 2 3 TriodeK MU=8.07 EX=1.571 KG1=5297.4 KP=141 KVB=111 RGI=2000
+ CCG=0.0P CGP=0.0P CCP=0.0P;
.ENDS

****************************************************
.SUBCKT TriodeK 1 2 3; A G C
E1 7 0 VALUE=
+{V(1,3)/KP*LOG(1+EXP(KP*(1/MU+V(2,3)/SQRT(KVB+V(1,3)*V(1,3)))))}
RE1 7 0 1G
G1 1 3 VALUE={0.5*(PWR(V(7),EX)+PWRS(V(7),EX))/KG1}
RCP 1 3 1G ; TO AVOID FLOATING NODES IN MU-FOLLOWER
C1 2 3 {CCG} ; CATHODE-GRID
C2 2 1 {CGP} ; GRID-PLATE
C3 1 3 {CCP} ; CATHODE-PLATE
D3 5 3 DX ; FOR GRID CURRENT
R1 2 5 {RGI} ; FOR GRID CURRENT
.MODEL DX D(IS=1N RS=1 CJO=10PF TT=1N)
.ENDS TriodeK


I didn't verify the model in any circuits. Maybe someone will do it 🙂
 
gsmok, you might want to add the following to your page:


Code:
<meta http-equiv="cache-control" content="max-age=0" />
<meta http-equiv="cache-control" content="no-cache" />
<meta http-equiv="expires" content="0" />
<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
<meta http-equiv="pragma" content="no-cache" />
This will prevent browser from caching old versions and should eliminate this problem. The page itself is only about 160K worth of data (not including the Google ads, which won't cache anyway), so it ought not be a big burden on users to eliminate the caching.

Or, alternatively, for just preventing the JavaScript file from caching you could do something like:
Code:
 <script src="triodepublic.js?_=1"></script>
And just increment the number (the 1 in the above) every time you update the script and it will force browsers to load the new version.
 
Last edited: