Renard Wireless Converter - Revision history

Dirknerkle: Added preliminary note at the top of the page.

2019-11-12T21:16:09Z

Added preliminary note at the top of the page.

← Older revision		Revision as of 21:16, 12 November 2019
Line 1:		Line 1:
	:[[File:Ren-w_complete.JPG\|330px ]]		:[[File:Ren-w_complete.JPG\|330px ]]

			'''NOTE 11/12/2019: This documentation is now 10-years old and some concepts written in these pages no longer apply. DIGI has new configuration software for the XBee radios and in addition, the XBee firmware has changed, too. To add insult to injury, the new Vixen and XLights sequencers do not support MARK parity, so throughout this documentation, set parity to NONE instead. With the advent of the inexpensive ESP8266 module, wireless control seems to be shifting to Wi-Fi networking, but XBee can still be a viable wireless control option for many DIY'ers. XBee has greater range and is less affected by the communication issues and conflicts that Wi-Fi presents.'''

Dirknerkle: /* Why a Wireless Converter? */

2013-05-24T19:59:41Z

Why a Wireless Converter?

← Older revision		Revision as of 19:59, 24 May 2013
Line 6:		Line 6:
	:Sometimes it's not practical, affordable or maybe even possible to lay physical cable to a particular light controller. For example, trenching beneath your driveway to put a megatree on the other side is a messy, dirty and potentially expensive project. Or let's say you have a pond behind your house and you'd like to put a display on the bank on the other side where there's already an electrical connection for a circulating fountain. Or maybe your neighbor across the street wants you to help him light his house -- trenching beneath a street or suspending cable above it would probably require multiple permits from your local municipality, if it were allowed at all. Maybe you've built a new house and you don't want to leave a window open so all the cables can be routed through it to the outside. Or perhaps you live in an apartment building or rented condo where drilling a hole through the wall isn't even an option. These are just some examples of instances where a wireless connection to your outside Renard controller could very likely be the simplest and most affordable choice. That's why the Ren-W was invented.		:Sometimes it's not practical, affordable or maybe even possible to lay physical cable to a particular light controller. For example, trenching beneath your driveway to put a megatree on the other side is a messy, dirty and potentially expensive project. Or let's say you have a pond behind your house and you'd like to put a display on the bank on the other side where there's already an electrical connection for a circulating fountain. Or maybe your neighbor across the street wants you to help him light his house -- trenching beneath a street or suspending cable above it would probably require multiple permits from your local municipality, if it were allowed at all. Maybe you've built a new house and you don't want to leave a window open so all the cables can be routed through it to the outside. Or perhaps you live in an apartment building or rented condo where drilling a hole through the wall isn't even an option. These are just some examples of instances where a wireless connection to your outside Renard controller could very likely be the simplest and most affordable choice. That's why the Ren-W was invented.

	::NOTES: In the years since this documentation was originally created, the physical Ren-W board has undergone a few revisions. Even so, the construction methodology hasn't changed and the concepts expressed in this WIKI continue to hold true. The antenna configurations of the XBee radios and the configuration setup of the XBee radios with XCTU software have not changed either, and the documents here should stand in good stead for a long time to come.		::'''NOTES:''' In the years since this documentation was originally created, the physical Ren-W board has undergone a few revisions. Even so, the construction methodology hasn't changed and the concepts expressed in this WIKI continue to hold true. The antenna configurations of the XBee radios and the configuration setup of the XBee radios with XCTU software have not changed either, and the documents here should stand in good stead for a long time to come.

	::It is highly suggested that instead of cherrypicking bits of information here and there, the reader should go through everything at least once to get a flavor for what wireless is all about. The Q&A and Troubleshooting sections solve most of the questions that users have had, and the section about antennas covers the various XBee antenna types quite thoroughly. Lastly, the Renard Start Address firmware is absolutely the right tool to accompany wireless operation. The Start Address guide is really a closely-knit companion piece to the Ren-W information.		::It is highly suggested that instead of cherrypicking bits of information here and there, the reader should go through everything at least once to get a flavor for what wireless is all about. The Q&A and Troubleshooting sections solve most of the questions that users have had, and the section about antennas covers the various XBee antenna types quite thoroughly. Lastly, the Renard Start Address firmware is absolutely the right tool to accompany wireless operation. The Start Address guide is really a closely-knit companion piece to the Ren-W information.

Dirknerkle: /* Why a Wireless Converter? */

2013-05-24T19:58:09Z

Why a Wireless Converter?

← Older revision		Revision as of 19:58, 24 May 2013
Line 6:		Line 6:
	:Sometimes it's not practical, affordable or maybe even possible to lay physical cable to a particular light controller. For example, trenching beneath your driveway to put a megatree on the other side is a messy, dirty and potentially expensive project. Or let's say you have a pond behind your house and you'd like to put a display on the bank on the other side where there's already an electrical connection for a circulating fountain. Or maybe your neighbor across the street wants you to help him light his house -- trenching beneath a street or suspending cable above it would probably require multiple permits from your local municipality, if it were allowed at all. Maybe you've built a new house and you don't want to leave a window open so all the cables can be routed through it to the outside. Or perhaps you live in an apartment building or rented condo where drilling a hole through the wall isn't even an option. These are just some examples of instances where a wireless connection to your outside Renard controller could very likely be the simplest and most affordable choice. That's why the Ren-W was invented.		:Sometimes it's not practical, affordable or maybe even possible to lay physical cable to a particular light controller. For example, trenching beneath your driveway to put a megatree on the other side is a messy, dirty and potentially expensive project. Or let's say you have a pond behind your house and you'd like to put a display on the bank on the other side where there's already an electrical connection for a circulating fountain. Or maybe your neighbor across the street wants you to help him light his house -- trenching beneath a street or suspending cable above it would probably require multiple permits from your local municipality, if it were allowed at all. Maybe you've built a new house and you don't want to leave a window open so all the cables can be routed through it to the outside. Or perhaps you live in an apartment building or rented condo where drilling a hole through the wall isn't even an option. These are just some examples of instances where a wireless connection to your outside Renard controller could very likely be the simplest and most affordable choice. That's why the Ren-W was invented.

	:NOTES: In the years since this documentation was originally created, the physical Ren-W board has undergone a few revisions. Even so, the construction methodology hasn't changed and the concepts expressed in this WIKI continue to hold true. The antenna configurations of the XBee radios and the configuration setup of the XBee radios with XCTU software have not changed either, and the documents here should stand in good stead for a long time to come.		::NOTES: In the years since this documentation was originally created, the physical Ren-W board has undergone a few revisions. Even so, the construction methodology hasn't changed and the concepts expressed in this WIKI continue to hold true. The antenna configurations of the XBee radios and the configuration setup of the XBee radios with XCTU software have not changed either, and the documents here should stand in good stead for a long time to come.

	:It is highly suggested that instead of cherrypicking bits of information here and there, the reader should go through everything at least once to get a flavor for what wireless is all about. The Q&A and Troubleshooting sections solve most of the questions that users have had, and the section about antennas covers the various XBee antenna types quite thoroughly. Lastly, the Renard Start Address firmware is absolutely the right tool to accompany wireless operation. The Start Address guide is really a closely-knit companion piece to the Ren-W information.		::It is highly suggested that instead of cherrypicking bits of information here and there, the reader should go through everything at least once to get a flavor for what wireless is all about. The Q&A and Troubleshooting sections solve most of the questions that users have had, and the section about antennas covers the various XBee antenna types quite thoroughly. Lastly, the Renard Start Address firmware is absolutely the right tool to accompany wireless operation. The Start Address guide is really a closely-knit companion piece to the Ren-W information.

	== '''Overview''' ==		== '''Overview''' ==

Dirknerkle: /* Why a Wireless Converter? */

2013-05-24T19:57:41Z

Why a Wireless Converter?

← Older revision		Revision as of 19:57, 24 May 2013
Line 6:		Line 6:
	:Sometimes it's not practical, affordable or maybe even possible to lay physical cable to a particular light controller. For example, trenching beneath your driveway to put a megatree on the other side is a messy, dirty and potentially expensive project. Or let's say you have a pond behind your house and you'd like to put a display on the bank on the other side where there's already an electrical connection for a circulating fountain. Or maybe your neighbor across the street wants you to help him light his house -- trenching beneath a street or suspending cable above it would probably require multiple permits from your local municipality, if it were allowed at all. Maybe you've built a new house and you don't want to leave a window open so all the cables can be routed through it to the outside. Or perhaps you live in an apartment building or rented condo where drilling a hole through the wall isn't even an option. These are just some examples of instances where a wireless connection to your outside Renard controller could very likely be the simplest and most affordable choice. That's why the Ren-W was invented.		:Sometimes it's not practical, affordable or maybe even possible to lay physical cable to a particular light controller. For example, trenching beneath your driveway to put a megatree on the other side is a messy, dirty and potentially expensive project. Or let's say you have a pond behind your house and you'd like to put a display on the bank on the other side where there's already an electrical connection for a circulating fountain. Or maybe your neighbor across the street wants you to help him light his house -- trenching beneath a street or suspending cable above it would probably require multiple permits from your local municipality, if it were allowed at all. Maybe you've built a new house and you don't want to leave a window open so all the cables can be routed through it to the outside. Or perhaps you live in an apartment building or rented condo where drilling a hole through the wall isn't even an option. These are just some examples of instances where a wireless connection to your outside Renard controller could very likely be the simplest and most affordable choice. That's why the Ren-W was invented.

			:NOTES: In the years since this documentation was originally created, the physical Ren-W board has undergone a few revisions. Even so, the construction methodology hasn't changed and the concepts expressed in this WIKI continue to hold true. The antenna configurations of the XBee radios and the configuration setup of the XBee radios with XCTU software have not changed either, and the documents here should stand in good stead for a long time to come.

			:It is highly suggested that instead of cherrypicking bits of information here and there, the reader should go through everything at least once to get a flavor for what wireless is all about. The Q&A and Troubleshooting sections solve most of the questions that users have had, and the section about antennas covers the various XBee antenna types quite thoroughly. Lastly, the Renard Start Address firmware is absolutely the right tool to accompany wireless operation. The Start Address guide is really a closely-knit companion piece to the Ren-W information.

	== '''Overview''' ==		== '''Overview''' ==

Chelmuth: /* Renard basics and how they relate to Ren-W */

2012-10-07T03:04:31Z

Renard basics and how they relate to Ren-W

← Older revision		Revision as of 03:04, 7 October 2012
Line 33:		Line 33:
	:To make two (or more) Renard controllers respond identically with the same Vixen commands, Vixen users usually replicate the Vixen channel information that controls one Renard to the corresponding channels that control the other Renards. However, what if you could use a “signal splitter” cable that distributed the same serial signal to multiple controllers, not unlike the concept of a “multi-outlet serial plug strip?” (Splitting an actual, stock serial signal to multiple devices without additional amplification is certainly possible but is generally a discouraged practice – the concept is used here for the illustration.) With such a splitter, each SS controller plugged into the “multi-outlet serial strip” would receive exactly the same channel information at the same time, just as if each was connected directly to the computer’s serial port. In the 32-channel example above however, since the SS8 has only 8 channels, it would be able to use only Vixen channels 1-8 while the SS24 would be able to use channels 1-24, ''and channels 25-32 would not be used by either controller.'' The “serial signal splitter” concept can be accomplished wirelessly quite easily; Ren-W refers to this as ''“Global Broadcasting.”''		:To make two (or more) Renard controllers respond identically with the same Vixen commands, Vixen users usually replicate the Vixen channel information that controls one Renard to the corresponding channels that control the other Renards. However, what if you could use a “signal splitter” cable that distributed the same serial signal to multiple controllers, not unlike the concept of a “multi-outlet serial plug strip?” (Splitting an actual, stock serial signal to multiple devices without additional amplification is certainly possible but is generally a discouraged practice – the concept is used here for the illustration.) With such a splitter, each SS controller plugged into the “multi-outlet serial strip” would receive exactly the same channel information at the same time, just as if each was connected directly to the computer’s serial port. In the 32-channel example above however, since the SS8 has only 8 channels, it would be able to use only Vixen channels 1-8 while the SS24 would be able to use channels 1-24, ''and channels 25-32 would not be used by either controller.'' The “serial signal splitter” concept can be accomplished wirelessly quite easily; Ren-W refers to this as ''“Global Broadcasting.”''

	:A version of Renard firmware is available that makes "global broadcasting" possible while still retaining individual channel control. The firmware is an ideal match for the Ren-W and uses a "start address" concept where you set the starting channel number for the controller(s). For more information read the configuration guide: [http://www.~~christmasinshirley~~.com/wiki/index.php?title=Renard_Start_Address_Configuration_Guide Start Address Configuration Guide]		:A version of Renard firmware is available that makes "global broadcasting" possible while still retaining individual channel control. The firmware is an ideal match for the Ren-W and uses a "start address" concept where you set the starting channel number for the controller(s). For more information read the configuration guide: [http://www.doityourselfchristmas.com/wiki/index.php?title=Renard_Start_Address_Configuration_Guide Start Address Configuration Guide]

	== '''XBee Wireless Radio Module Basics''' ==		== '''XBee Wireless Radio Module Basics''' ==

Dirknerkle: /* Signal Propagation Delay */

2012-04-24T00:46:53Z

Signal Propagation Delay

← Older revision		Revision as of 00:46, 24 April 2012
Line 48:		Line 48:
	== '''Signal Propagation Delay''' ==		== '''Signal Propagation Delay''' ==

	:An XBee module can require up to 6ms to process received data; normally it's 2-3ms. While this is a very short period of time, consider that the delay is cumulative when multiple Ren-W nodes are configured in repeater mode. For example, in a Ren-W network of 5 nodes, the last SS controller could be nearly 30ms late in reacting to Vixen control commands. This may not be very perceptible in some situations but in others, it could become quite noticeable and the delay should be factored into the general design of a Ren-W network, and possibly during the light sequencing design as well. Note that in global broadcast mode, the delay is [[not]] cumulative as all receiving Ren-Ws ~~would~~ receive the Vixen commands simultaneously and each unit would only be 2-3ms (or less) late. In actual testing, ~~the~~ delay ~~was~~ virtually undetectable ~~to the naked eye~~.		:An XBee module can require up to 6ms to process received data; normally it's 2-3ms. While this is a very short period of time, consider that the delay is cumulative when multiple Ren-W nodes are configured in repeater mode. For example, in a Ren-W network of 5 nodes, the last SS controller could be nearly 30ms late in reacting to Vixen control commands. This may not be very perceptible in some situations but in others, it could become quite noticeable and the delay should be factored into the general design of a Ren-W network, and possibly during the light sequencing design as well. Note that in global broadcast mode, the delay is not cumulative as all receiving Ren-Ws receive the Vixen commands simultaneously and each unit would only be 2-3ms (or less) late. In actual testing, whatever delay may exist in global broadcast mode is virtually undetectable.

	== '''Selecting the right XBee Modules - Which Do I Need?''' ==		== '''Selecting the right XBee Modules - Which Do I Need?''' ==

Dirknerkle: /* Signal Propagation Delay */

2012-04-24T00:44:57Z

Signal Propagation Delay

← Older revision		Revision as of 00:44, 24 April 2012
Line 48:		Line 48:
	== '''Signal Propagation Delay''' ==		== '''Signal Propagation Delay''' ==

	:An XBee module can require up to 6ms to process received data. While this is a very short period of time, consider that the delay is cumulative when multiple Ren-W nodes are configured in repeater mode. For example, in a Ren-W network of 5 nodes, the last SS controller could be nearly 30ms late in reacting to Vixen control commands. This may not be very perceptible in some situations but in others, it could become quite noticeable and the delay should be factored into the general design of a Ren-W network, and possibly during the light sequencing design as well. Note that in global broadcast mode, the delay is not cumulative as all receiving Ren-Ws would receive the Vixen commands simultaneously and each unit would only be ~~6ms~~ (or less) late. In actual testing, the delay was virtually undetectable to the naked eye.		:An XBee module can require up to 6ms to process received data; normally it's 2-3ms. While this is a very short period of time, consider that the delay is cumulative when multiple Ren-W nodes are configured in repeater mode. For example, in a Ren-W network of 5 nodes, the last SS controller could be nearly 30ms late in reacting to Vixen control commands. This may not be very perceptible in some situations but in others, it could become quite noticeable and the delay should be factored into the general design of a Ren-W network, and possibly during the light sequencing design as well. Note that in global broadcast mode, the delay is [[not]] cumulative as all receiving Ren-Ws would receive the Vixen commands simultaneously and each unit would only be 2-3ms (or less) late. In actual testing, the delay was virtually undetectable to the naked eye.

	== '''Selecting the right XBee Modules - Which Do I Need?''' ==		== '''Selecting the right XBee Modules - Which Do I Need?''' ==

Dirknerkle: /* Compatibility with various Renard Controllers */

2012-04-24T00:43:04Z

Compatibility with various Renard Controllers

← Older revision		Revision as of 00:43, 24 April 2012
Line 22:		Line 22:
	:* Frank Kostyun's Ren24, versions 3.0 and 3.3, and the Ren24LV		:* Frank Kostyun's Ren24, versions 3.0 and 3.3, and the Ren24LV
	:* Budude's Ren48LSD v3b		:* Budude's Ren48LSD v3b
	:* Renard Simple24 and Renard Simple32		:* Renard Simple24 and Renard Simple32 by Mactayl and TStraub
			:* CTMal's RenServo
	:* Other Renard boards that use similar serial input/output circuitry should also work.		:* Other Renard boards that use similar serial input/output circuitry should also work.
	:* The following serial port parameters are highly suggested: Baud: 57600, Parity: Mark, Stop bits: 2		:* The following serial port parameters are highly suggested: Baud: 57600, Parity: Mark, Stop bits: 2

Dirknerkle: /* Overview */

2012-04-24T00:41:27Z

Overview

← Older revision		Revision as of 00:41, 24 April 2012
Line 11:		Line 11:
	:Ren-W is an inexpensive, compact (3”H x 2.5”W), easy-to-build and configure plug-in wireless adapter for Renard controllers and 595/Grinch systems that use Ren-C (see Ren-C note below). It can also be used with other Renard controllers with very slight modifications to the controllers to tap +5v power for the Ren-W. The Ren-W functions as a transparent serial connection between Renard controllers by converting RS-485 serial data into a digital stream, transmitting it wirelessly to another Ren-W where the digital stream is recombined into serial data and fed into the Renard controller’s normal RJ45 input jack (J2) via short cat5 cable, just like it would have been had the computer been hard-wired directly to the controller. In a typical Renard daisy chain design, channel data that a Renard controller can’t use is passed through and out the controller’s data-out RJ45 jack (J1) as RS-485 data, which is then fed back into the Ren-W, retransmitted to the next Ren-W that’s supposed to receive it, where the digital stream is recombined into serial data, etc. and the process is repeated for as many Ren-W adapters as are in the chain. The Ren-W uses inexpensive yet powerful XBee Pro wireless radio modules to perform the actual wireless transmission/reception functions. The cost to build a single Ren-W board varies from about $27 to $73, depending on the various electronic components chosen.		:Ren-W is an inexpensive, compact (3”H x 2.5”W), easy-to-build and configure plug-in wireless adapter for Renard controllers and 595/Grinch systems that use Ren-C (see Ren-C note below). It can also be used with other Renard controllers with very slight modifications to the controllers to tap +5v power for the Ren-W. The Ren-W functions as a transparent serial connection between Renard controllers by converting RS-485 serial data into a digital stream, transmitting it wirelessly to another Ren-W where the digital stream is recombined into serial data and fed into the Renard controller’s normal RJ45 input jack (J2) via short cat5 cable, just like it would have been had the computer been hard-wired directly to the controller. In a typical Renard daisy chain design, channel data that a Renard controller can’t use is passed through and out the controller’s data-out RJ45 jack (J1) as RS-485 data, which is then fed back into the Ren-W, retransmitted to the next Ren-W that’s supposed to receive it, where the digital stream is recombined into serial data, etc. and the process is repeated for as many Ren-W adapters as are in the chain. The Ren-W uses inexpensive yet powerful XBee Pro wireless radio modules to perform the actual wireless transmission/reception functions. The cost to build a single Ren-W board varies from about $27 to $73, depending on the various electronic components chosen.

			== '''DMX''' ==
	:Ren-W is NOT compatible with DMX systems as DMX requires data speeds upwards of 250kbps. The XBee radio that Ren-W uses for wireless communication cannot support streaming data at that speed; it tops out at around 80kbps, which means that 57,600 baud is the highest communication speed Ren-W can support.		:Ren-W is NOT compatible with DMX systems as DMX requires data speeds upwards of 250kbps. The XBee radio that Ren-W uses for wireless communication cannot support streaming data at that speed; it tops out at around 80kbps, which means that 57,600 baud is the highest communication speed Ren-W can support.

Dirknerkle: /* Overview */

2012-04-24T00:40:46Z

Overview

← Older revision		Revision as of 00:40, 24 April 2012
Line 9:		Line 9:
	== '''Overview''' ==		== '''Overview''' ==

	:Ren-W is an inexpensive, compact (3”H x 2.5”W), easy-to-build and configure plug-in wireless adapter for Renard SS controllers and 595/Grinch systems that use Ren-C (see Ren-C note below). It can also be used with other Renard controllers with very slight modifications to the controllers to tap +5v power for the Ren-W. The Ren-W functions as a transparent serial connection between Renard controllers by converting RS-485 serial data into a digital stream, transmitting it wirelessly to another Ren-W where the digital stream is recombined into ~~RS-232~~ serial data and fed into the Renard controller’s normal RJ45 input jack (J2) via short cat5 cable, just like it would have been had the computer been hard-wired directly to the controller. In a typical Renard daisy chain design, channel data that a Renard controller can’t use is passed through and out the controller’s data-out RJ45 jack (J1) as RS-485 data, which is then fed back into the Ren-W, retransmitted to the next Ren-W that’s supposed to receive it, where the digital stream is recombined into serial data, etc. and the process is repeated for as many Ren-W adapters as are in the chain. The Ren-W uses inexpensive yet powerful XBee Pro wireless radio modules to perform the actual wireless transmission/reception functions. The cost to build a single Ren-W board varies from about $27 to $73, depending on the various electronic components chosen.		:Ren-W is an inexpensive, compact (3”H x 2.5”W), easy-to-build and configure plug-in wireless adapter for Renard controllers and 595/Grinch systems that use Ren-C (see Ren-C note below). It can also be used with other Renard controllers with very slight modifications to the controllers to tap +5v power for the Ren-W. The Ren-W functions as a transparent serial connection between Renard controllers by converting RS-485 serial data into a digital stream, transmitting it wirelessly to another Ren-W where the digital stream is recombined into serial data and fed into the Renard controller’s normal RJ45 input jack (J2) via short cat5 cable, just like it would have been had the computer been hard-wired directly to the controller. In a typical Renard daisy chain design, channel data that a Renard controller can’t use is passed through and out the controller’s data-out RJ45 jack (J1) as RS-485 data, which is then fed back into the Ren-W, retransmitted to the next Ren-W that’s supposed to receive it, where the digital stream is recombined into serial data, etc. and the process is repeated for as many Ren-W adapters as are in the chain. The Ren-W uses inexpensive yet powerful XBee Pro wireless radio modules to perform the actual wireless transmission/reception functions. The cost to build a single Ren-W board varies from about $27 to $73, depending on the various electronic components chosen.

	:Ren-W is NOT compatible with DMX systems as DMX requires data speeds upwards of 250kbps. The XBee radio that Ren-W uses for wireless communication cannot support streaming data at that speed; it tops out at around 80kbps, which means that 57,600 baud is the highest communication speed Ren-W can support.		:Ren-W is NOT compatible with DMX systems as DMX requires data speeds upwards of 250kbps. The XBee radio that Ren-W uses for wireless communication cannot support streaming data at that speed; it tops out at around 80kbps, which means that 57,600 baud is the highest communication speed Ren-W can support.