What PID's/ SID's/FID's are

[Ralph L. Fullenwider]

Hello everyone:

For those who are not familiar with codes, multiplexing or other forms of
reporting used in this day and age, I will attempt to bring to light a
little about these systems in the later Coaches.

The reporting codes and information are inputs and outputs much like on the
computer you are using for the Forum. And each code is simply an address of
where in a computer, the information is stored. So in order to get a
readout for that code, you have to have the input/output (I/O) schedule for
the addresses.

Though we see the codes reported in decimal (number) form, the actual
addresses are usually programmed in Hex or Octal or even machine coding,
then converted to binary and finally to numbers. In doing this, one wire
can be used to send a signal out on and to report back on several addresses
depending on the speed of the polling process.

The reason for the software, readers and so forth is to convert these
multiplexed addresses to a form that we can attach a number to and have a
readout of what code or instruction is in that address.

The codes are usually preset with a read out of what it is. Example: A
polling takes place sending out a question to a certain address, then if no
flags are set nothing comes back. But if an address, such as the DDEC
address for Low coolant is polled and a flag set, it sends back a number of
13. Then you look up the code on the map and it tells you, code 13 is
coolant level sensor low, add coolant and the flag goes off satisfied.

This is much simplified, to be sure, but the general idea comes across.
Easy huh? Hope this helps a little for those wondering what people are
talking about in some of the posts.

Safe travels,

Ralph and Charolette Fullenwider
84FC35
Ralph's RV Solutions, Duncan, Oklahoma

[Gregory OConnor]

Ralph, It may just be my nature but; I dont believe that all the
digital equipment is worth the worry. When I get a check engine
light; I check the engine. If the heat goes up; I back off the
demand. I have driven a good 400,000 on used class 8 diesel trucks
with as much as 700,000 miles on the clocks. Things do not often go
wrong and when they do:
1- it showes up in water/ oil heat and or performance
or
2-too late even while you watch a PC


digital stuff I see as more of a hobby.

GregoryO'Connor
94ptRomolandCA

--- In WanderlodgeForum@yahoogroups.com, "Ralph L. Fullenwider"
wrote:
>
> Hello everyone:
>
> For those who are not familiar with codes, multiplexing or other
forms of
> reporting used in this day and age, I will attempt to bring to
light a
> little about these systems in the later Coaches.
>
> The reporting codes and information are inputs and outputs much
like on the
> computer you are using for the Forum. And each code is simply an
address of
> where in a computer, the information is stored. So in order to get
a
> readout for that code, you have to have the input/output (I/O)
schedule for
> the addresses.
>
> Though we see the codes reported in decimal (number) form, the
actual
> addresses are usually programmed in Hex or Octal or even machine
coding,
> then converted to binary and finally to numbers. In doing this,
one wire
> can be used to send a signal out on and to report back on several
addresses
> depending on the speed of the polling process.
>
> The reason for the software, readers and so forth is to convert
these
> multiplexed addresses to a form that we can attach a number to and
have a
> readout of what code or instruction is in that address.
>
> The codes are usually preset with a read out of what it is.
Example: A
> polling takes place sending out a question to a certain address,
then if no
> flags are set nothing comes back. But if an address, such as the
DDEC
> address for Low coolant is polled and a flag set, it sends back a
number of
> 13. Then you look up the code on the map and it tells you, code 13
is
> coolant level sensor low, add coolant and the flag goes off
satisfied.
>
> This is much simplified, to be sure, but the general idea comes
across.
> Easy huh? Hope this helps a little for those wondering what people
are
> talking about in some of the posts.
>
> Safe travels,
>
> Ralph and Charolette Fullenwider
> 84FC35
> Ralph's RV Solutions, Duncan, Oklahoma
>

[Leroy Eckert]

Greg: You are 100% correct about the engine data program and the Hobby element,
and I personally don't need a cell phone, in motion satellite TV, remote control
HD flat screen, iPod, Two way radio, GPS, DVD, PSP, MP3, high speed cable
internet, Xbox, VMSpc, Bluetooth, PC wireless laptop, WiFi, Broadband, Federal
Income tax, State income tax, SUI, FUI, LUI, or even a Bluebird WB-40. That is a
lot of @#$%. Beer is good!

Except for the taxes, this day and age, the above make life a little more
comfortable wouldn't you say?

Leroy Eckert
1990 WB-40 "Smoke N Mirrors"
Niceville, FL





----- Original Message -----
From: Gregory OConnor
To: WanderlodgeForum@yahoogroups.com
Sent: Tuesday, February 06, 2007 2:06 PM
Subject: [WanderlodgeForum] Re: What PID's/ SID's/FID's are


