¿ªÔÆÌåÓý

Date

Re: 3582A repair success

 

Dave,.
Just curious, there was an electron microscope for sale on Govplanet a few weeks ago, which interested me both from a learning perspective and as a source of a good vacuum system, can't remember the name but it was European. Sounds like it can be possible to support your own system or are they tied up with proprietary software of some kind ?

On Tue, Sep 8, 2020, 11:09 AM Dave McGuire <mcguire@...> wrote:

? ?Recall that, last week, I was working on a 3582A spectrum analyzer in
which the +5.1V regulator had failed.

? ?The switching regulator employs a large IC, a Microsemi PIC646 as the
switching element.? It's a strange part that integrates two power
transistors, two resistors, and a diode in a TO-3 package with three
(yes three!) leads.? The transistors are arranged as a Sziklai pair, and
the diode fulfills the role of the catch diode in a switching regulator.

? ?The "outer" transistor in the Sziklai pair was a dead short.

? ?I was able to locate one at a component vendor whom I trust; it was a
bit pricey but it's a long-discontinued part.? It arrived this morning,
I installed it, and the 3582A is now functional.

? ?I'm keeping the failed part, for when I get my electron microscope
back up and running.

? ? ? ? ? ? ? -Dave

--
Dave McGuire, AK4HZ
New Kensington, PA




Re: 3582A repair success

 

A happy ending..!

Thinking that at some point the old part stock will run out, and perhaps your investigation might reveal how to recreate the part with individual currently available components...

_Dave KC6UPS


Re: Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

There is also the problem where software updates break existing systems. An example of this from some time ago? was a professional C compiler fro embedded systems. New version came out and duly installed with no issues, until we tried to change an older progam. It all complied without issues but the resulting code didn't work. Recompline the unaltered source code didn't work either. It was a while ago but IIRC it was a device libary incompability. Choices appeared to be re-write the code completely, get an old copy with separate licence on a standalone machine or leave the code as was. As the chane was to change the timing of a pulse to allow a specific task I ended up doing a bodge with a 6 pin PIC that monitored the pulse and another signal and changed it according. It replaced two resistors and looked like two resistors an a blob of epoxy.

Robert G8RPI.


Re: Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

Also note that I mentioned programs that *I* wrote, implying not only knowledge of the structure but of course, the source code itself.? There's stuff I won't bother to rewrite.

We also can fall into the trap where:

1) the program is sold and the new owners want a subscription (EAGLE, and don't ask....)

2) the program behaves oddly or wants more money each year (Microsoft Office... replaced by Libre Office, personal choice).

3) the new owners want a LOT Of money and got rid of the "Free" version (Borland Pascal....) replaced by Lazarus Pascal

4) the owners stopped updating the software (too many programs to mention).

Harvey

On 9/8/2020 9:06 PM, Toby wrote:
On 2020-09-08 8:05 p.m., Harvey White wrote:
Hmmm

Well, I write a lot of my own programs, and databases for the programs
(assuming they use them) are easy enough when the programs use that
data, have a similar data structure, or I had enough time invested in
the program to make it worthwhile translating structures.

You have to design that backwards compatibility *into* the programs, if
it makes sense.

It's possible to design a program so different (not that you should)
that importing data from the last one makes no sense.

Having said that, there's a Kanji dictionary program that, if I ever
resurrect it, would be able to read the old data files.

Then again, I wrote that, and the effort would be worth the effort.
Yes, the key word is EFFORT, I didn't say it was impossible but it all
takes WORK to make happen, to migrate data, to make things futureproof,
to continue porting them forward year by year. And you're just b*ggered
if you're using proprietary stuff that didn't.

--T


Harvey



On 9/8/2020 5:18 PM, Toby wrote:
On 2020-09-08 3:32 p.m., Paul Amaranth wrote:
Gotta agree with Dave here.? Software can last forever.
Not without extraordinary effort.

Didn't really want to add to an off topic thread, but just preserving
_data_ is a hard problem. Keeping programs buildable and runnable is
even harder.

--T





Re: Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

On 2020-09-08 8:05 p.m., Harvey White wrote:
Hmmm

Well, I write a lot of my own programs, and databases for the programs
(assuming they use them) are easy enough when the programs use that
data, have a similar data structure, or I had enough time invested in
the program to make it worthwhile translating structures.

