August 27, 2014

Troubleshooting the Wireless Pulse Counter

In most cases the Wireless Pulse Counter is just plug and play. But if you do have problems getting readings from your Wireless Pulse Counter, please have a look at this trouble shooting guideline.
I will update this post when needed.

First. Make sure your Tellstick DUO/NET have a firmware equal to, or higher than 12 for DUO or 17 for NET or 79 for RFXtrx433. Here is more information for the Tellsticks, http://developer.telldus.com/blog/2014/04/03/tellduscenter_2.1.2. In this firmware version there has been a correction in the Fineoffset protocol that enables the checksum feature in the protocol. This will ensure that you do not get any false readings.


The WPC does not show up in TelldusCenter (or similar):
  • Make sure that the LED on the WPC is blinking once every minute. The LED blink when it transmit data. Even if it has not detected any blinks.
  • Make sure that the Tellstick blinks at the same time the WPC LED blink. This indicates that the Tellstick have received and decoded the data.

The WPC show up in TelldusCenter (or similar), but the counter value is not changing:
  • Make sure that the "eye" of the WPC can receive pulses. Aim a standard TV-remote to the "eye" and press a button. Make sure that you do this where there is very dim light. The next transmission you get should then be seen as an increased value.
  • If the LED blinks more often than once every minute. If it blinks every 10 seconds or so. Then it is likely that you use a USB power pack that is too "smart" for the WPC. Some of the power packs automatically shut down if there is no load. The WPC draws so little power that some of the power packs thinks that nothing is connected and turns off and on. When it restarts all the time, it will always send the same value.

The WPC show up in TelldusCenter (or similar), but the counter value is unreasonably high:
  • It is likely that there are false detections. This could be due to light coming in from the sides of the WPC and the Electric meter. Use for example styrofoam to make a tight mounting. Cut out a sheet and make a small hole for the WPC "eye" (the phototransistor) and place it all right on top of the LED on the Electric meter.

August 20, 2014

WMS Mk2 - Currently supported devices

Here is a list of currently supported devices (WMS Mk2 sold after August 1st, 2014).
http://foogadgets.tictail.com

EDIT (2014-09-15): I have removed the support for DS276X since the configuration of the chip and also the extra calculations needed to present a valid sensor reading, was too complex.
To read Thermocouples I recommend the MAX31850 instead.


1-wire networks could be big as long as they are well built. The WMS Mk2 has successfully been tested in a network with 33 sensors and 75m length.


August 13, 2014

New Firmware and Manual for the WMS Mk2

Just before the summer vacations I finalized the Wireless Multi-sensor Mk2 firmware that I have been working with for quite some time.

News,

  • CO2 sensor S8 from SenseAir is now supported. It can be connected to the Event Input after changing the input mode of the Event Input (c.f. Manual). You can get the CO2-sensor here.
  • MAX31850K support. This chip is a Thermocouple Type K to 1-wire chip. This makes it possible to make a Type K thermocouple wireless. It can output 409.6°C as the highest temperature. It is a limitation set by the protocol I use. Here you can find a MAX31850K-module, m.nu.
  • DS2450 support. This is a 4 channel AD converter. All 1-wire sensors based on this chip will be compatible with the WMS Mk2. This,  this, this, this and this is also compatible modules since they are based on the DS2450 chip.

Improvements,

  • Events are now sent as a LMST-606 device. An ON or OFF signal will be sent depending on if the input pin is pulled up or pulled down.
  • The Manual is out in a first revision.

All Wireless Multi-sensors Mk2 will be shipped with this new firmware from now on.