X10 Community Forum
🔌General Home Automation => Other Automation Systems => Powerline Control Reliability => Topic started by: JeffVolp on July 03, 2009, 07:51:49 PM
-
Some of you have been following my work on the forthcoming X10 signal meter. I thought I'd put up a photo of the prototype and tell you a few of its features. Here is the photo:
http://jvde.us/xtb/XTBM_prototype.jpg
While I originally planned to just replace the ESM1, this will be a "poor man's Monterey".
The readout (updated to match the new photograph) indicates:
X is the X10 signal voltage for the most recent command
F is the received X10 carrier frequency
N is the background noise level
P06 is the last unit code received (P house code, 6 unit code)
DIM is the last command received
There is still a lot of firmware work to do, but the target is this fall. It will be available in kit or assembled form.
Question, do you prefer the black case or a bone color case, like the XTB?
EDIT NOTE: The photograph has been updated as the design has evolved. The noise level is now working correctly, and the Q has been replaced with an actual frequency measurement.
Jeff
-
Awesome Jeff!!. Look forward for this be available. >!
Humm. Bone or Black. Which one will be cheaper Jeff. I choose that one. :)%
-
Thanks for the update and teaser. I maybe also in line when it is available.
I personally like Black.
-
Humm. Bone or Black. Which one will be cheaper Jeff. I choose that one. :)%
I wanted "metallic blue" to match the LCD, but Polycase doesn't make the windowed version in that color. Black, bone (and gray) are the same cost.
Jeff
-
...I wanted "metallic blue" to match the LCD, but Polycase doesn't make the windowed version in that color...
Metallic blue would of been cool but bottom line function is more important.
The prototype looks really cool so if most people are saying black then that's fine with me.
-
Too bad on the Metalic Blue. That would top my list for sure. ;D
I do like all the data on the display. Kind of like a TesterLinc's only all on one display. Except maybe the store function that held the last 50 [I think] messages received. The voltage part of the display is a great feature.
-
That is just plain sexy.
I'll want a kit. I'll need to get it cheaply as possible. ;)
Black. Beige shows our dirty little fingerprints.
-
Hi Jeff,
I can see you haven't been resting on your laurels this summer. With both the ESM1 and Testerlinc off the market, this device will be a boon to people maintaining their X10 systems. It looks like a nice improvement over those devices as well.
I do have a few questions:
1) Quality count : Which window is used for this measurement- The transmission window (1ms) or receive window (0.6ms)? Is there a minimum quality count for decoding a logic 1? As a reference, my testerlinc routinely shows a Q in the 130 range - Interesting since a 1ms burst of 120Khz would yield a max of 120 counts.
2) Noise N .80V : That's some pretty stout noise. Is this measured using a bandpass around the X10 frequency, or a highpass? I'm curious whether this could measure noise in the Insteon carrier region.
3) Displayed X10 Codes: Will this device be able to decode/display X10 extended codes/data?
Sorry for all the questions. Once again, you've piqued my interest.
Boiler
-
The quality count is the number of cycles seen in the X10 reception window. X10 specifies a logic "1" requires a minimum of 48 pulses in a reception window that extends from .250uS to 900uS after the zero crossing. Actually, my sample window is only 532uS right now, but that will be changed. It measures the burst voltage at 16 points over the full 1mS pulse length, and displays the average.
As I said, firmware development is in process. The noise code is not working yet. There is a bandpass filter with maximum sensitivity just above 120KHz. Yes, it will certainly measure noise in the Insteon region with almost the same sensitivity as at 120KHz.
Noise is a complex issue. There can be relatively stable background noise, such as that produced by a single noise source or the unmodulated carrier of a wireless intercom. Then there can be modulated noise produced by multiple sources summing together. Differences in the noise frequency cause beat frequencies that modulate the noise amplitude. Finally, there can be transients, which are high amplitude, short duration events.
While I was going to try to peak detect the transients, their short duration means they really do not effect X10 communication. My intent now is to display an average noise voltage, and possibly add a descriptive symbol or keyword to indicate whether the noise is stable or varying.
It will display "Xtnd" for an Extended command, but it will not process the extended data portion. Similarly for X10 Preset Dim commands, where it will display "Pset".
Jeff
-
Jeff,
Thank you for the explanation. I agree with your approach to display average noise (rather than trying to quantify transients) and see the varying/stable tag as being very useful in understanding the noise environment.
Your explanation did raise another question - will you be averaging noise over the entire 60Hz period or just in a window around the the zero crossing. Pros and cons for either method. Standard X10 devices should not be affected unless the noise is present in the transmission window. However, some devices with AGC could be fooled by out of noise outside the transmission window and decrease their sensitivity to compensate (non gated devices).
I've always wanted to ask the noise window question for both the ELK and Testerlinc but had nobody to ask. It makes a huge difference in how you interpret the reading. In this case, it's really handy being able to ask the designer directly.
Boiler
-
I am sampling in two windows right now, 1mS before zero crossing, and also during the X10 transmission window itself. Since that spans the Insteon transmission period, I thought it would allow me to identify an Insteon transmission. However, my CFL "noise generator" produces a lot of noise in those two sample windows, which looks like an Insteon signal if I just sample the amplitude. A recent (untested) change to the PCB allows me to measure the frequency of the signal. I hope that helps me discriminate between an Insteon command and just in-band noise. I may sample in a third 1mS window just after the X10 transmission window if that approach alone doesn't work. That said, there is a limit to how much can be done in a 2KB PIC.
Jeff
-
I want me one! Don't care 'bout no steeenkeen color.
Actually bone would look good in livingroom or office, as a "dressy" permanent system health indicator. and black or gray looks like a great lab or workshop instrument. I don't think your final color selection will matter much to us hard core "X10ers".
"Bits" is worried about fingerprints only because he loves peanut butter and jelly sandwiches. Don't worry Bits, only the jelly will show up on the bone. Besides, I bet the bone would look great in your studio :)%
OK on a more serious note. Jeff, It looks great. It provides more information that I expected. What is your projected price(s). I haven't "slodered" a Heathkit in three decades...I'm ready for a nice kit. Can't wait!!
Dave
-
The cost is dominated by a few components: PCB, LCD display, case, connectors, power transformer, and AD817A op-amp. The other 70 odd components are relatively inexpensive. I only bought bare-bones prototype PCBs so far ($36 each shipped), so I don't have a good number for that. I'm shooting for the kit to be $70-$80, and the assembled unit maybe $40 more.
Jeff
-
WOHOO, I got that in a coffee can in the back yard.I'm sure I will have found it by the time you are ready to ship. ;D
-
I was hoping for bright yellow so I could find where I last left it.
-
I was hoping for bright yellow so I could find where I last left it.
It might have to glow in the dark for me to find it. rofl
The cost is dominated by a few components: PCB, LCD display, case, connectors, power transformer, and AD817A op-amp. The other 70 odd components are relatively inexpensive.... ...I'm shooting for the kit to be $70-$80, and the assembled unit maybe $40 more....
Hmm... Now I just have to figure out if I'm a good enough solderer to get all the "70 odd components"+ in the right place without frying any or if I should shell out the additional to have it done for me.
-
Hmm... Now I just have to figure out if I'm a good enough solderer to get all the "70 odd components"+ in the right place without frying any or if I should shell out the additional to have it done for me.
It is a relatively loose layout. Most components solder flat onto the board. The only thing that may be a little tough to do is to get proper alignment of the LCD connectors so they mate correctly when the cover is installed. The downside of a loose layout is that the PCB is more expensive than it would be for a tight layout. But you can more than make up for that by warming up the soldering iron.
Jeff
-
I'm so excited, I'm vibrating.
-
I'm so excited, I'm vibrating.
You know you're a die hard X10 user when a signal meter is a turn on. ;) rofl
-
I'm so excited, I'm vibrating.
You know you're a die hard X10 user when a signal meter is a turn on. ;) rofl
Yeah, you have seen me the day I got my first repeater.....oh my goodness. ;)
-
Another status update on the signal meter (revised 7/24): As mentioned earlier, I incorporated a hardware mod to be able to measure the carrier frequency. I updated the prototype photo showing that readout:
http://jvde.us/xtb/XTBM_prototype.jpg
You may notice I also increased the X10 signal level resolution. (I deleted the "V's" from the display to cram on more data.)
During testing, one of my Maxi Controllers read out 130Khz. While I first suspected something was wrong in the code, checking with my digital scope confirmed the number was indeed correct. That is one of the ancient boxy Sears units, so it may have drifted from the nominal 120KHz over the years. A relatively new Leviton Maxi Conroller is exactly at 120KHz, and my TW751 reads 121KHz.
I was a bit surprised that X10 modules still work fine with a Maxi Controller that far off frequency. I was going to use frequency to recognize an Insteon transmission, but clearly that won't work by itself.
In addition to displaying VALID X10 commands, the unit will also display:
BAD START CODE (something other than 1110)
ERROR: COLLISION (too many bits received)
ERROR: BIT COUNT (not enough bits received)
ERROR: NOISE (for excessive noise on the powerline)
The modified prototype hardware is working well, and PCBs have been ordered. Availability should still be early fall.
Jeff
-
O-boy, o-boy, o-boy, o-boy, o-boy! :)%
-
Wha whoo!!!! #:)
Looking forward to it!
-
... That is one of the ancient boxy Sears units.....
Ah! A kindred spirit!
-
Question for you fellows using the CM15A...
So the signal meter can automatically display a repeater's signal level when it is plugged in, it will issue a command shortly after power-up, and read back the repeated amplitude. Only the first half of the command will be sent so it can monitor the powerline during the repeated second half. I plan to use "P Hail Acknowledge" for the command to try to avoid causing any problems. Does anybody see a problem with that?
Also, for the noise monitor, it will send a command when there is a sudden increase or decrease in noise level. I know P16 is used by some other equipment, so I thought I would piggyback on that code. It would send "P16 ON" if there is a sudden increase in background noise, and "P16 OFF" for a sudden decrease. I had thought about using Bright and Dim commands as more intuitive, but ON and OFF should be easier to capture in a reporting system. Any comments?
FYI, PCBs ordered today...
Jeff
-
...It would send "P16 ON" if there is a sudden increase in background noise, and "P16 OFF" for a sudden decrease...
Doesn't the CM15A send a "P16 ON" when power is restored. If so, would that be any conflict?
-
...It would send "P16 ON" if there is a sudden increase in background noise, and "P16 OFF" for a sudden decrease...
Doesn't the CM15A send a "P16 ON" when power is restored. If so, would that be any conflict?
It wouldn't be at my end. The XTB-IIR sends "P16 Status ON" when power is restored.
The X10/Leviton tester pair sends a P1 ON/OFF repeating sequence. Since that is already defined for tester use, perhaps I should use that here too?
Jeff
-
Question for you fellows using the CM15A...
So the signal meter can automatically display a repeater's signal level when it is plugged in, it will issue a command shortly after power-up, and read back the repeated amplitude. Only the first half of the command will be sent so it can monitor the powerline during the repeated second half. I plan to use "P Hail Acknowledge" for the command to try to avoid causing any problems. Does anybody see a problem with that?
Also, for the noise monitor, it will send a command when there is a sudden increase or decrease in noise level. I know P16 is used by some other equipment, so I thought I would piggyback on that code. It would send "P16 ON" if there is a sudden increase in background noise, and "P16 OFF" for a sudden decrease. I had thought about using Bright and Dim commands as more intuitive, but ON and OFF should be easier to capture in a reporting system. Any comments?
FYI, PCBs ordered today...
Jeff
#1
Not a problem for me.
#2
This is great!! What a great tool to help us track down intermitent noise problems, by logging the precise time the noise occured (or started). Just for giggles I think my system will say, "Dave, what was that noise?" with every P16 ON. :)%
-
Just for giggles I think my system will say, "Dave, what was that noise?" with every P16 ON. :)%
How about: "Dave, TURN THAT OFF!"
Jeff
-
I'm looking forward to building the meter. For those who haven't built a kit in a while, fear not, I successfully assembled the XTB-IIR earlier this year. Jeff's kit instructions are complete (and accurate!).
Oh, I vote for black because it matches better with my OptiVisor. Now if I could just get a deal on a lab coat... -:)
-
Now if I could just get a deal on a lab coat... -:)
How does less than 4 bucks sound? :D
http://www.sciplus.com/search.cfm?utm_source=internal&utm_medium=search&utm_content=cf&utm_campaign=celsearchtest&formfield1234567891=321&formfield1234567892=9&formfield1234567894=&term=lab+coat&btnHand.x=0&btnHand.y=0
-
Oh, I vote for black because it matches better with my OptiVisor.
Black cases have been ordered...
Jeff
-
How does less than 4 bucks sound? :D
That would send my wife over the edge! rofl
-
Black cases have been ordered...
Jeff
s-s-s-s-s-s-snuff!
...silence...
(and that friends, is the sound of "bated breath")
-
I would like some feedback here.
I added the code that transmits a P1 ON in response to a significant increase in noise, and confirmed that was working by injecting a variable noise level from my Wavetek.
Then I plugged in that infamous Cellet cellphone charger. The meter immediately started logging bad start codes, but there was virtually no increase in indicated noise level, and the noise increase detector was not triggered.
The meter samples the powerline in three windows: just before, during, and just after the X10 transmission window. It normally displays the signal or noise level during the X10 window. Using a storage scope to capture noise from the Cellet charger, its switching regulator only pulses on in the X10 reception window a few times a second. While that is certainly enough to corrupt X10 transmissions, it is not enough to raise the average noise level significantly. Looking just during X10 reception windows, the average noise remains below 25mV. However, looking over the whole cycle, the noise gets up to almost a volt when there is a load on the charger. Yes, that is one nasty device.
To be useful, I think the meter should identify even very intermittent noise capable of causing X10 communications problems. I modified the A/D sampling routines to not only capture peak noise over an entire X10 transmission, but also peak noise during each individual X10 sample window. That does show an increase when the charger is plugged in, but still less than 100mV. However, that is certainly capable of causing bad start codes, and a serious X10 reliability problem. Maybe the best indicator is the fact that the meter is displaying a continuous stream of bad start codes whenever the charger is plugged in.
Displaying peak noise clearly works better for a device such as the Cellet charger. It will also give a good reading for constant noise, such as that produced by a wireless intercom. Noise injected from my Wavetek reads virtually the same with either an average or a peak detector. The peak detector does have a problem with very short high-energy pulses, which indicate an elevated noise level, but may not be long enough to corrupt X10 communications. My next step is to gate the max amplitude detector with pulse count, and ignore any high amplitude pulse that does not last long enough to be detected as a X10 logic "1".
One other option is to examine noise over other regions of the waveform. The Cellet charger is much more active during the mid portion of the sinewave, which is where it generates most of its noise. However, that noise has no impact at all on X10 communication. Sampling over more of the waveform could "red-flag" devices as filter candidates even though adding the filter does nothing to improve X10 system reliability. Because of this, I thought it best to focus just on the X10 reception window. The other windows are used to help isolate X10 traffic from the background noise level on either side of the X10 sample window.
Any suggestions as I continue to work this issue are welcome.
Jeff
-
...Any suggestions as I continue to work this issue are welcome...
You're so far ahead of most of us on the whole issue of noise and X10 that I humble in you presence.
I'll certainly let you know should I think of something, however. ;D
-
Though my test equipment is not close to what you have Jeff. I have seen devices give me a bar or two on my ESM1. While my scope shows the noise on the peak of the waveform. So maybe looking around the X10 signal area maybe be better.
-
I have seen devices give me a bar or two on my ESM1. While my scope shows the noise on the peak of the waveform. So maybe looking around the X10 signal area maybe be better.
The Cellet charger gives one flickering bar on the ESM1, whether it is loaded or not. Because the Cellet noise reaches almost a volt during the peak of the waveform when loaded, the ESM1 must be sampling only during the X10 reception window too.
The noise detector will display peak amplitude of noise bursts in the X10 reception window that are long enough to trigger false "1" bits.
Followup: That method is working well. It ignores the big fat transient we have right in the middle of the X10 sample window, but easily recognizes the noise produced by the Cellet charger.
Jeff
-
The XTBM signal meter is almost here. I ordered the remaining components today, and will assemble the first "production" unit next week.
While I have been thoroughly testing the various modes, I would like some feedback to see if there are any usability issues I haven't thought of. Please contact me directly if you would like to receive one of the first few kits at a special introductory price.
Jeff
-
Here is a photo of the XTBM "production prototype" PCB:
http://jvde.us/xtb/XTBM_v10_pcb.jpg
Here is a draft of the description:
http://jvde.us/xtb/XTBM_X10_signal_meter.doc
For those who have already ordered kits, I am sorting and packaging components now, and your kits will be on the way tomorrow or Monday.
Thanks,
Jeff
-
Looks like it will be a welcomed addition to many X10 installations.
-
Weller temp controlled iron and 63/37 solder excitedly waiting for USPS delivery. (I'm vibrating...which may make soldering difficult). :)%
-
Yeah, I'm looking forward to building, and playing, with the XTMB!
-
FYI to kit buyers.
The kit is an easy build. Very high quality PC board, and well laid out. I'm not finished building yet, but am impressed with the quality so far.
One tip would be to print the jpg color pix of the assembled PC board to a good color printer for parts placement reference during build.
Especially important if you do not know resistor color code. Let's see, how does that go again; "Bad Boys ......" ;D
-
As an example of how to use the XTBM, I have the prototype plugged into our "problem" X10 circuit. That circuit feeds seven X10 devices, including three transmitters. With no booster in the system, the XTBM was reporting the .13V signal received from the Ocelot's TW523. Plugging the prototype XTB-R into a standard AC receptacle near the distribution panel boosted that reading to 2.27V. Peak background noise is .05V.
The meter is displaying the G16 ON/OFF toggle that runs our hot water recirculation pump several times an hour.
Jeff
-
FYI to kit buyers.
The kit is an easy build.
Not nearly as many components as the XTB-IIR.
-
I have the XTBM assembled. It went together rather easily, except that I installed the header with the short side up and it didn't reach the LCD plug. I replaced the header (Jeff said to cut the plastic off and de-solder the pins individually) and put it back together.
I have an XTB-IIR in my house and on start-up the XTBM notes that I have a repeater. Line 1 on the LCD displays X4.31 F120k so I believe the XTB-IIR is really doing its job. Line 2 displays the last X10 command and VALID if the command was good.
Jeff, are there any particular stress tests you'd like me to run on the unit?
It looks like you have another winner. Thanks for creating the XTBM.
Greg
-
Assembled mine also. I thought that I was the only one that had installed the header upside down. For those intent on installing it backwards, be warned it's not an easy task getting it back out, and in doing so you'll probably destroy the part. I had to get a replacement header from Jeff.
-
I have an XTB-IIR in my house and on start-up the XTBM notes that I have a repeater. Line 1 on the LCD displays X4.31 F120k so I believe the XTB-IIR is really doing its job. Line 2 displays the last X10 command and VALID if the command was good.
That means the repeater ampltude at your location was 4.31Vpp, and the repeater is right on the money at 120KHz. Note that I had incorrectly kitted some units with a 4.99K 1% instead of 499 ohms 1%. The unit will read low if that resistor is the wrong value. Replacement resistors have been mailed.
I'm sorry that a couple of you installed the header wrong. I thought that would have been clear from the high resolution photo:
http://jvde.us/xtb/XTBM_v10_pcb.jpg
Thanks for being one of the first to assemble the unit.
Jeff
-
...I'm sorry that a couple of you installed the header wrong. I thought that would have been clear from the high resolution photo...
Well, clear to me versus clear to you, O Great One, can be two different things! rofl
Believe me, this was a case of operator error.
-
I'm sorry if the photo wasn't clear enough. Since a couple of you made the same mistake, I added a comment about the orientation in the assembly notes.
Please let me know if anything else was unclear. I hope to have time to create an expanded version of the assembly notes in the next week.
Regarding the display:
X is X10 signal voltage in Vpp
F is X10 or noise frequency in KHz
N is maximum noise seen in or immediately after the X10 reception window.
The decoded X10 commands should be obvious.
It displays "VALID" for two seconds after decoding a valid X10 command. Then it goes back to monitoring the powerline.
High noise is indicated by ^Noise^.
I will expand on this in the on line documentation in the next week or two.
Jeff
-
Documentation is up on the website now linked off the XTB page:
http://jvde.us/xtb_index.htm
I would appreciate any feedback from those of you who assembled the first kits. Once again I apologize for sending one wrong resistor value. I hope your units are working well now.
Any comments you have on the updated assembly notes or the instructions would also be appreciated:
http://jvde.us/xtb/XTBM_instructions.htm
http://jvde.us/xtb/XTBM_assembly.htm
Thanks,
Jeff
-
After the 4.99K resistor change to the correct 499 ohms my XTBM is working great! The assembly was easy. My only confusion was looking at the caps for conventional pf/mf value numbers. It took a few minutes to realize the numbers found on the caps are vendor part numbers, not values and tolerance.
I really like the P1 "Noise Alert" feature. I have our system now giving "house wide" verbal alerts "I have detected high system noise" if noise is detected during the day. The noise alert is logged but otherwise ignored at night. Makes tracking noise bursts much easier when you know the exact moment the burst occured.
The X10 community has needed this tool for a long, long time.
Thanks Jeff!!!
-
My only confusion was looking at the caps for conventional pf/mf value numbers. It took a few minutes to realize the numbers found on the caps are vendor part numbers, not values and tolerance.
Because of their small size, most manufacturers use short hand for the capacitor values. Just like 5% resistor color codes, 101 means 100 pF, 102 means 1000 pF, 103 means 10,000 pF or .01 uF, and so on.
The other side usually has codes for tolerance and temperature coefficient.
I'm glad the unit is working well for you now. That extra digit in the 1% color code got me.
Jeff
-
Got mine built today. Took me about 90 minutes or so to assemble. The only problem that I had was that the color bands on the resistors have gotten smaller and tend to blend together. Not to mention that it's hard to get those items in the holes on the board. Maybe if the kit were enlarged (and the components) it would be a little easier to put together.
-
Those components getting smaller is why I bought a 2x visor! :)
-
Buying a 2X visor would be admitting that I'm getting older.
-
I bought one of those bench lights with the saucer-size magnifier a couple of years ago, and it is a huge help for working with these small components.
Jeff
-
Anywho......
What's an acceptable noise level on that thing? My home indicates a level of 01 most of the time. Just for grins, I plugged a Chinese cell phone charger in next to it and got a level of 19-20 under no load, and somewhere near 40 under a load.
On another note, my Sears controller has an output signal of 5 to 7.2 when next to the XTBM, (which I assume is VERY good) while my CM15A give a reading of .17 across the house.
The .17 (F 118 [slight drift due to wiring?]) is perfectly fine for controlling devices.
Maybe we need a thread so others can compare notes?
-
One more thought.
Jeff,
While assembling the unit, I realized what kind of thought went into the design, testing, assembly notes and support.
Thank You
(Jeff sent me a new firmware version PIC right after he realized an issue with the self test mode.)
It's rare in this day and age to see a company that actually cares about a product after it's left their door.
It's my opinion that the price is extremely low for the time and effort put into it by one person, but then, I think the same for BVC and PC Companion.
-
Knight,
We are all getting older otherwise we would assume a body temperature of the room. rofl
I used my 2X visor AND my magnifier lamp AND an Ohm meter and I still got it wrong (more rofl ). My mistakes were not because kit is difficult to assemble, but because I just don't see well.
BTW, 90 minutes? You are good! I know some electronics manufactures who would be gleeful to hire you (bunches more rofl ). Again, my slowness was because of eyesight...guess I am going to have to quit postponing that cataract operation.
But the XTBM is one really neat machine! I love it. Jeff should package a " X10 Universal Home Automation Problem Solving Kit" (XUHAPSK ?) made up of a XTBIIR and a XTBM.
-
OK,
got to admit that my multi-tester was by my side on the resistors. I used to be able to whip through a Heath or Velleman kit while watching Jeopardy. Been building kits since before I got into X10 at the ripe old age of 13.
I needed a diesel horn for my train, had to etch the board myself (not anywhere near as good looking as the XTBM [should have used a straight edge])
BTW, Jeff alerted me to all you guys' that were ahead of me mistakes!
-
What's an acceptable noise level on that thing? My home indicates a level of 01 most of the time. Just for grins, I plugged a Chinese cell phone charger in next to it and got a level of 19-20 under no load, and somewhere near 40 under a load.
On another note, my Sears controller has an output signal of 5 to 7.2 when next to the XTBM, (which I assume is VERY good) while my CM15A give a reading of .17 across the house.
.01 for noise is very good. Here I read .01 to .02 most of the time. At .05 a nearby appliance module can begin missing commands. However, it really depends on the character of the noise. .05 (50mVpp) sitting right at 120KHz would be worse that 20 (200mVpp) far enough outside the X10 band to be pretty much rejected by the module filter. The XTBM does have peak sensitivity at 120KHz, so noise at that frequency will produce the highest reading.
I would suggest that any time the noise reads over .05, it is worth spending some time to identify the cause and isolate it with an appropriate filter.
I have found that X10 devices work reliably down to 100mVpp (.10 on the display). Below that things become marginal. FYI, my Maxi Controllers (OLD boxy Sears unit and a newer Leviton unit) also read around 7Vpp when sampled directly at the same power strip.
90 minutes is a very good assembly time.
Thank you all for the feedback.
Jeff