Ralph, It may just be my nature but; I dont believe that all the
digital equipment is worth the worry. When I get a check engine
light; I check the engine. If the heat goes up; I back off the
demand. I have driven a good 400,000 on used class 8 diesel trucks
with as much as 700,000 miles on the clocks. Things do not often go
wrong and when they do:
1- it showes up in water/ oil heat and or performance
or
2-too late even while you watch a PC

digital stuff I see as more of a hobby.

GregoryO'Connor
94ptRomolandCA

--- In WanderlodgeForum@yahoogroups.com, "Ralph L. Fullenwider"
wrote:
>
> Hello everyone:
>
> For those who are not familiar with codes, multiplexing or other
forms of
> reporting used in this day and age, I will attempt to bring to
light a
> little about these systems in the later Coaches.
>
> The reporting codes and information are inputs and outputs much
like on the
> computer you are using for the Forum. And each code is simply an
address of
> where in a computer, the information is stored. So in order to get
a
> readout for that code, you have to have the input/output (I/O)
schedule for
> the addresses.
>
> Though we see the codes reported in decimal (number) form, the
actual
> addresses are usually programmed in Hex or Octal or even machine
coding,
> then converted to binary and finally to numbers. In doing this,
one wire
> can be used to send a signal out on and to report back on several
addresses
> depending on the speed of the polling process.
>
> The reason for the software, readers and so forth is to convert
these
> multiplexed addresses to a form that we can attach a number to and
have a
> readout of what code or instruction is in that address.
>
> The codes are usually preset with a read out of what it is.
Example: A
> polling takes place sending out a question to a certain address,
then if no
> flags are set nothing comes back. But if an address, such as the
DDEC
> address for Low coolant is polled and a flag set, it sends back a
number of
> 13. Then you look up the code on the map and it tells you, code 13
is
> coolant level sensor low, add coolant and the flag goes off
satisfied.
>
> This is much simplified, to be sure, but the general idea comes
across.
> Easy huh? Hope this helps a little for those wondering what people
are
> talking about in some of the posts.
>
> Safe travels,
>
> Ralph and Charolette Fullenwider
> 84FC35
> Ralph's RV Solutions, Duncan, Oklahoma
>





[Non-text portions of this message have been removed]

[Ralph L. Fullenwider]

Greg:

I agree with the use of the KISS method and analog readouts.

I had a couple of back channel questions concerning some of the technical
talk lately and asked to shed a little light so more of an understanding
might be had. So I wrote a little blurb to do that.

The RV industry is behind the curve with technology but are starting to get
away from relay logic and going to multiplexing systems. Of course this
technology has been out for years in the industrial arena along with fiber
optics and 422 and 232 communications with up to 25 nodes on each single
conductor.

All the high line coaches are just now starting to pick up on some of this
stuff, The problem being, most of this technology was never meant to be
rolling down the road at 70MPH in a 40K plus motor coach.

Yep, give me the tried and true any day, but one has to keep up with on
going technology or get left behind. Am still trying to figure out
blue tooth and how to program the VCR. lol

Safe travels,

Ralph and Charolette Fullenwider
84FC35
Ralph's RV Solutions, Duncan, Oklahoma

At 08:06 PM 2/6/2007 +0000, you wrote:
>Ralph, It may just be my nature but; I dont believe that all the
>digital equipment is worth the worry. When I get a check engine
>light; I check the engine. If the heat goes up; I back off the
>demand. I have driven a good 400,000 on used class 8 diesel trucks
>with as much as 700,000 miles on the clocks. Things do not often go
>wrong and when they do:
>1- it showes up in water/ oil heat and or performance
>or
>2-too late even while you watch a PC
>
>
>digital stuff I see as more of a hobby.
>
>GregoryO'Connor
>94ptRomolandCA
>
> --- In WanderlodgeForum@yahoogroups.com, "Ralph L. Fullenwider"
> wrote:
> >
> > Hello everyone:
> >
> > For those who are not familiar with codes, multiplexing or other
>forms of
> > reporting used in this day and age, I will attempt to bring to
>light a
> > little about these systems in the later Coaches.
> >
> > The reporting codes and information are inputs and outputs much
>like on the
> > computer you are using for the Forum. And each code is simply an
>address of
> > where in a computer, the information is stored. So in order to get
>a
> > readout for that code, you have to have the input/output (I/O)
>schedule for
> > the addresses.
> >
> > Though we see the codes reported in decimal (number) form, the
>actual
> > addresses are usually programmed in Hex or Octal or even machine
>coding,
> > then converted to binary and finally to numbers. In doing this,
>one wire
> > can be used to send a signal out on and to report back on several
>addresses
> > depending on the speed of the polling process.
> >
> > The reason for the software, readers and so forth is to convert
>these
> > multiplexed addresses to a form that we can attach a number to and
>have a
> > readout of what code or instruction is in that address.
> >
> > The codes are usually preset with a read out of what it is.
>Example: A
> > polling takes place sending out a question to a certain address,
>then if no
> > flags are set nothing comes back. But if an address, such as the
>DDEC
> > address for Low coolant is polled and a flag set, it sends back a
>number of
> > 13. Then you look up the code on the map and it tells you, code 13
>is
> > coolant level sensor low, add coolant and the flag goes off
>satisfied.
> >
> > This is much simplified, to be sure, but the general idea comes
>across.
> > Easy huh? Hope this helps a little for those wondering what people
>are
> > talking about in some of the posts.
> >
> > Safe travels,
> >
> > Ralph and Charolette Fullenwider
> > 84FC35
> > Ralph's RV Solutions, Duncan, Oklahoma
> >
>
>
>