You have to design that backwards compatibility *into* the programs, if
it makes sense.

It's possible to design a program so different (not that you should)
that importing data from the last one makes no sense.

Having said that, there's a Kanji dictionary program that, if I ever
resurrect it, would be able to read the old data files.

Then again, I wrote that, and the effort would be worth the effort.

Yes, the key word is EFFORT, I didn't say it was impossible but it all
takes WORK to make happen, to migrate data, to make things futureproof,
to continue porting them forward year by year. And you're just b*ggered
if you're using proprietary stuff that didn't.

--T



Harvey



On 9/8/2020 5:18 PM, Toby wrote:
On 2020-09-08 3:32 p.m., Paul Amaranth wrote:
Gotta agree with Dave here.? Software can last forever.
Not without extraordinary effort.

Didn't really want to add to an off topic thread, but just preserving
_data_ is a hard problem. Keeping programs buildable and runnable is
even harder.

--T





Re: Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

The 11794A software that was part of the 8902S microwave measurement system - Stretch goal was also to find the 11795A software that was part of the 8952S and the 11806A Attenuator Test Software & 11808A Signal generator Software.

I've heard that these might be dongle locked but I haven't ever spoken to someone who has the software to confirm.

TonyG


Re: Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

On 9/8/20 8:03 PM, Tony Goodhew wrote:
And to bring it back on topic, lately I've been doing it with HP
measurement automation software.
Not wanting to get anyone in trouble here but I'd be very interested in a list of the software you've managed to preserve - I've been looking for a couple of HP apps now for many years and haven't found anything yet so I despair of ever being able to get a hold of it for my devices here.
Most recently I got the HP 3048A and 3047A phase noise measurement software running, and just before that, the 85867A and 85869A EMI receiver software.

Next I'll be working on a large pile of floppies that contain calibration and verification software for many random HP instruments.

I am searching in earnest for the software for the 9825 that controls the 5390A Frequency Stability Analysis System. I fear that may actually be lost.

What have you been looking for?

-Dave


--
Dave McGuire, AK4HZ
New Kensington, PA


Re: Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

Hmmm

Well, I write a lot of my own programs, and databases for the programs (assuming they use them) are easy enough when the programs use that data, have a similar data structure, or I had enough time invested in the program to make it worthwhile translating structures.

You have to design that backwards compatibility *into* the programs, if it makes sense.

It's possible to design a program so different (not that you should) that importing data from the last one makes no sense.

Having said that, there's a Kanji dictionary program that, if I ever resurrect it, would be able to read the old data files.

Then again, I wrote that, and the effort would be worth the effort.

Harvey

On 9/8/2020 5:18 PM, Toby wrote:
On 2020-09-08 3:32 p.m., Paul Amaranth wrote:
Gotta agree with Dave here. Software can last forever.
Not without extraordinary effort.

Didn't really want to add to an off topic thread, but just preserving
_data_ is a hard problem. Keeping programs buildable and runnable is
even harder.

--T



Re: Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

Hey Dave,
And to bring it back on topic, lately I've been doing it with HP measurement automation software.

Not wanting to get anyone in trouble here but I'd be very interested in a list of the software you've managed to preserve - I've been looking for a couple of HP apps now for many years and haven't found anything yet so I despair of ever being able to get a hold of it for my devices here.

Thanks,

TonyG


Re: Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

On 2020-09-08 6:07 p.m., Dave McGuire wrote:
On September 8, 2020 5:18:30 PM "Toby" <toby@...> wrote:
On 2020-09-08 3:32 p.m., Paul Amaranth wrote:
Gotta agree with Dave here. Software can last forever.
Not without extraordinary effort.

Didn't really want to add to an off topic thread, but just preserving
_data_ is a hard problem. Keeping programs buildable and runnable is
even harder.
Nah. Again, this is something I do every day. Replication is the key. Software is a lot easier than data in that regard. Occasionally things get lost, but really, it's been a very small percentage.

This is practice, not theory.

And to bring it back on topic, lately I've been doing it with HP measurement automation software.
OK, so you are putting in the aforementioned extraordinary effort. Cool.

--T


-Dave


Re: Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

