OBD2 is predominantly based on the SAE J1939 application-layer protocol, and the Controller Area Network (CAN) bus. Whilst J1939 specifies the cyclic transmission of ECU identification information, in no part of the as-implemented OBD2 specification is there provision for antennae to 'broadcast VIN, speed' etc.
Try grabbing yourself a copy of the specification - it's available from SAE and ISO. The prurient specifications are ISO 15765 for the modern set of diagnostics (UDS), along with SAE's J1939 specification, of which you'll likely want Part 71, the application-layer diagnostics.
I'd be curious to see what sort of authentication the networks are pushing for this sort of broadcast message - will third parties be able to forge the sender phone number/name?
I frequently receive spam on my mobile by SMS and "service messages" (SMS with integrated hyperlinks) which purport to be from a textual name rather than a sender telephone number.
Given the propensity for telco networks to be less than secure with regards to CNI information, I'd hope that tighter restrictions on sender CNI in SMS is adopted if this plan goes ahead - with the level of sheeple out there, a targeted social engineering attack against a public event could cause chaos. Take, for example, the WVU emergency alert system mentioned in another comment - if someone were to forge a message about a school shooting to a decent number of students, I could quite easily see the day's classes being disrupted. Extrapolate that to a national warning system.. and there's a lot to be done before I'd trust a SMS coming in from "Federal Warning System" regarding a serious incident.
I'm just viewing this from the outside (as the OP said, I only had to deal with US telcos as a tourist for a couple of months), but it seems to me that the US carriers in particular tend to have more of a say in how the phone firmware functionality is specified - i.e. the contentious practice of disabling Bluetooth/USB functionality in favour of OTA transfer methods (read: $$), and I had assumed that similar practice would carry through to other parts of the product.
It seems from the wording in TFA that Verizon chose to implement the directive by acting in this manner; whilst it may be the default for the phone(s) in question, the article does make out like the telco enforces this behaviour to comply with the FCC directive.
Absolutely. You've just got to wonder what sort of idiot did the requirements analysis for this sort of functionality.
I mean, sure, companies try to cover their arse from the FCC.. but wouldn't an ordinary person think "hang on.. we might be sued if the alarm goes off when a violent intruder hears a customer calling 911!"? I'd go as far to say it's beyond borderline criminal, it's outright malicious.
Seriously.. are there/any/ mobile telcos in the US that don't suck in one way or another? I hated dealing with them for a month as a tourist, let alone for any longer period.
Australia.. whilst is certainly a common word over here. Provided you avoid the under-25 crowd.
And to keep it on topic.. 3G is certainly commonplace in urban settings here, as is HSDPA. If you're willing to pay an exorbitant amount, you can get HSDPA in the bush via Telstra's UMTS850 network.. but it's not cheap by any measure.
EDGE smedge. Try using HSDPA.. it royally kicks the arse out of EDGE or UMTS. Downloading at 3mbps whilst in a train at 80km/h.. I don't think that comes anywhere close to the "user experience" of EDGE.
The article doesn't cite/any/ real-world statistics to back up the arguments.. sounds like a load of iHype to me.
The 64-bit designation refers to the width of the address bus*. For example, IA-32 processors have been able to handle 64 bit integers for ages.. so a 64-bit address-capable processor handling 128 bit numbers is nothing new.
* Yes, PAE was a slight deviation from a 32 bit address space, but in userspace, it's 32 bit flat memory.
I'm in Australia, and we've got a national healthcare system, (Medicare, which operates in parallel with the private health system.
Essentially, those earning over $50k (IIRC) are taxed an additional 1% for healthcare. Medication on the PBS is subsidised by the government (A$3.50 for low-income individuals, $22 for everyone else), and covers most everyday prescription medication. As for general practitioners, "bulk billing" is the tagline that refers to doctors that bill directly to Medicare (read: $0 out of pocket), which is approx. $30 from the government for each consultation. Unfortunately, there's a trend lately towards not taking on any new bulk-billing patients with the current shortage of general practitioners.
On the whole though, it's a pretty fair system - I recently had a cholecystectomy, and had approx. $200 out of pocket charges.. $100 for the x-ray, and $100 for the specialist consultation. The surgery itself is free in public hospitals, and I only had to wait about 3 weeks.
The private health system operates their own hospitals; costs start at about $400-500/year for individuals... but I'll let someone else cover that. Or Google.
Software engineering is not art as a whole, but there are facets where the decomposition and implementation of a software system can be viewed as an artform. Personally, my view is that it is seen as an art not only because of the creative aspect of programming (algorithm design or selection), but also due to the lack of maturity of the software engineering industry.
Industries such as Civil Engineering have had centuries of refinement, whereas the SE industry is relatively young, only really developing in the last half-century. We haven't had the same amount of time to derive generic methods to decompose systems, and as a whole, the industry acts as a set of disconnected islands - predominantly, not sharing information or practices.
In the last couple of decades, there have been forward strides made with regards to identifying patterns and other generic, reusable software engineering assets, but the overall industry is still immature. In addition, the diversity of projects leads to a higher degree of perceived (and perhaps, actual) complexity - to take a Civil Eng analogy, one day we (Software Engineers) are building bridges, the next we'll be building a space elevator, and the day after, constructing a skyscraper.
My personal belief is that it's a matter of time before software engineering as an industry matures, and before that occurs, the degree of sharing and derivation of generic, reusable software components needs to increase rapidly.
Not since the place got over-run with a chorus of ninnies whining "I don't understaaaaand! Software should just wooooork!"
That's all well and good, but there's still a subset of us who are interested. I certainly don't go and bitch about Amiga articles because they're there.. but, that's the Internet. Someone's gotta complain, especially if it's free.
Looks like yet another slashvertisment for an upcoming book/conference.
It's a nice start, but lacking any real depth - the article could be summarised in one or two sentences, listing a number of good and bad practices. I know it's stripping people of their $DEITY-given right to derive fiduciary advantage from relaying information and opinion, but can we please have some/real/ in-depth software engineering articles for once in a while?
I'd buy one except that it's ancient, GSM-technology-wise: It doesn't do EDGE, UMTS or HSDPA. Which rules out 90% of what I (and many developers would) use the handset for - connectivity to data networks, for example, SSH sessions at any decent speed/latency.
It's a bloody good start. But it's got a long way to go.
I'd like to put my 2c worth of counterexamples for this. I was diagnosed with gall stones earlier this year.. ended up having an operation to have my gall bladder removed. Total out-of-pocket cost for specialist visits plus surgery (i.e. everything) was about AUD$200. Only had to wait a month in the public system.
If you wouldn't be happy in the.net job, don't take it. Unless you're in serious debt, it's better to go for the job you'd be happier in. Personally, I'd set the limit at a minimum of a 35% increase (as opposed to 66%) for the Perl job.
Do what makes you happy. It'll pay off in the long-run, and you typically gain more contacts that way for future jobs.
How is this a bad thing though, if said components are written well? While well-written external components are often a gamble as to how well they integrate with existing systems, or how well they work, sufficiently stable and generic components can be leveraged to create systems in much less time than writing from the ground up. Isn't this what the last 20-30 years of the push towards software engineering has been emphasising - encapsulation, reuse and lack of rework?
The one problem with this, as mentioned in the parent comment, is the multitude of systems, languages and frameworks that exist, and developers are expected to understand. Businesses (where appropriate) should standardise upon a limited number of these frameworks and languages, and go from there. There's a fine balance between time spent learning others' code, and gluing said code together to meet internal business needs. Finding that balance is not necessarily a task for developers at the coalface, but instead one for capable IT management to work with both their internal teams, and others in the business, to decide. We've all had to put up with stupid decisions in the workforce (if you haven't, you haven't been working long enough), and it's very rare that a middle-to-large sized company 'gets it'.
I've been using Campfire as part of a group project. Initially I was against the idea.. but it's become useful, in that there's also logs of prior entries. About as close to a cross of chat and message board that's practical..
Slashdot Mirror
That's bullshit.
OBD2 is predominantly based on the SAE J1939 application-layer protocol, and the Controller Area Network (CAN) bus. Whilst J1939 specifies the cyclic transmission of ECU identification information, in no part of the as-implemented OBD2 specification is there provision for antennae to 'broadcast VIN, speed' etc.
Try grabbing yourself a copy of the specification - it's available from SAE and ISO. The prurient specifications are ISO 15765 for the modern set of diagnostics (UDS), along with SAE's J1939 specification, of which you'll likely want Part 71, the application-layer diagnostics.
Enough with the tin-foil-hat crap.
I'd be curious to see what sort of authentication the networks are pushing for this sort of broadcast message - will third parties be able to forge the sender phone number/name?
I frequently receive spam on my mobile by SMS and "service messages" (SMS with integrated hyperlinks) which purport to be from a textual name rather than a sender telephone number.
Given the propensity for telco networks to be less than secure with regards to CNI information, I'd hope that tighter restrictions on sender CNI in SMS is adopted if this plan goes ahead - with the level of sheeple out there, a targeted social engineering attack against a public event could cause chaos. Take, for example, the WVU emergency alert system mentioned in another comment - if someone were to forge a message about a school shooting to a decent number of students, I could quite easily see the day's classes being disrupted. Extrapolate that to a national warning system.. and there's a lot to be done before I'd trust a SMS coming in from "Federal Warning System" regarding a serious incident.
I'm just viewing this from the outside (as the OP said, I only had to deal with US telcos as a tourist for a couple of months), but it seems to me that the US carriers in particular tend to have more of a say in how the phone firmware functionality is specified - i.e. the contentious practice of disabling Bluetooth/USB functionality in favour of OTA transfer methods (read: $$), and I had assumed that similar practice would carry through to other parts of the product.
It seems from the wording in TFA that Verizon chose to implement the directive by acting in this manner; whilst it may be the default for the phone(s) in question, the article does make out like the telco enforces this behaviour to comply with the FCC directive.
Absolutely. You've just got to wonder what sort of idiot did the requirements analysis for this sort of functionality.
I mean, sure, companies try to cover their arse from the FCC.. but wouldn't an ordinary person think "hang on.. we might be sued if the alarm goes off when a violent intruder hears a customer calling 911!"? I'd go as far to say it's beyond borderline criminal, it's outright malicious.
There's her problem. She's using Verizon.
/any/ mobile telcos in the US that don't suck in one way or another? I hated dealing with them for a month as a tourist, let alone for any longer period.
Seriously.. are there
Anywhere that's not the USA, pretty much. (read: GSM-using countries)
And as for the NIC..
USB: http://www.huawei.com/mobileweb/en/products/view.do?id=282
Expresscard: http://www.huawei.com/mobileweb/en/products/view.do?id=780
PCMCIA: http://www.huawei.com/mobileweb/en/products/view.do?id=145
And that's just one manufacturer. I'm sure you can find miniPCI versions around. UMTS is bloody good.. but expensive.
Australia.. whilst is certainly a common word over here. Provided you avoid the under-25 crowd.
And to keep it on topic.. 3G is certainly commonplace in urban settings here, as is HSDPA. If you're willing to pay an exorbitant amount, you can get HSDPA in the bush via Telstra's UMTS850 network.. but it's not cheap by any measure.
EDGE smedge. Try using HSDPA.. it royally kicks the arse out of EDGE or UMTS. Downloading at 3mbps whilst in a train at 80km/h.. I don't think that comes anywhere close to the "user experience" of EDGE.
/any/ real-world statistics to back up the arguments.. sounds like a load of iHype to me.
The article doesn't cite
The Shannon limit still applies. It's not a solution to all the problems of RF signalling..
The 64-bit designation refers to the width of the address bus*. For example, IA-32 processors have been able to handle 64 bit integers for ages.. so a 64-bit address-capable processor handling 128 bit numbers is nothing new.
* Yes, PAE was a slight deviation from a 32 bit address space, but in userspace, it's 32 bit flat memory.
I'm in Australia, and we've got a national healthcare system, (Medicare, which operates in parallel with the private health system.
Essentially, those earning over $50k (IIRC) are taxed an additional 1% for healthcare. Medication on the PBS is subsidised by the government (A$3.50 for low-income individuals, $22 for everyone else), and covers most everyday prescription medication. As for general practitioners, "bulk billing" is the tagline that refers to doctors that bill directly to Medicare (read: $0 out of pocket), which is approx. $30 from the government for each consultation. Unfortunately, there's a trend lately towards not taking on any new bulk-billing patients with the current shortage of general practitioners.
On the whole though, it's a pretty fair system - I recently had a cholecystectomy, and had approx. $200 out of pocket charges.. $100 for the x-ray, and $100 for the specialist consultation. The surgery itself is free in public hospitals, and I only had to wait about 3 weeks.
The private health system operates their own hospitals; costs start at about $400-500/year for individuals... but I'll let someone else cover that. Or Google.
Software engineering is not art as a whole, but there are facets where the decomposition and implementation of a software system can be viewed as an artform. Personally, my view is that it is seen as an art not only because of the creative aspect of programming (algorithm design or selection), but also due to the lack of maturity of the software engineering industry.
Industries such as Civil Engineering have had centuries of refinement, whereas the SE industry is relatively young, only really developing in the last half-century. We haven't had the same amount of time to derive generic methods to decompose systems, and as a whole, the industry acts as a set of disconnected islands - predominantly, not sharing information or practices.
In the last couple of decades, there have been forward strides made with regards to identifying patterns and other generic, reusable software engineering assets, but the overall industry is still immature. In addition, the diversity of projects leads to a higher degree of perceived (and perhaps, actual) complexity - to take a Civil Eng analogy, one day we (Software Engineers) are building bridges, the next we'll be building a space elevator, and the day after, constructing a skyscraper.
My personal belief is that it's a matter of time before software engineering as an industry matures, and before that occurs, the degree of sharing and derivation of generic, reusable software components needs to increase rapidly.
That's all well and good, but there's still a subset of us who are interested. I certainly don't go and bitch about Amiga articles because they're there.. but, that's the Internet. Someone's gotta complain, especially if it's free.
Looks like yet another slashvertisment for an upcoming book/conference.
/real/ in-depth software engineering articles for once in a while?
It's a nice start, but lacking any real depth - the article could be summarised in one or two sentences, listing a number of good and bad practices. I know it's stripping people of their $DEITY-given right to derive fiduciary advantage from relaying information and opinion, but can we please have some
I'd buy one except that it's ancient, GSM-technology-wise: It doesn't do EDGE, UMTS or HSDPA. Which rules out 90% of what I (and many developers would) use the handset for - connectivity to data networks, for example, SSH sessions at any decent speed/latency.
It's a bloody good start. But it's got a long way to go.
Ding dong, the witch is dead..
I'd like to put my 2c worth of counterexamples for this. I was diagnosed with gall stones earlier this year.. ended up having an operation to have my gall bladder removed. Total out-of-pocket cost for specialist visits plus surgery (i.e. everything) was about AUD$200. Only had to wait a month in the public system.
Anyone could have made the mistake.. good to keep us all in the loop though :)
And let this be a reminder to the kids - RTFM, twice!
If you wouldn't be happy in the .net job, don't take it. Unless you're in serious debt, it's better to go for the job you'd be happier in. Personally, I'd set the limit at a minimum of a 35% increase (as opposed to 66%) for the Perl job.
Do what makes you happy. It'll pay off in the long-run, and you typically gain more contacts that way for future jobs.
Yeah, Christmas Island's NIC has had something of an interesting past.. yay for phonetics!
It doesn't exist!
How is this a bad thing though, if said components are written well? While well-written external components are often a gamble as to how well they integrate with existing systems, or how well they work, sufficiently stable and generic components can be leveraged to create systems in much less time than writing from the ground up. Isn't this what the last 20-30 years of the push towards software engineering has been emphasising - encapsulation, reuse and lack of rework?
The one problem with this, as mentioned in the parent comment, is the multitude of systems, languages and frameworks that exist, and developers are expected to understand. Businesses (where appropriate) should standardise upon a limited number of these frameworks and languages, and go from there. There's a fine balance between time spent learning others' code, and gluing said code together to meet internal business needs. Finding that balance is not necessarily a task for developers at the coalface, but instead one for capable IT management to work with both their internal teams, and others in the business, to decide. We've all had to put up with stupid decisions in the workforce (if you haven't, you haven't been working long enough), and it's very rare that a middle-to-large sized company 'gets it'.
Nor I. I wouldn't trust it with anything even barely private. Which is precisely why I didn't care about discussing a uni project there :)
I've been using Campfire as part of a group project. Initially I was against the idea.. but it's become useful, in that there's also logs of prior entries. About as close to a cross of chat and message board that's practical..
Absolute insanity... although, I guess this proves that Voodoo cards aren't just legacy hardware.. they're supported..