Digest for sci.electronics.repair@googlegroups.com - 20 updates in 2 topics

sms <scharf.steven@geemail.com>: Dec 27 09:10AM -0800

On 12/26/2018 7:03 PM, arlen holder wrote:
> On Wed, 26 Dec 2018 15:30:14 -0500, nospam wrote:
 
>> nonsense. not only are there equivalents, there are even better options.
 
> Please just name one (link) if that's the case.
 
LOL, you often see inquiries for an iOS app with all the functionality
of Torque Pro. Unfortunately there's no such animal. I don't know why
the author doesn't port it to iOS with the appropriate caveats regarding
which OBD-II dongles will work with the iOS version (you can use Wi-Fi
dongles or BLE dongles, which are six times as expensive, but still not
outrageously priced).
 
https://itunes.apple.com/us/app/engine-link-obd-ii-vehicle/id591557194?mt=8
is rated 2.4 out of 5. They do explain that only certain types of OBD-II
dongles will work.
 
https://play.google.com/store/apps/details?id=org.prowl.torque&hl=en_US
is rated 4.5 out of 5. It just has a lot more functionality.
 
Still puzzled as to why the Bluetooth SPP profile was left out of iOS.
No one has ever had a good answer to that.
nospam <nospam@nospam.invalid>: Dec 27 12:27PM -0500

In article <q03127$qp3$1@dont-email.me>, sms
 
> > Please just name one (link) if that's the case.
 
> LOL, you often see inquiries for an iOS app with all the functionality
> of Torque Pro. Unfortunately there's no such animal.
 
no, you don't 'often see inquiries' and there definitely are such apps
on ios.
 
> I don't know why
> the author doesn't port it to iOS
 
because he doesn't have the resources and/or skills to develop and
support two apps on two different platforms. or, he's simply not
interested.
 
> which OBD-II dongles will work with the iOS version (you can use Wi-Fi
> dongles or BLE dongles, which are six times as expensive, but still not
> outrageously priced).
 
nonsense.
 
they're about the same price, maybe a couple of bucks more for a
bluetooth le version, which is also much easier to set up and use than
bluetooth classic.
 
the wifi adapters are more expensive, however, they are intended for
use with something that doesn't have bluetooth, such as most windows
laptops (all mac laptops have bluetooth le and classic).
 
> Still puzzled as to why the Bluetooth SPP profile was left out of iOS.
> No one has ever had a good answer to that.
 
plenty of people have.
 
the answer is simple: spp is obsolete, having been replaced by the far
more capable bluetooth le.
 
writing apps to use le is *very* easy. not so with spp.
arlen holder <arlen@arlen.com>: Dec 27 07:04PM

On Thu, 27 Dec 2018 12:27:06 -0500, nospam wrote:
 
> no, you don't 'often see inquiries' and there definitely are such apps
> on ios.
 
Hi nospam,
Doesn't it strike you as odd that you make claim after claim after claim,
over the years, and _none_ of your claims ever turns out to be true?
 
Meanwhile, sms and I make claims, which we back up with cites.
 
It doesn't strike you as odd that you don't act like a normal adult does?
 
> because he doesn't have the resources and/or skills to develop and
> support two apps on two different platforms. or, he's simply not
> interested.
 
Or it can't be done on iOS the way he wants it done (e.g., Bluetooth SPP),
or he doesn't want to put up with Apple's bullshit, or ... whatever
conjecture you want to devise.
 
What's odd about you nospam is that you can never speak on facts.
 
The fact is that the functionality sms speaks of doesn't exist on iOS, and
all your denials of that obvious fact don't change that obvious fact.
 
> they're about the same price, maybe a couple of bucks more for a
> bluetooth le version, which is also much easier to set up and use than
> bluetooth classic.
 
The last time you made similar idiotic fact-free claims was when you
claimed there was functionality for a buck that turned out to be yet
another baseless claim by you nospam, to add to the heap of baseless
claims.
o Name a single iOS app functionality that you can get for a buck, that isn't already on Android, for free
<https://groups.google.com/forum/#!msg/misc.phone.mobile.iphone/aUyeuaPI9pc/KHQx-ecNBAAJ>
 
Your credibility, nospam, is worse than that of the monkey.
 
> the answer is simple: spp is obsolete, having been replaced by the far
> more capable bluetooth le.
 
You Apple Apologists, nospam, always makes myriad excuses for the limited
functionality of iOS versus Android.
 