On September 8, 2020 5:18:30 PM "Toby" <toby@...> wrote:
On 2020-09-08 3:32 p.m., Paul Amaranth wrote:
Gotta agree with Dave here. Software can last forever.
Not without extraordinary effort.

Didn't really want to add to an off topic thread, but just preserving
_data_ is a hard problem. Keeping programs buildable and runnable is
even harder.
Nah. Again, this is something I do every day. Replication is the key. Software is a lot easier than data in that regard. Occasionally things get lost, but really, it's been a very small percentage.

This is practice, not theory.

And to bring it back on topic, lately I've been doing it with HP measurement automation software.

-Dave

--
Dave McGuire, AK4HZ
New Kensington, PA


Re: OT: Looking for recommendations on 3D modeling software

 

Google it. Articles and demonstrations abound. I've worked security too, since that seems to be relevant.

-Dave

On September 8, 2020 5:30:13 PM "Sandra Carroll" <smgvbest@...> wrote:
I'm going to drop most of this convo but this statement I can not leave alone.
" The reason they don't want z/OS source code released is so that the cracker kiddies don't see just how much it is Swiss cheese with regard to security."
I have no idea where you get these false facts from but they are indeed false.

And FWIW, I am a z/OS Security engineer and I was a Linux RHCE and Windows MCSE in the past.

Sandra Carroll

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave McGuire
Sent: Tuesday, September 8, 2020 1:23 PM
To: [email protected]
Subject: Re: [HP-Agilent-Keysight-equipment] OT: Looking for recommendations on 3D modeling software

On 9/8/20 12:55 PM, Sandra Carroll wrote:
Disagree,
Im talking about code out on github or sourceforge that are setup as you describe.
Projects die. I cannot quote the source exactly but where was an article that showed that over 70% if not higher Opensource project die.
I actually think it was like 90% but can not be sure, I know it was high.

Unless a project is widely adopted it will eventually die no mater how good it is.
If you're talking about "projects", sure, they die all the time. But the subject here is SOFTWARE. And making that assertion about software isn't just questionable, it's dead wrong, and I prove it every day.

I do this literally every day at the museum, and sometimes outside the museum. Hell, just last night I got a piece of HP software up and running that hasn't been supported since the 80s and I'm pretty sure nobody else has run since not long after that. Why? The source code was published.

The "project" is long since dead, but who cares? The software runs just fine.

This is something we do, very literally, every day at the museum, and I've done it over and over in other environments when the software wasn't quite so old.

As I inferred I'm a mainframe person. MVS was in todays terms open source. Infact you can get MVS 3.9 still as its under that license.
But at that time there was no github. No way to really share code. After taking so many calls asking to fix code companies wrote IBM decided to go OCO (object code only)
So they could support their customers needs consistently.

Fast forward to today. No one wants z/OS (formerly MVS) to go opensource. Most of its' customers are in financial. Security is extremely tight
Governments use it. None want z/OS to go opensource. And there's nothing wrong with that. Its want we the customers want and isnt' that the point.
The reason they don't want z/OS source code released is so that the cracker kiddies don't see just how much it is Swiss cheese with regard to security. That's a documented fact; z/OS binary distributions have been floating around illicitly for years and people have performed penetration testing on it. Information on this is everywhere. The best thing that could ever happen to z/OS would be to release the source code, so a few million young and communicative eyeballs, (rather than a few dozen old and isolated ones, could audit that code.

But of course that'd be a disaster, because of the security breaches that would occur first, after the flaws are discovered but before PTFs are rolled out.

And people have been sharing code for decades...wow, Sandra, github did not invent source code sharing! Heck, even in the somewhat stunted and isolated IBM mainframe world there was (and still is!) the SHARE group and the CBT tapes! Open source software has been the way of computing since there WAS computing. Suits rolling in after the fact and commercializing everything was, and is, still an outlier for many of us. There is, and always has been, far more open source software in the world than closed source.

IBM gave away their OSs at first because they didn't see any intrinsic value in software; they wrote it to sell hardware, and for no other reason. They closed it up when they realized they could make people pay for it, and thus create a new (and huge) profit center. This is a documented and well-known fact.

