<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Wanderlodge Gurus - The Member Funded Wanderlodge Forum - Monitoring]]></title>
		<link>http://www.wanderlodgegurus.com/</link>
		<description><![CDATA[Wanderlodge Gurus - The Member Funded Wanderlodge Forum - http://www.wanderlodgegurus.com]]></description>
		<pubDate>Sun, 17 May 2026 17:49:30 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Bluefire - a cool tool]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=11396</link>
			<pubDate>Tue, 23 Jun 2020 18:53:43 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=11396</guid>
			<description><![CDATA[Well, I finally broke down and bought a Bluefire for motorhomes ECM reader to monitor the DDEC.  I have to admit, it’s a very useful tool.  I have been using it to read some very recent and vexing DDEC codes and clear them as I fix things, but that’s a different thread. <br />
<br />
I downloaded the corresponding app and am running my new “glass dash” on a spare iPad.  It verifies my suspicions (and in some cases, hopes) that some of my analog gauges were reporting incorrect readings.  In that sense, it’s reassuring to be viewing better information on the engine and tranny.  Plus it’s interesting to see the instantaneous mpg figures when going downhill!  I hit a high of 340 mpg at one point!  Yeah, that didn’t last long. <br />
<br />
FYI, they have recently substantially reduced the price on these things. Plus if you use coupon code of “Amazon” they take even more off.   My only negative comment is that there doesn’t seem to be much for direct  customer support, except through an online forum of Q&amp;A postings. <br />
<br />
But all in all, I have found it to be a very useful tool to add to your bus.]]></description>
			<content:encoded><![CDATA[Well, I finally broke down and bought a Bluefire for motorhomes ECM reader to monitor the DDEC.  I have to admit, it’s a very useful tool.  I have been using it to read some very recent and vexing DDEC codes and clear them as I fix things, but that’s a different thread. <br />
<br />
I downloaded the corresponding app and am running my new “glass dash” on a spare iPad.  It verifies my suspicions (and in some cases, hopes) that some of my analog gauges were reporting incorrect readings.  In that sense, it’s reassuring to be viewing better information on the engine and tranny.  Plus it’s interesting to see the instantaneous mpg figures when going downhill!  I hit a high of 340 mpg at one point!  Yeah, that didn’t last long. <br />
<br />
FYI, they have recently substantially reduced the price on these things. Plus if you use coupon code of “Amazon” they take even more off.   My only negative comment is that there doesn’t seem to be much for direct  customer support, except through an online forum of Q&amp;A postings. <br />
<br />
But all in all, I have found it to be a very useful tool to add to your bus.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[oil pressure guage spiking]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=10936</link>
			<pubDate>Mon, 06 Mar 2017 19:06:26 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=10936</guid>
			<description><![CDATA[so the oil pressure guage seems to read as should untill i get up to 65mph then it pretty muvh just spikes. has anyone else came accross this issue? it is on a 93 with the detroit 500hp]]></description>
			<content:encoded><![CDATA[so the oil pressure guage seems to read as should untill i get up to 65mph then it pretty muvh just spikes. has anyone else came accross this issue? it is on a 93 with the detroit 500hp]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Reading Manifold Temperature with VMSPc]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=10664</link>
			<pubDate>Mon, 08 Feb 2016 19:16:18 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=10664</guid>
			<description><![CDATA[Recently installed Silverleaf VMSPc on our LXi (Series 60) and I'm trying to find out if it's possible to monitor the manifold temperature.  I found several older posts on various forums where others were having the same issue.  Just wondering if anyone ever found out is it was possible.   When I do a PID scan, I don't get a PID response for PID 105 which is the one to monitor for manifold temp ...so it's either not enabled through the ECU or maybe I have a bad wire.  Thanks in advance for any insights you can provide.<br />
John]]></description>
			<content:encoded><![CDATA[Recently installed Silverleaf VMSPc on our LXi (Series 60) and I'm trying to find out if it's possible to monitor the manifold temperature.  I found several older posts on various forums where others were having the same issue.  Just wondering if anyone ever found out is it was possible.   When I do a PID scan, I don't get a PID response for PID 105 which is the one to monitor for manifold temp ...so it's either not enabled through the ECU or maybe I have a bad wire.  Thanks in advance for any insights you can provide.<br />
John]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Exterior temperature sensor]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=10104</link>
			<pubDate>Fri, 06 Dec 2013 01:35:58 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=10104</guid>
			<description><![CDATA[Does anybody know where the exterior temp sensor is located on a 96 WB?  Mine quit working on the last trip home. The inside one still works, so it's either the sensor or the wiring to the main unit.<br />
<br />
Thanks!!]]></description>
			<content:encoded><![CDATA[Does anybody know where the exterior temp sensor is located on a 96 WB?  Mine quit working on the last trip home. The inside one still works, so it's either the sensor or the wiring to the main unit.<br />
<br />
Thanks!!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Air System Gauges]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=9946</link>
			<pubDate>Tue, 13 Aug 2013 05:36:53 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=9946</guid>
			<description><![CDATA[My prior 2000 LXi had 3 air pressure gauges. One for the front, one for the rear and one for the tag. <br />
<br />
My current 2000 LXi has only one air gauge for monitoring both front and back and one tag air gauge. <br />
<br />
My prior LXi had a tag dump switch and a suspension dump switch.<br />
My current LXi has no tag dump switch and only a suspension dump switch. <br />
<br />
I'm guessing my current bus was an earlier model than my prior bus as I don't remember the build date on my prior bus?<br />
<br />
This would indicate to me that the air system design was changed sometime in the 2000 year models. I wonder why BB made the change? <br />
<br />
Anyone know?]]></description>
			<content:encoded><![CDATA[My prior 2000 LXi had 3 air pressure gauges. One for the front, one for the rear and one for the tag. <br />
<br />
My current 2000 LXi has only one air gauge for monitoring both front and back and one tag air gauge. <br />
<br />
My prior LXi had a tag dump switch and a suspension dump switch.<br />
My current LXi has no tag dump switch and only a suspension dump switch. <br />
<br />
I'm guessing my current bus was an earlier model than my prior bus as I don't remember the build date on my prior bus?<br />
<br />
This would indicate to me that the air system design was changed sometime in the 2000 year models. I wonder why BB made the change? <br />
<br />
Anyone know?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[POLL: Remote Monitor/Control of your Wanderlodge]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=9833</link>
			<pubDate>Sat, 01 Jun 2013 16:33:29 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=9833</guid>
			<description><![CDATA[Assuming data plans are just a few dollars a month and can be purchased contract free on a month by month as needed basis. How much would you spend to be able to remotely monitor and control major systems in your bus? Think pet safety when left alone in an enclosed motorhome, extended repairs at a service facility, or long term storage in a remote location, etc.<br />
<br />
<span style="font-size: medium;"><span style="font-weight: bold;">Scroll up to vote in the Poll.</span></span>]]></description>
			<content:encoded><![CDATA[Assuming data plans are just a few dollars a month and can be purchased contract free on a month by month as needed basis. How much would you spend to be able to remotely monitor and control major systems in your bus? Think pet safety when left alone in an enclosed motorhome, extended repairs at a service facility, or long term storage in a remote location, etc.<br />
<br />
<span style="font-size: medium;"><span style="font-weight: bold;">Scroll up to vote in the Poll.</span></span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Digitel monitoring system]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=9813</link>
			<pubDate>Tue, 21 May 2013 23:06:41 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=9813</guid>
			<description><![CDATA[David has been discussing Sensor Area Networks, and it reminded me about a really neat feature on the older Birds - the Digitel monitoring system.  Additionally, I was speaking with a prospective Bird owner about a week ago and when I mentioned it to him, he responded that he had been reading all the forums for several years and looking at older Birds and he had never heard of such a thing.  I assured him it was real, whether he had heard of it or not, and I had one in my 1983 PT40 and it worked pretty well.  Because of those two items, I am going to make this a new thread so that prospective owners might find this information easier.<br />
<br />
The Digitel system was a really cool voice chip system on the late 70s-early 80s Birds (I don't know exactly how many years it spanned; perhaps Ralph can jump in here with some clarification).  I believe (from memory, so cut me some slack here!) that it may have been from PMMI, the same folks that did the musical horns.  Basically, in addition to time and temperature, it was tied into many of the bus systems and it actually spoke to you to warn you about various items on the Bird.   It reminded us of the robot on Lost in Space, and we referred to it as "The Little Man" (as in turn the Little Man on or off).  The main switch was in the dinette control panel.<br />
<br />
The first time the Little Man spoke to me was after about a week of ownership.  We had gone down to Mustang Island (aka Upper Padre Island) for a weekend.  We had just started up and over a really steep and really narrow ship channel bridge.  As a new owner, the lanes seemed like they were only about 9 feet wide with a concrete railing right on the line on either side.  Well, about halfway up this bridge, out of no where, in the speaker above my head comes this "WARNING! There is water in the fuel! Please stop and rectify."  And, he usually repeated everything he said twice, just so you would not miss it!  Well, I did manage not to hit anything, but I nearly ruined the seat covering.  Needless to say I stopped as soon as I got off the bridge and ran for the blue box.  Turns out, the Little Man was wired into the sensor in the sump in the fuel tank, the one that turns on the water in the fuel light on the dash.  As we went upward, the water that had settled in that sump went back to touch the sensor and the Little Man was there to warn me, even before the light on the dash went on.  Scared me silly.  Turned out there was about 4-6 ounces of water in the fuel sump when I figured out what to do next and drained it.  A little sensitive, but useful information nonetheless.<br />
<br />
Mostly, we kept the Little Man turned off, because our 83 was built during the 55mph speed limit, so in today's 70 or more speed limits, it was kind of annoying, albeit pretty funny.  As soon as you got past 60mph, he came on in the speaker over the driver with a gentle "Warning, you are exceeding the speed limit".  A little after 65, it was more of a "WARNING!  You are exceeding the speed limit, please slow down".  Once you crossed 70, he got downright apoplectic and started screaming at you "WARNING! YOU ARE EXCEEDING THE SPEED LIMIT. SLOW DOWN IMMEDIATELY!"  I couldn't get much past 72mph in the 83, so I don't know if he started crying for help at 75 or 80, or if he just sulked.  It was pretty funny how they seemingly had programmed in a personality.  <br />
 <br />
"He" also helped identify annoying warning buzzers.  I was going down the road and this annoying warning buzzer would start growling and then stop.  There were no dash warning lights on.  After about 100+ miles of that, we stopped and the first words were "Turn the Little Man on please".  In about 20 seconds, here he comes with a nice "Please check leveling jacks."  I looked down at the levers.  They were all in neutral and no leveling lights were on, so I scoffed, but hit the levers to retract anyway.  As soon as I touched the front drivers jack, I heard an immediate thunk.  That jack must have slipped down on that rough road by a whopping quarter of an inch or so.  Anyway, the Little Man was then happy, I was happy and we proceeded on without an annoying buzzer.<br />
<br />
He also had a great "WARNING! Intruder Alert! Warning, Intruder Alert!", but that's a story for another time, if my wife will let me tell it!  LOL<br />
<br />
In summary, I am hoping David's SAN work can reproduce a new version of the Little Man.  Maybe some of you guys with older coaches with a functioning Digitel can fill David in on some of the other features that this system monitored.<br />
<br />
FWIW,<br />
<br />
Mike Bulriss<br />
1991 WB40 "Texas Minivan"<br />
San Antonio, TX]]></description>
			<content:encoded><![CDATA[David has been discussing Sensor Area Networks, and it reminded me about a really neat feature on the older Birds - the Digitel monitoring system.  Additionally, I was speaking with a prospective Bird owner about a week ago and when I mentioned it to him, he responded that he had been reading all the forums for several years and looking at older Birds and he had never heard of such a thing.  I assured him it was real, whether he had heard of it or not, and I had one in my 1983 PT40 and it worked pretty well.  Because of those two items, I am going to make this a new thread so that prospective owners might find this information easier.<br />
<br />
The Digitel system was a really cool voice chip system on the late 70s-early 80s Birds (I don't know exactly how many years it spanned; perhaps Ralph can jump in here with some clarification).  I believe (from memory, so cut me some slack here!) that it may have been from PMMI, the same folks that did the musical horns.  Basically, in addition to time and temperature, it was tied into many of the bus systems and it actually spoke to you to warn you about various items on the Bird.   It reminded us of the robot on Lost in Space, and we referred to it as "The Little Man" (as in turn the Little Man on or off).  The main switch was in the dinette control panel.<br />
<br />
The first time the Little Man spoke to me was after about a week of ownership.  We had gone down to Mustang Island (aka Upper Padre Island) for a weekend.  We had just started up and over a really steep and really narrow ship channel bridge.  As a new owner, the lanes seemed like they were only about 9 feet wide with a concrete railing right on the line on either side.  Well, about halfway up this bridge, out of no where, in the speaker above my head comes this "WARNING! There is water in the fuel! Please stop and rectify."  And, he usually repeated everything he said twice, just so you would not miss it!  Well, I did manage not to hit anything, but I nearly ruined the seat covering.  Needless to say I stopped as soon as I got off the bridge and ran for the blue box.  Turns out, the Little Man was wired into the sensor in the sump in the fuel tank, the one that turns on the water in the fuel light on the dash.  As we went upward, the water that had settled in that sump went back to touch the sensor and the Little Man was there to warn me, even before the light on the dash went on.  Scared me silly.  Turned out there was about 4-6 ounces of water in the fuel sump when I figured out what to do next and drained it.  A little sensitive, but useful information nonetheless.<br />
<br />
Mostly, we kept the Little Man turned off, because our 83 was built during the 55mph speed limit, so in today's 70 or more speed limits, it was kind of annoying, albeit pretty funny.  As soon as you got past 60mph, he came on in the speaker over the driver with a gentle "Warning, you are exceeding the speed limit".  A little after 65, it was more of a "WARNING!  You are exceeding the speed limit, please slow down".  Once you crossed 70, he got downright apoplectic and started screaming at you "WARNING! YOU ARE EXCEEDING THE SPEED LIMIT. SLOW DOWN IMMEDIATELY!"  I couldn't get much past 72mph in the 83, so I don't know if he started crying for help at 75 or 80, or if he just sulked.  It was pretty funny how they seemingly had programmed in a personality.  <br />
 <br />
"He" also helped identify annoying warning buzzers.  I was going down the road and this annoying warning buzzer would start growling and then stop.  There were no dash warning lights on.  After about 100+ miles of that, we stopped and the first words were "Turn the Little Man on please".  In about 20 seconds, here he comes with a nice "Please check leveling jacks."  I looked down at the levers.  They were all in neutral and no leveling lights were on, so I scoffed, but hit the levers to retract anyway.  As soon as I touched the front drivers jack, I heard an immediate thunk.  That jack must have slipped down on that rough road by a whopping quarter of an inch or so.  Anyway, the Little Man was then happy, I was happy and we proceeded on without an annoying buzzer.<br />
<br />
He also had a great "WARNING! Intruder Alert! Warning, Intruder Alert!", but that's a story for another time, if my wife will let me tell it!  LOL<br />
<br />
In summary, I am hoping David's SAN work can reproduce a new version of the Little Man.  Maybe some of you guys with older coaches with a functioning Digitel can fill David in on some of the other features that this system monitored.<br />
<br />
FWIW,<br />
<br />
Mike Bulriss<br />
1991 WB40 "Texas Minivan"<br />
San Antonio, TX]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Sensor Area Networks (SANs)]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=9770</link>
			<pubDate>Sat, 04 May 2013 15:19:28 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=9770</guid>
			<description><![CDATA[Folks,<br />
<br />
For the time being I'm going to set configuring WaGu aside so I can get back to our Sensor Area Network.<br />
<br />
I'd like your opinion on a few things.<br />
<br />
First, I think scattering arduinos throughout the bus may not be the best solution. Too many arduinos creates too many points of failure. Plus I'm not convinced the arduino with it's associated sensor hardware is up to the commercial/industrial environments our bus SAN requires. Also, the arduino doesn't seem to have the computing power required forcing us to eventually hang them off a Rasberry Pi or some other full purpose high-power computing environment.<br />
<br />
To solve some of these issues I started to look around at what the robotics world and the automated factory world is using.<br />
<br />
I stumbled across an interesting architecture pioneered by a gentleman named Saul Greenberg from the University of Calgary, <a href="http://en.wikipedia.org/wiki/Phidget" target="_blank">Wiki</a>.<br />
<br />
His architecture may suit our needs better. Basically he takes a bunch of sensors, aggregates them, and connects them to a computing platform via USB. The computing platform can be any type of machine running a host of real operating systems. It can even be a Rasberry Pi.  The rPi can be located anywhere and is powerful enough to communicate via the full TCP/IP stack with any other host, local or remote. This means ostensibly you could control your bus with your iPad (over iOS) from your homebase living room sofa, many miles away.<br />
<br />
The idea would be a set of sensors implemented using Phidgets connected to a rPi communicating wirelessly to a GUI somewhere (iPhone, iPad, Android, Laptop, Dashtop).<br />
<br />
Check out these links: <a href="http://www.phidgets.com/index.php" target="_blank">Phidgets</a>, <a href="http://www.robotshop.com/productinfo.aspx?pc=RB-Phi-57&amp;lang=en-US" target="_blank">Robotshop</a>, <a href="http://www.dsprobotics.com/flowstone.html" target="_blank">DSP Robotics</a>, <a href="http://www.phidgets.com/docs/OS_-_Linux" target="_blank">Linux Support</a>.]]></description>
			<content:encoded><![CDATA[Folks,<br />
<br />
For the time being I'm going to set configuring WaGu aside so I can get back to our Sensor Area Network.<br />
<br />
I'd like your opinion on a few things.<br />
<br />
First, I think scattering arduinos throughout the bus may not be the best solution. Too many arduinos creates too many points of failure. Plus I'm not convinced the arduino with it's associated sensor hardware is up to the commercial/industrial environments our bus SAN requires. Also, the arduino doesn't seem to have the computing power required forcing us to eventually hang them off a Rasberry Pi or some other full purpose high-power computing environment.<br />
<br />
To solve some of these issues I started to look around at what the robotics world and the automated factory world is using.<br />
<br />
I stumbled across an interesting architecture pioneered by a gentleman named Saul Greenberg from the University of Calgary, <a href="http://en.wikipedia.org/wiki/Phidget" target="_blank">Wiki</a>.<br />
<br />
His architecture may suit our needs better. Basically he takes a bunch of sensors, aggregates them, and connects them to a computing platform via USB. The computing platform can be any type of machine running a host of real operating systems. It can even be a Rasberry Pi.  The rPi can be located anywhere and is powerful enough to communicate via the full TCP/IP stack with any other host, local or remote. This means ostensibly you could control your bus with your iPad (over iOS) from your homebase living room sofa, many miles away.<br />
<br />
The idea would be a set of sensors implemented using Phidgets connected to a rPi communicating wirelessly to a GUI somewhere (iPhone, iPad, Android, Laptop, Dashtop).<br />
<br />
Check out these links: <a href="http://www.phidgets.com/index.php" target="_blank">Phidgets</a>, <a href="http://www.robotshop.com/productinfo.aspx?pc=RB-Phi-57&amp;lang=en-US" target="_blank">Robotshop</a>, <a href="http://www.dsprobotics.com/flowstone.html" target="_blank">DSP Robotics</a>, <a href="http://www.phidgets.com/docs/OS_-_Linux" target="_blank">Linux Support</a>.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Diagnostic plug]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=9731</link>
			<pubDate>Sat, 20 Apr 2013 20:55:21 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=9731</guid>
			<description><![CDATA[I have a question for you super sharp technical folks.  Is there any reasonable way to check the integrity of a Series 60 engine diagnostic plug short of hooking it up to a Detroit diagnostic computer.   <br />
<br />
The Pro Driver on my 2003 LXI is inoperable and I am not sure if it is a Pro Driver problem, a wire problem between the unit and the diagnostic plug or a wire problem betwen the diagnostic plug and the engine ECU.  <br />
<br />
I have not taken the time to remove and diagnose the individual items.  Both the Pro Driver and the diagnostic plug are very difficult to access.  I have a wiring diagram for both the Pro Driver and the ECU to the diagnostic plug.<br />
<br />
Any suggestions or advice would be appreciated.]]></description>
			<content:encoded><![CDATA[I have a question for you super sharp technical folks.  Is there any reasonable way to check the integrity of a Series 60 engine diagnostic plug short of hooking it up to a Detroit diagnostic computer.   <br />
<br />
The Pro Driver on my 2003 LXI is inoperable and I am not sure if it is a Pro Driver problem, a wire problem between the unit and the diagnostic plug or a wire problem betwen the diagnostic plug and the engine ECU.  <br />
<br />
I have not taken the time to remove and diagnose the individual items.  Both the Pro Driver and the diagnostic plug are very difficult to access.  I have a wiring diagram for both the Pro Driver and the ECU to the diagnostic plug.<br />
<br />
Any suggestions or advice would be appreciated.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Arduino Uno vs Beaglebone vs Raspberry Pi]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=195</link>
			<pubDate>Thu, 28 Mar 2013 20:11:27 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=195</guid>
			<description><![CDATA[<a href="http://digitaldiner.blogspot.fr/2012/10/arduino-uno-vs-beaglebone-vs-raspberry.html" target="_blank">http://digitaldiner.blogspot.fr/2012/10/...berry.html</a><br />
<br />
Have fun  <img src="images/smilies/cool.gif" style="vertical-align: middle;" border="0" alt="Cool" title="Cool" /><br />
<br />
--Ned]]></description>
			<content:encoded><![CDATA[<a href="http://digitaldiner.blogspot.fr/2012/10/arduino-uno-vs-beaglebone-vs-raspberry.html" target="_blank">http://digitaldiner.blogspot.fr/2012/10/...berry.html</a><br />
<br />
Have fun  <img src="images/smilies/cool.gif" style="vertical-align: middle;" border="0" alt="Cool" title="Cool" /><br />
<br />
--Ned]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[ProDriver]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=191</link>
			<pubDate>Tue, 26 Mar 2013 01:18:15 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=191</guid>
			<description><![CDATA[So an outstanding Bird owner has assisted me in obtaining a ProDriver for my bird. Does anybody have any wiring info for such an animal?]]></description>
			<content:encoded><![CDATA[So an outstanding Bird owner has assisted me in obtaining a ProDriver for my bird. Does anybody have any wiring info for such an animal?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[CAT 3208 monitoring]]></title>
			<link>http://www.wanderlodgegurus.com/showthread.php?tid=121</link>
			<pubDate>Wed, 27 Feb 2013 06:46:15 +0000</pubDate>
			<guid isPermaLink="false">http://www.wanderlodgegurus.com/showthread.php?tid=121</guid>
			<description><![CDATA[Sorry but I don't know of a monitor for the 3208. Unlike more modern engines, my '91 300HP doesn't have a "computer" to manage the engine, and therefore has no data bus to provide trouble codes, engine data, and the other monitor functions that the DDEC computer and data bus collect and provide to the dashboard area.   <br />
<br />
Still, my WL has plenty of sensors and interesting places to collect information, including the usual things like coolant levels, temps, pressures, and so forth.  It would be useful to break out and monitor the individual sensors that are currently aggregated into the "Check Engine" warning light. I know of a sensor on the leveling jacks, a sensor on the coolant tank on top of the engine radiator, and I assume there are more.  Any of these will turn on the generic "Check engine" warning.  I hate it when that happens, because I want it tell me which system the problem is in.<br />
<br />
So I think about lashing up a short custom wiring harness to feed the data from sensors to an Arduino inside the coach.  They have plenty enough processing power to log, filter, transform, and transmit a handful of raw data inputs for display. I'd probably try to send it wirelessly to dashboard area for display. <br />
<br />
I've never used Arduino for wireless data transmission.  I picked up an XBee shield thinking it was what I needed, but it needs the actual XBEE wireless radio component as an add-on.  The XBee web site says this shield model is deprecated!  So I am back at square one on that aspect of the project.<br />
<br />
David mentioned once that he was thinking about an engine fan speed monitor, and I thought this sounded like a cool idea so I put together a prototype based on a bicycle speedometer and a few lines of code modified from a sample code I found on the web.  It works perfectly as a counter--every time I wave the magnet near the sensor, the arduino reads it as a high value. When the magnet is out of range, the arduino reads it as "0".  All that remains is finding a mounting place close enough to the Horton fan to pick up the magnet as it goes by, attached to a fan blade. Heh--an Arduino fan speed sensor!<br />
<br />
 I get carried away with the possibiiities.  I know better, but under this hardcore veneer of 3208 "KISS" discipline, I am at heart a fully-instrumented kind of guy. I don't mind the uncertainty of taking the bus on the road with the prospect of mechanical problems at some point before returning home. But I would love to be able to see problems developing before they occur by keeping an eye on more aspects of critical systems and engine operating parameters.  There's no particular reason why I couldn't monitor many more things than my coach in factory trim is equipped to do.<br />
<br />
Is anyone else hacking the 3208/Arduino frontier?  Care to share?<br />
<br />
--Ned<br />
<br />
Ned Bedinger<br />
'91 SP36]]></description>
			<content:encoded><![CDATA[Sorry but I don't know of a monitor for the 3208. Unlike more modern engines, my '91 300HP doesn't have a "computer" to manage the engine, and therefore has no data bus to provide trouble codes, engine data, and the other monitor functions that the DDEC computer and data bus collect and provide to the dashboard area.   <br />
<br />
Still, my WL has plenty of sensors and interesting places to collect information, including the usual things like coolant levels, temps, pressures, and so forth.  It would be useful to break out and monitor the individual sensors that are currently aggregated into the "Check Engine" warning light. I know of a sensor on the leveling jacks, a sensor on the coolant tank on top of the engine radiator, and I assume there are more.  Any of these will turn on the generic "Check engine" warning.  I hate it when that happens, because I want it tell me which system the problem is in.<br />
<br />
So I think about lashing up a short custom wiring harness to feed the data from sensors to an Arduino inside the coach.  They have plenty enough processing power to log, filter, transform, and transmit a handful of raw data inputs for display. I'd probably try to send it wirelessly to dashboard area for display. <br />
<br />
I've never used Arduino for wireless data transmission.  I picked up an XBee shield thinking it was what I needed, but it needs the actual XBEE wireless radio component as an add-on.  The XBee web site says this shield model is deprecated!  So I am back at square one on that aspect of the project.<br />
<br />
David mentioned once that he was thinking about an engine fan speed monitor, and I thought this sounded like a cool idea so I put together a prototype based on a bicycle speedometer and a few lines of code modified from a sample code I found on the web.  It works perfectly as a counter--every time I wave the magnet near the sensor, the arduino reads it as a high value. When the magnet is out of range, the arduino reads it as "0".  All that remains is finding a mounting place close enough to the Horton fan to pick up the magnet as it goes by, attached to a fan blade. Heh--an Arduino fan speed sensor!<br />
<br />
 I get carried away with the possibiiities.  I know better, but under this hardcore veneer of 3208 "KISS" discipline, I am at heart a fully-instrumented kind of guy. I don't mind the uncertainty of taking the bus on the road with the prospect of mechanical problems at some point before returning home. But I would love to be able to see problems developing before they occur by keeping an eye on more aspects of critical systems and engine operating parameters.  There's no particular reason why I couldn't monitor many more things than my coach in factory trim is equipped to do.<br />
<br />
Is anyone else hacking the 3208/Arduino frontier?  Care to share?<br />
<br />
--Ned<br />
<br />
Ned Bedinger<br />
'91 SP36]]></content:encoded>
		</item>
	</channel>
</rss>