It's why we summarized the Apple/Android delta, accurately, as:
o Hardware (about the same, Apple slightly less functional in general)
o Apps (about the same for Mom & Pop - not even close for power users)
o Storage (a completely different paradigm - no way to compare logically)
<https://groups.google.com/d/msg/comp.mobile.ipad/ahrT3Qpy_aE/cjFcFbxZDAAJ>
nospam <nospam@nospam.invalid>: Dec 27 04:47PM -0500

In article <q037nr$6ru$1@news.mixmin.net>, arlen holder
 
> Or it can't be done on iOS the way he wants it done (e.g., Bluetooth SPP),
> or he doesn't want to put up with Apple's bullshit, or ... whatever
> conjecture you want to devise.
 
bluetooth le is not 'apple's bullshit'.
 
bluetooth le, aka bluetooth 4, replaces bluetooth classic (v3 and
earlier) for almost everything. spp is *obsolete*.
 
it's *easier* to write apps using btle (i've done it; you have not, nor
has sms) and it does a *lot* more than spp could ever possibly do.
arlen holder <arlen@holder.com>: Dec 28 12:54AM

On Thu, 27 Dec 2018 16:47:14 -0500, nospam wrote:
 
> it's *easier* to write apps using btle (i've done it; you have not, nor
> has sms) and it does a *lot* more than spp could ever possibly do.
 
*The only people who believe _anything_ you say, nospam, are Apologists.*
 
FACTS
 
The fact is that the OBD functionality sms speaks of, is, based on what is
said in this thread by reliable people (i.e., not you, nospam), does not
exist on iOS.
 
This apparent lack of OBD functionality seems that it might be very similar
to the known lack of TOR functionality on iOS, where, in the case of TOR,
there are no sanctioned apps by the Guardian Project, but only "suggested"
third-best alternatives (where the Guardian Project explains that iOS simply
utterly lacks in the necessary API functionality).
<https://www.torproject.org/docs/faq.html.en>
<https://guardianproject.info/apps/orweb/>
 
Those two cases may be different from the myriad other cases of utter lack
of functionality on iOS (e.g., there is no ability to graph wifi signal
strength over time, no torrenting, no automatic call recording, no app
launchers, no second source for apps, etc.).
 
Why does iOS _always_ prove to lack basic app functionality?
I don't know why.
It just always does.
 
I'm not saying I know all the reasons that iOS lacks app functionality.
 
I am just saying that there are so very many cases where iOS lacks app
functionality that Android has had for years, that your assertions always
ring hollow that apps on iOS can even *approach* that which they do on
Android.
 
In this situation, sms is more trustworthy - as you are not.
(Your record on trust is worse than that of a liar & politician & salesman.)
 
Why you _always_ lie, nospam, is beyond me - since you gain nothing.
It's a habit you need to kick - since you have zero credibility.
 
*The only people who believe _anything_ you say, nospam, are Apologists.*
nospam <nospam@nospam.invalid>: Dec 27 08:22PM -0500

In article <q03s8p$ebv$1@news.mixmin.net>, arlen holder
 
> The fact is that the OBD functionality sms speaks of, is, based on what is
> said in this thread by reliable people (i.e., not you, nospam), does not
> exist on iOS.
 
that's not a fact at all. it's pure rubbish.
 
the obd functionality is entirely within the obd device that plugs into
the vehicle's obd port.
 
that device reads assorted info from the vehicle and sends it via
bluetooth to an ios or android device. there are also models that use
wifi or usb, usually to be used with a laptop, as most windows laptops
do not have bluetooth built in (macs do).
 
there is *no* limitation on what can be done with that data, other than
the skill of the app developer writing the app and how much effort they
wish to expend in doing so.
 
i've written *several* apps that use obd and bluetooth. you have not,
nor has sms.
rbowman <bowman@montana.com>: Dec 27 09:18PM -0700

On 12/27/2018 10:10 AM, sms wrote:
> which OBD-II dongles will work with the iOS version (you can use Wi-Fi
> dongles or BLE dongles, which are six times as expensive, but still not
> outrageously priced).
 
Mostly because iOS is a pain in the ass. We develop apps for Android and
may do iOS someday using Xamarin, but it isn't a high priority.
nospam <nospam@nospam.invalid>: Dec 27 11:27PM -0500

In article <g8lmd8F8o87U1@mid.individual.net>, rbowman
 
> Mostly because iOS is a pain in the ass. We develop apps for Android and
> may do iOS someday using Xamarin, but it isn't a high priority.
 
if you don't develop for ios, you're not in a position to comment about
ios being a 'pain in the ass', and if you're using xamarin for app
development, you're even less in a position to comment.
 
i've done native app development for both ios and android, and ios is
*much* easier.
sms <scharf.steven@geemail.com>: Dec 28 04:53AM -0800