I'm sorry to be so disagreeable, but you're incorrect on so many levels here that I just can't sugar-coat it. It's nothing personal and of course I mean no disrespect whatsoever; I just have to correct your rather dramatic misconceptions.

-Dave

--
Dave McGuire, AK4HZ
New Kensington, PA






--
Dave McGuire, AK4HZ
New Kensington, PA


Re: OT: Looking for recommendations on 3D modeling software

Sandra Carroll
 

I'm going to drop most of this convo but this statement I can not leave alone.
" The reason they don't want z/OS source code released is so that the cracker kiddies don't see just how much it is Swiss cheese with regard to security."
I have no idea where you get these false facts from but they are indeed false.

And FWIW, I am a z/OS Security engineer and I was a Linux RHCE and Windows MCSE in the past.

Sandra Carroll

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave McGuire
Sent: Tuesday, September 8, 2020 1:23 PM
To: [email protected]
Subject: Re: [HP-Agilent-Keysight-equipment] OT: Looking for recommendations on 3D modeling software

On 9/8/20 12:55 PM, Sandra Carroll wrote:
Disagree,
Im talking about code out on github or sourceforge that are setup as you describe.
Projects die. I cannot quote the source exactly but where was an article that showed that over 70% if not higher Opensource project die.
I actually think it was like 90% but can not be sure, I know it was high.

Unless a project is widely adopted it will eventually die no mater how good it is.
If you're talking about "projects", sure, they die all the time. But the subject here is SOFTWARE. And making that assertion about software isn't just questionable, it's dead wrong, and I prove it every day.

I do this literally every day at the museum, and sometimes outside the museum. Hell, just last night I got a piece of HP software up and running that hasn't been supported since the 80s and I'm pretty sure nobody else has run since not long after that. Why? The source code was published.

The "project" is long since dead, but who cares? The software runs just fine.

This is something we do, very literally, every day at the museum, and I've done it over and over in other environments when the software wasn't quite so old.

As I inferred I'm a mainframe person. MVS was in todays terms open source. Infact you can get MVS 3.9 still as its under that license.
But at that time there was no github. No way to really share code. After taking so many calls asking to fix code companies wrote IBM decided to go OCO (object code only)
So they could support their customers needs consistently.

Fast forward to today. No one wants z/OS (formerly MVS) to go opensource. Most of its' customers are in financial. Security is extremely tight
Governments use it. None want z/OS to go opensource. And there's nothing wrong with that. Its want we the customers want and isnt' that the point.
The reason they don't want z/OS source code released is so that the cracker kiddies don't see just how much it is Swiss cheese with regard to security. That's a documented fact; z/OS binary distributions have been floating around illicitly for years and people have performed penetration testing on it. Information on this is everywhere. The best thing that could ever happen to z/OS would be to release the source code, so a few million young and communicative eyeballs, (rather than a few dozen old and isolated ones, could audit that code.

But of course that'd be a disaster, because of the security breaches that would occur first, after the flaws are discovered but before PTFs are rolled out.

And people have been sharing code for decades...wow, Sandra, github did not invent source code sharing! Heck, even in the somewhat stunted and isolated IBM mainframe world there was (and still is!) the SHARE group and the CBT tapes! Open source software has been the way of computing since there WAS computing. Suits rolling in after the fact and commercializing everything was, and is, still an outlier for many of us. There is, and always has been, far more open source software in the world than closed source.

IBM gave away their OSs at first because they didn't see any intrinsic value in software; they wrote it to sell hardware, and for no other reason. They closed it up when they realized they could make people pay for it, and thus create a new (and huge) profit center. This is a documented and well-known fact.

I'm sorry to be so disagreeable, but you're incorrect on so many levels here that I just can't sugar-coat it. It's nothing personal and of course I mean no disrespect whatsoever; I just have to correct your rather dramatic misconceptions.

-Dave

--
Dave McGuire, AK4HZ
New Kensington, PA


Re: HP8568A with no CONT SWEEP

 