[Don Bradner]

Ralph, I'm glad you posted your explanation - I'm not surprised that there were
questions.

As a 3-year user of VMSpc, I find the advantages to be several. First, my mind
processes digital data better. I see 65 MPH more readily than I do a needle
pointing at the corresponding spot on the analog gauge.

Second, I get data that is not otherwise available. I really like, for example,
to be able to see the cruise set speed, so I know when I hit resume what it is
going to take me to. Worked better on the last coach where that number was
retained between power-on sessions, but it still is good after spending 30
minutes passing through a town off the cruise.

The remaining thing is the ability to set yellow and red alarms at my own choice
of set points. I'm going to get a red light from coolant temperature well before
I'm in trouble, and I hope the same will be true for coolant level. My copilot
keeps an eye on the laptop, and alerts me the moment any status changes from
green to any other color, without her having to know what numbers are "bad"
ones.

On 2/6/2007 at 7:11 PM Ralph L. Fullenwider wrote:

>Greg:
>
>I agree with the use of the KISS method and analog readouts.
>
>I had a couple of back channel questions concerning some of the technical
>talk lately and asked to shed a little light so more of an understanding
>might be had. So I wrote a little blurb to do that.

Don Bradner
http://www.arcatapet.net

[Gregory OConnor]

Don, Input from the copilot is another thing I dont want in my bus.
T " its red"
G "whats red"
T "the thing you told me to watch"
G "...............what happened to yellow"
T "OK its yellow..........., now its red"
G "Whats Red"
T "Hold on, Its 4th and 3,.... RUN IT, DAM'IT RUN IT"
G " Run WHAT!, What the hell is 4th & 3 ?"
T " Florida vs WVU,.....I cant do two things at once,
you watch the PMS-pc thing your self"
G " Focus, we have a problem"
T " OK OK , it says Windshield fluid low"
GregoryO'Connor
94ptRomoland


--- In WanderlodgeForum@yahoogroups.com, "Don Bradner"
wrote:
>
> Ralph, I'm glad you posted your explanation - I'm not surprised
that there were questions.
>
> As a 3-year user of VMSpc, I find the advantages to be several.
First, my mind processes digital data better. I see 65 MPH more
readily than I do a needle pointing at the corresponding spot on the
analog gauge.
>
> Second, I get data that is not otherwise available. I really like,
for example, to be able to see the cruise set speed, so I know when I
hit resume what it is going to take me to. Worked better on the last
coach where that number was retained between power-on sessions, but
it still is good after spending 30 minutes passing through a town off
the cruise.
>
> The remaining thing is the ability to set yellow and red alarms at
my own choice of set points. I'm going to get a red light from
coolant temperature well before I'm in trouble, and I hope the same
will be true for coolant level. My copilot keeps an eye on the
laptop, and alerts me the moment any status changes from green to
any other color, without her having to know what numbers are "bad"
ones.
>
> On 2/6/2007 at 7:11 PM Ralph L. Fullenwider wrote:
>
> >Greg:
> >
> >I agree with the use of the KISS method and analog readouts.
> >
> >I had a couple of back channel questions concerning some of the
technical
> >talk lately and asked to shed a little light so more of an
understanding
> >might be had. So I wrote a little blurb to do that.
>
> Don Bradner
> http://www.arcatapet.net
>

[Don Bradner]

That would have to come in while I was drinking coffee!!! Spfffft

My copilot enjoyed it as well.

On 2/7/2007 at 3:28 PM Gregory OConnor wrote:

>Don, Input from the copilot is another thing I dont want in my bus.
>T " its red"
>G "whats red"
>T "the thing you told me to watch"
>G "...............what happened to yellow"
>T "OK its yellow..........., now its red"
>G "Whats Red"
>T "Hold on, Its 4th and 3,.... RUN IT, DAM'IT RUN IT"
>G " Run WHAT!, What the hell is 4th & 3 ?"
>T " Florida vs WVU,.....I cant do two things at once,
> you watch the PMS-pc thing your self"
>G " Focus, we have a problem"
>T " OK OK , it says Windshield fluid low"
>GregoryO'Connor
>94ptRomoland

Don Bradner
http://www.arcatapet.net