On 12/27/2018 8:18 PM, rbowman wrote:
>> outrageously priced).
 
> Mostly because iOS is a pain in the ass. We develop apps for Android and
> may do iOS someday using Xamarin, but it isn't a high priority.
 
Understood, but for a paid app, that is extremely popular, with
>1,000,00 installs and >55,000 reviews, you'd think that the pain might
be worth it for the author. Especially because you often see people
asking "is there an equivalent app to Torque Pro for the iPhone?" Even
prior to BLE, there were Wi-Fi OBD-II dongles being used with OBD-II iOS
apps (which were a pain because you could only have one Wi-Fi connection
at a time from a phone, but still usable for diagnostics, just not
continuous monitoring). Developing for BLE is more difficult than using
Bluetooth SPP, but not magnitudes more difficult.
nospam <nospam@nospam.invalid>: Dec 28 10:00AM -0500

In article <q056c2$rsc$1@dont-email.me>, sms
 
> Understood, but for a paid app, that is extremely popular, with
> >1,000,00 installs and >55,000 reviews, you'd think that the pain might
> be worth it for the author.
 
nope. if it's only one person, his hands are full with that one app.
 
developing for and supporting two different platforms is a lot more
work than just one and it's hard to do both well.
 
> Especially because you often see people
> asking "is there an equivalent app to Torque Pro for the iPhone?"
 
nope, but for those that do ask, the answer is overwhelmingly 'yes'.
 
> apps (which were a pain because you could only have one Wi-Fi connection
> at a time from a phone, but still usable for diagnostics, just not
> continuous monitoring).
 
false. it works quite well for continuous monitoring, but the main
intent of a wifi dongle was for laptop use.
 
> Developing for BLE is more difficult than using
> Bluetooth SPP, but not magnitudes more difficult.
 
nonsense. developing for bluetooth le is *significantly* easier for a
number reasons. i've done both. you have not.
 
stop making up shit.
rbowman <bowman@montana.com>: Dec 28 08:09AM -0700

On 12/27/2018 09:27 PM, nospam wrote:
> development, you're even less in a position to comment.
 
> i've done native app development for both ios and android, and ios is
> *much* easier.
 
Yeah, you've made it abundantly clear that you're an Apple fanboi.
Personally, I've had one Apple product in my life -- a Shuffle someone
gave me. It isn't bad but itunes sucks.
 
I'm a hired gun so I would have worked on Apple stuff if anyone ever
wanted to pay me to do so, but they never did.
rbowman <bowman@montana.com>: Dec 28 08:22AM -0700

On 12/28/2018 05:53 AM, sms wrote:
>>1,000,00 installs and >55,000 reviews, you'd think that the pain might
> be worth it for the author. Especially because you often see people
> asking "is there an equivalent app to Torque Pro for the iPhone?"
 
Maybe, if a million iPhone users were asking for it... Buying the Apple
hardware to develop on, learning the new toolchain, and dealing with the
Apple store puts a little bump in the road. For Android you download
Android Studio to your Windows box, pick up a cheap Android device, and
you're good to go. I just bought a 7" B&N Nook for $50. It's no
powerhouse but it's acceptable. Apple might be trimming prices a bit but
they're not there yet.
nospam <nospam@nospam.invalid>: Dec 28 10:42AM -0500

In article <g8msjgFgl59U1@mid.individual.net>, rbowman
 
> > i've done native app development for both ios and android, and ios is
> > *much* easier.
 
> Yeah, you've made it abundantly clear that you're an Apple fanboi.
 
ad hominem.
 
two can play that game: you've made it abundantly clear that you're an
apple hater fueled by myths.
 
> Personally, I've had one Apple product in my life -- a Shuffle someone
> gave me. It isn't bad but itunes sucks.
 
then you're even less in a position to comment.
 
> I'm a hired gun so I would have worked on Apple stuff if anyone ever
> wanted to pay me to do so, but they never did.
 
you're asking the wrong people. there's a *huge* demand for apple
development and it pays *quite* well.
nospam <nospam@nospam.invalid>: Dec 28 10:42AM -0500

In article <g8mtapFgptgU1@mid.individual.net>, rbowman
 
> Maybe, if a million iPhone users were asking for it... Buying the Apple
> hardware to develop on, learning the new toolchain, and dealing with the
> Apple store puts a little bump in the road.
 
not at all. write a decent app and you'll recover any costs many times
over. there's nothing to deal with the app store either. when the app
is done, submit it.
 
> For Android you download
> Android Studio to your Windows box, pick up a cheap Android device, and
> you're good to go.
 