I have seen many HP 8566A/B, 8568/B DAC failures on A16 and A3A8 brds PN 1826-0448. Most failures were low order bits that stuck high or low. A redesign used a newer PN 1826-0668? There was a Service Note that addressed this and a yellow manual change sheet for the manual parts list. The new part is a direct replacement with better reliability. Check for a late version of the 85662A manual to get the exact PN. I may not have remembered the PN correctly, but the last digit is the only one that I may question. It may be the difference in the AD7525 and the AD7533 DAC¡¯s.
Your 85662A (A3A8 brd., A3A8U8?) is sending the EOS signal to the RF section too soon, my guess would be bit 4 is probably stuck high, since the sweep is about 7/8 of normal.
Don Bitters


Even more OT - Digital preservation - Re: [HP-Agilent-Keysight-equipment] OT: 3D modeling software

 

On 2020-09-08 3:32 p.m., Paul Amaranth wrote:
Gotta agree with Dave here. Software can last forever.
Not without extraordinary effort.

Didn't really want to add to an off topic thread, but just preserving
_data_ is a hard problem. Keeping programs buildable and runnable is
even harder.

--T


A1H neon bulb for on/off press switch

 

Anyone know of a European source for the A1H neon bulb used inside the on/off press switches in equipment such as the HP8640B, HP8444A, and probably a host of others?

Thanks, Alan G3XAQ


Re: E4407B J1 serial

 

Cutting model tubing (and hence hard jacket) can also be done with a utility knife and this used to be the common method before plumber's tubing cutters downsized.

Roll the tubing under the blade until the cut encircles the tube, then increase the pressure, continuing to roll, until you cut all the way through. The mechanism is very similar to a tubing cutter but with some practice the pressure is more finely controlled and can avoid deforming the tube.?

This video shows the technique but avoids cutting all the way through by breaking after a line is created. You may not be able to bend the wire sharply enough to do this and have to cut more deeply.



Re: OT: Looking for recommendations on 3D modeling software

 

Gotta agree with Dave here. Software can last forever. I still use a
postscript formatting program that appeared on one of the comp.sources
mailing lists (prior to the invention of the web) and I continue to use
a 30 year version of uemacs that has been heavily modified (actually,
I couldn't give that up, I think it's an extension of my fingers).

There is some language drift over the years that needs attention though.
Perfectly reasonable C code from 30 years ago will likely not compile
with the default options on today's compilers. Some of it may need a
little work.

The advantage of a "dead" project is the interface is not being continuously
tweaked by someone who thinks shuffling the menus and making your relearn the
UI is progress.

Paul

On Tue, Sep 08, 2020 at 01:22:37PM -0400, Dave McGuire wrote:
On 9/8/20 12:55 PM, Sandra Carroll wrote:
Disagree,
Im talking about code out on github or sourceforge that are setup as you describe.
Projects die. I cannot quote the source exactly but where was an article that showed that over 70% if not higher Opensource project die.
I actually think it was like 90% but can not be sure, I know it was high.

Unless a project is widely adopted it will eventually die no mater how good it is.
If you're talking about "projects", sure, they die all the time. But the
subject here is SOFTWARE. And making that assertion about software isn't
just questionable, it's dead wrong, and I prove it every day.
--
Paul Amaranth, GCIH | Manchester MI, USA
Aurora Group of Michigan, LLC | Security, Systems & Software
paul@... | Unix/Linux - We don't do windows


Re: OT: Looking for recommendations on 3D modeling software

 

The EAGLE version only does 3 by 4 inch boards, single sheet, double sided at most.

For my own purposes, too limited.

EAGLE used to be a separate product, but IIRC, is *only* available as an addon to Fusion 360.? More robust versions of Fusion 360/EAGLE are available by subscription only.

Harvey

On 9/8/2020 10:01 AM, Sandra Carroll wrote:
I¡¯m surprised no one has mention fusion360. Full CAD/CAM with Eagle now as well.
3D parametric, direct manufacture to 3D printers. I send to both simplify3D and chitubox all the time.

Easy to use. Still no cost to makers.

On open source
Some comments. I¡¯ve run into countless projects that die or are abandoned in the opensource community. Yeh some of the big stay around but far greater go nowhere.

Opensource is not this great pancea of perfection. If your not a developer yourself you can only hope they¡¯ll accept your proposal for a change. Personal experience is they don¡¯t always do this. In fact in my experience they rarely do. It does not fit the authors vision of how it should work.

I love Perl. But the community refused for the longest time to accept ebcdic(mainframe) into the their world. And only did by making it ascii internally which has its own problems for those of us in the mainframe.

I¡¯m not against opensource, I use it all the time. Like anything it has it¡¯s upside and downside.

Sandra

Sent from my iPhone 7 Plus

On Sep 8, 2020, at 9:29 AM, Chuck Harris <cfharris@...> wrote:

?Bear in mind that one of the features of open source projects
is they really never go away. Commercial projects come and vanish,
and change their licensing terms with great regularity.

OpenSCAD is used by dozens of other projects, and is a very solid
package. The source is available on github, and if you don't like
the direction the authors are going, you can take it and make it
your way. Sure, if you aren't talented that way, you will have to
hire it done, but that is what you are already doing with the outright
commercial packages... without any hope of customization.

If OpenSCAD is too hard to learn (it isn't), you can use one of the
many packages, like FreeCAD, that have incorporated it into their
graphic interfaces.

We greybeards remember the PC so well, that we wrote GNU and linux
for it, and emancipated ourselves from Microsoft.

Educator licenses are available to universities to allow them to
train their kiddies on the package at no cost to the university.

The university professor gives a 1 year copy to each student, and
they use it for their course work. At the end of the year, it is
inactivated.

The companies do that because it is free advertising, and a free
beta testing of their product. They also know that once trained on
a product, students will ask for it where they work.

That is the sole and only reason Apple and Microsoft have such nice
licensing terms for K-12 schools.

Also, to use a student license, usually you are required to show
registration at a university. The rules on student licenses are
highly restrictive relative to commercial intention. A product
designed on a student license cannot ever be commercialized without
transferring it to a full on commercial seat... at typically $50K a
seat... and once there, it can never be brought back to a student
seat.

-Chuck Harris

Tom Gardner wrote:
Overall I doubt that members of this group will want to make anything really complex,
but they might like it to be available to other members in a decade or so. So have a
quick look and choose any tool that feels comfortable without a large learning curve.

After a///very//quick look/, it appears that OnShape is....

Free for "educators", with a 1 year time limit on the licence - whatever that means.

Online only, running in a browser like OpenJSCAD. The standard questions with any
"cloud service" are whether:

* it will be there in 5 years time; see Microsoft PlaysForSure(TM), and giggle
* the licence conditions can be changed, e.g. is the company/product changes ownership

Greybeards will remember the sighs of relief when PCs became available, because it
meant that users' data was not "held hostage" inside silos owned by other companies.



On 08/09/20 02:54, Kuba Ober wrote:
OnShape - as long as it¡¯s not for commercial purposes - all your projects are
publicly viewable then. A joy to use. All it needs is an OK internet connection and
a supported web browser.

FreeCAD is another option.

7 sep. 2020 kl. 10:17 fm skrev victor.silva via groups.io
<daejon1@...>:

?This is off topic but the end result will be for HP products so please bear with me.

I am looking for recommendation on 3D modeling software (preferably freeware) and
a company that I can then send the 3D model to
make a battery holder clamshells. I propose to make half clamshell pieces that
would then make a complete
battery holder by using 2 pieces that would fit together.

Thank you,
Victor


Re: E4407B J1 serial

 

On 9/8/20 11:54 AM, Steve - Home wrote:
Or the OmniSpectra T200-500. I have a couple of those and they¡¯re good.
Seems almost every name brand connector manufacturer also sold tools for their connectors, usually at an exorbitant price, and with dire warnings that performance specifications were only valid if the connector was properly installed, i.e. with their tools.
I¡¯ve also had good luck with the smallest tubing cutters sold in hobby shops For cutting RC airplane fuel lines. Just use it to score the outer conductor and snap it off; carefully cut the ptfe insulation with a sharp razor blade or hobby knife. Don¡¯t use the tubing cutter to cut all the way through the outer conductor as it will roll the inside edge to a slightly smaller diameter and upset the impedance, though probably noticeable only in high precision measurements.
Crap, that'll teach me to read to the end of my mail spool before replying.

So if you can stop the tubing cutter before it goes through the wall, then snap it, that'd probably do the trick. I wonder if a "stop" could be implemented in a standard tubing cutter to prevent excessive cutting depth.

-Dave

--
Dave McGuire, AK4HZ
New Kensington, PA