same for ios.
 
xcode is free and pick up a cheap iphone for testing. done. and if
you're *that* cheap (and not interested in quality of work), use the
simulator and let your beta testers test on actual hardware.
 
> I just bought a 7" B&N Nook for $50. It's no
> powerhouse but it's acceptable. Apple might be trimming prices a bit but
> they're not there yet.
 
a b&n nook is in no way comparable to an iphone or ipad.
tubeguy@myshop.com: Dec 27 09:11PM -0600

Whats the difference between Magnetic & Crystal headphones?
 
I have an old tube tester which has a jack labeled "NOISE"
I downloaded a manual for it and it says that is to hear noisy tubes.
Then it says use MAGNETIC headphones, crystal headphones will NOT work.
 
I wont likely ever use this function, but I am curious......
 
My guess would be "magnetic" phones would have something like a speaker
in them, and that all modern phones are made this way. (just a guess).
 
So what is a crystal headphone and how does that work?
tabbypurr@gmail.com: Dec 27 07:33PM -0800


> My guess would be "magnetic" phones would have something like a speaker
> in them, and that all modern phones are made this way. (just a guess).
 
> So what is a crystal headphone and how does that work?
 
magnetic are either moving coil or moving iron. Google can soon explain how piezos & crystal earpieces work.
 
 
NT
whit3rd <whit3rd@gmail.com>: Dec 27 10:04PM -0800

> Whats the difference between Magnetic & Crystal headphones?
 
Magnetic headphones (like most earbuds) are low-impedance and have DC
conductivity. Crystal headphones are high impedance (and are capacitive,
kind of like a capacitor microphone in reverse), so have NO DC conductivity.
The likely reason to use magnetic is that a DC path to ground is required
to correctly bias some amplifier stage.
 
Absent a DC path to ground, some tube-type equipment outputs hundreds of
volts, could be hazardous.
tabbypurr@gmail.com: Dec 28 04:01AM -0800

On Friday, 28 December 2018 06:04:14 UTC, whit3rd wrote:
> to correctly bias some amplifier stage.
 
> Absent a DC path to ground, some tube-type equipment outputs hundreds of
> volts, could be hazardous.
 
Moving iron headphones were originally in the 1-8k ohm range, modern ones mostly 32 ohms. Crystals are odrers of magnitude higher impedance, much greater efficiency & dire sound quality. A DC path can be added using a resistor or choke.
 
 
NT
Look165 <look165@numericable.fr>: Dec 28 01:34PM +0100

One works with electromagnetic force, the other works with piezoelectric
force.
 
The first is low impedance and good for low frequencies, it uses current.
The other is high impedance and good for high frequencies, it uses voltage.
 
With a typical 8-Ohm or 32-Ohm output, the crystal headphone is useless.
 
"pfjw@aol.com" <peterwieck33@gmail.com>: Dec 28 05:39AM -0800

http://www.circuitstoday.com/wp-content/uploads/2011/11/PiezoTransducer-Circuit-Symbol.jpg
 
http://www.circuitstoday.com/wp-content/uploads/2011/11/Loudspeaker-Circuit-Symbol.jpg
 
I have generally found it useful to give a picture along with an explanation - it makes the jargon more grounded, pun intended.
 
Top picture is a Piezo (crystal) transducer symbol. In the simplest of terms, bend a crystal, it will emit electricity. Apply electricity to a crystal, it will bend. But, as you may see from the symbol, there is no direct connection between the two poles of the transducer.
 
A magnetic speaker, whether PM or Field Coil uses a voice-coil that is moved by changing AC voltages applied to the voice-coil. So the two poles are directly connected via the voice-coil. Yes, there is DC continuity - and as a rule, magnetic speakers do not like DC.
 
That the tube tester wants magnetic headphones indicates that it is a low current output device. Given that most tube testers - pretty much a done-deal after the 60s by way of design improvements - have no formal amplification built in, a magnetic headphone makes more sense. What the "Noise Tester" is measuring is a sample from the anode load resistor and amplifying the output to a speaker (or eye tube) - depending on the manufacturer.
 
Some testers have settings for this test that more resemble actual operating conditions, rather than "full throttle current" as typically done for life-test.
 
The above few lines from "sample" through "Life-test" are quotes.
 
http://www.john-a-harper.com/tubes201/#Noise
 
However, there are all kinds of noise - usually in very small values.
 
Peter Wieck
Melrose Park, PA
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to sci.electronics.repair+unsubscribe@googlegroups.com.

No Response to "Digest for sci.electronics.repair@googlegroups.com - 20 updates in 2 topics"

Post a Comment