Xenta 121 manual

I2C Transfer Board. M8N GPS. Baitboat Solutions. Telemetry Module. After-Sales Service Policies. Messages Online.

Where to Buy Parts. Upgrade Firmwares. Parameter Setup APPs. Mission Planner. Manuals in PDF. More Services. Download Center. Tutorial Videos. Tutorial Manuals. Manuals Online. Help Center. Tech Support. About RadioLink. Company Culture. Contact Us. Who We Are. Company News. Industry News. Media Reports. About Transmitter. Login Register Logout. Buy Now. Features of F As the mini racing drone that can fly at high speed at Altitude Hold Mode, F is very easy to master for drone freshman. Remote Controller The two joysticks of T8S correspond to the four basic channels respectively.

Left joystick Make the F rise or descend by toggling the left stick vertically upward or downward and rotate clockwise or anticlockwise by toggling the left stick to the left or right. Right joystick Make the F fly forward or backward by toggling the right stick vertically upward or downward and turn left or right by toggling the right stick to the left or right. Propellers Installation F is installed with propellers protector by factory default.

Put on the propeller protector from the bottom and adjust the position of the notches correspondingly. Stabilize the frame with left hand and buckle the notch of one side with right hand. Then buckle the notch of the other side with left hand. Put F on a level surface and do not move it when the green LED is flashing. Orange propellers indicates the head of F by default. The green LED of F will begin flashing when powered on. Place the T8FB and F close to each other within 50 centimeters.

Power on the T8FBand F The binding is complete when the LED is always on. Make sure F is armed Details in next section. Gently push the throttle of transmitter to see if motors move.

How to Disarm When the flight is finished, always make sure F is disarmed when get close and try touching it to avoid unexpected harm. At Altitude Mode:Hover Push the throttle joystick vertically upward till the F rises to a height as wish, then toggle it back to center position and release, the F will hover at this height. Image Transmission of F The image transmission device of Fis 5. That is, transmission off. The transmission distance is m. Power and Channel Frequency After powering on, wait for 10 seconds to initialize, red and blue and yellow always on means normal working status.

About Us. Drone Racing World Cup. Become a Dealer. After-Sales Service. Repair Service. Old to New. Drone Competition. Help Purchasing. Where to Buy. Aircraft Transmitters. Flight Controller System. RadioLink Online Store. Read our Privacy Policy. Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website.

Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.

Necessary Necessary. Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website.

Use Connector to make a direct connection between the corresponding input and output signals. However, this works only when binding between function blocks situated on the same page. Select two or more function blocks click on the first, then keep the Shift bar pressed when clicking on the rest , click right, select Connect. Normal means that you will get a line drawn between the function blocks recommended within the same page.

References means that you will get a number referring to another position in the network, where you will find the same number. This pair of numbers may be altered to a designation of your own choice. References are always used when the function blocks reside on different pages. As we already have split up the network into a number of pages, we recommend the latter method.

If the binding lies within the same page use Normal, otherwise References. Should this be the case, you must add a dummy node to one of the groups, in order to produce two different group bindings.

The first group binding gets group address 0, and then in ascending order. In order to determine which address a group binding will get, you must see to that this binding is made first of all. In practice, this may be difficult to achieve, so to find out which group addresses the bindings received, you can do as follows. If you click right on a unit in on-line mode and select Device Properties you can under the header Address Table see the address table of the unit, containing information about messages to and from the unit.

In the column ID you will find the current group address for the binding. In the example above the TAC group received group address 3. Deselect this box in order to leave the group addressing to LM3. As this binding was the first made in this network, it was assigned group no. Specify this in TAC Vista. Rightclick and select Connect. At least three nodes are required to produce a group binding; otherwise you have to add a dummy unit.

If there are several in the same window, then click on the first, keep the Shift-key pressed when you click on the next Function Block. Rightclick and then select Connect. Are you going to bind a signal between more than two units? First find out which end will be single, that is, will you send one-to-many or many-to-one?

This will determine which is Hub and which is Target. Hub is the single end, select the correct Subsystem - Device and NV. At Target only NVs of the correct type will appear, that is, the same types as selected for Hub. Click on Add to add the binding. If necessary, select a new Target to bind the same signal to more units. Do not forget to Add each new one. If you select a signal and click on Add All the corresponding binding will be made for all the selected units to NVs that have that same name.

Do not forget, however, to check under Connection that the correct signal was selected, before you apply the binding by clicking OK.

If the bindings appear on the same page you may use Graphics Normal. If the units reside on different pages, the binding will automatically be done using references Use References. Did you miss some nodes that also were to receive the same signal?

As there are no more than 15 table lines at the most for each node, you will soon run out of address lines even in small-sized networks. If you need to send more messages, you may in LM3 create a special type of binding, using the so called broadcast message. Characteristics for this type of messages are: Only one address the subnet address is used in the sending node, in spite of the fact that the transmission is for several nodes.

Message acknowledge cannot be requested. It is not possible to identify the receiving nodes, using a line analyzer. The message is a broadcast message, meaning that every single node listens.

The message is then ignored by nodes that do not belong to this binding. This means that a broadcast requires a larger bandwidth than a normal binding. If the broadcast crosses several Subnets, it may become a Domain broadcast, reaching the whole network.

Working method 1 Choose those nodes between which you wish to bind, rightclick and select Connect. Click on the Properties When the new binding type has been created, you can henceforth select it under Connection Attributes, New Connections:. Depending on the extent of the network, it may be more convenient to bring along the PC with the database to the site, treating one area at a time.

In this case you may either move the LNS Network Interface symbol to the drawing with the intended channel, or let the system redraw the intended channel connection in the page where the LNS symbol already resides. Make sure that Network Attached is indicated normal case during commissioning.

Enter the items for the intended destination and confirm that the PC has been moved, in the Move devices and routers window. If the routers are missing at this stage, or if you do not wish to install them right now, then specify them as Repeaters, otherwise you will get no contact between the channels.

Click right on the router, select Properties. Under the tab Advanced Properties you will find the settings for the type of router you have got. As the TAC Xenta units are Host-based, that is, the application does not reside in the neuron but outside, you are not to download the application via the network management tool. State Determine what State the unit should have directly after the installation. Also specify which values are to used here: Current values in database. As we chose On-line when creating the network, we do not have to set this for each unit.

Now we have to press the Service pin on the proper unit. Unless you selected the manual neuron ID entry; then the service pin will not be used! Another method is described below. The principle is to install one channel at a time.

It may be convenient to bring the PC to the selected channel, in order not to work against the whole network. How to move the Network interface has been described earlier in this chapter. If you have unique units, that is, each unit has a unique program ID, test the Auto Match; then you will not even have to look up the units! Go to the current Subsystem. Select LonMaker - Discover Devices. Device Selection Scope Decide if you want to work with The current subsystem only or The current subsystem and its dependent subsystems.

If the units reside on the other side of a repeater or a Router configured as a repeater , you may in Options have to checkmark the box Allow channel override. Options Checkmark the boxes Match using location string, Display location as text and Enable service pin matching.

Defined Devices Choose a unit in the list Defined Devices, by clicking on the Subsystem of the respective unit. After that, you press the Service pin of the corresponding unit. The unit will now move down to the list Devices to be Commissioned. This will select the nodes sequentially as you press Service Pin. Note the order of the units in the list and then seek out to the respective units in the same order!

Check that you have matched the correct unit with the corresponding Neuron ID before you click Finish and the units will be installed. If there is a checkmark that is, an external binding tool will be used no addressing will be done on the zero-length domain, that is, TAC Xenta will only listen on the application domain. In this case the group addresses will reside in the LNS data base and they will be transferred to the nodes at the installation.

Otherwise you may risk an address conflict. LM3 will use a whole set of different address values, but this is no drawback and will help us avoid address conflicts at a later stage. Try to use high subnet values, to minimise the risk of having the same subnet number on both sides of a router.

Uncheck the Download group addresses and perform another download. Also used by As hardware type 1 has another type of Neuron, which cannot be installed in a correct way, hardware type 1 must never be used together with LM3. If you wish to program the network off-line, all XIF files must be available. Starting with version 3.

It must not be moved around in the network, as you then may risk that the OP with its old subnet number will be put on another channel. The same subnet number must never appear on both sides of a router, as the router then will stop communicating.

This is done in order to find out which unit the OP communicates with. As the OP does not belong to the zero length domain no contact will be established. However, this request will be sent on the zero length domain.

This request will be sent on the zero length domain. As a standard the domain ID 11 hex is used and we recommend that you keep to this domain address. Please note that the 1-byte domain address 00 is not the same as the zero length domain. When a TAC Xenta OP is connected to the network, it will automatically look for a free address on subnet , node 70 or higher. Is no free address available, the OP will fall silent, not to disturb the network traffic.

If a node address is available the OP will use it. Subnet can be used on both sides of those Routers that TAC has used. Be careful though, as this is not according to standard. Should problems arise, you will have to install the OP permanently as described above. This is done in order to make sure which unit the OP communicates with.

System program lower than 3. System program 3. Disconnect the OP electrically. Remove the OP from the LM3 data base.

Therefore, you may be asked if you wish to rename the Device Template file, when adding a unit. As it should be easy to detect which unit uses which Device Template, your answer will depend on the circumstances. Among things reported are units without Neuron ID that is, units that have not yet been commissioned , units off-line etc. Specify if you want to check the status of the Entire Network, of the current Subsystem Hierarchy or only of the current Subsystem Page.

In spite of this, you should Set All, as there may be other units in the network that may have things to report. Checkmarking the Advanced options box will give you further options for the presented information. Click Get Now to examine the network. If everything is on-line and working, you will only get a text Summary includes If there are problems, the corresponding node will be shown in the lower window with a text indicating the type of problem.

In the upper window the status of the Functional Blocks is shown. This is specially true when you are about to modify something in the network, so that it will be easy to restore the earlier, working status.

A corresponding choice is made when you want to restore your network with the command Restore. To document all objects, bindings, etc. Unfortunately the collected information is hard to survey and, possibly, too extensive.

If, on the other hand, the new application does affect the SNVT contents, we have another situation. Do not take away or rename existing SNVTs. Should you still decide to do this, LM might think that this is a brand new application and so erase all associated function blocks, with all their bindings! We assume that you have followed our piece of advice and only added some SNVTs. At this moment the contents of the LNS database will not be up-todate. In LM3, click right on the unit, select Replace.

Should you select Upload From Device you will have problems with the unit already exists etc. For Template Name: enter a new, previously unused name. Select Manual, that is, manual Neuron ID entry, as the node is already installed and is there.

Make sure you do not checkmark the Load Application Image box. Determine the state of the new unit after the installation. If everything goes according to plan, the SNVTs of the new application are now supposed to be included.

Use drag and drop to put the new network variables into the function blocks of the unit. LM3 will also restore all bindings formerly in the unit. To clean up, it may be convenient to look up which Device Templates are no longer in use.

Use the tool bar to select LonMaker - Device Templates. Mark Device Templates no longer in use and select Remove. Should you mark a Device Template still being used, you will get an error message stating that this Device Template is in use and cannot be removed. Please follow the guidelines presented earlier in this chapter. Generate and download to TAC Xenta Perform any required bindings.

Appendix Application Key This is an example on the way it may look when you receive an Application Key, opening up for the use of new Credits chapter 2. TAC Order Department order tac. Thank you for your order. It has been successfully processed. B backup 21, 77 bind a signal 57 Bindable 71 binding 80 bindings 10 broadcast-meddelande. C Changing the application 78 Concepts 10 Configuration parameters 11 configuration parameters 11 Connector 51 Credits D database 21 decimal symbol 16 device name 28 Device Template 11, 49, 74, 80 domain 12, 29, 68, 71, 73 drawing 12 drawing file 12, 33 drawing library 21 drawing tool 11 dummy node 52 dummy-nodes Singapore 65 23 93 China Office 86 21 Sweden 46 8 11 TAC develops, manufactures and markets system solutions, products and software for the control and supervision of building services systems via open integrated systems, intended for use by customers looking for optimum indoor comfort, safety and operating costs.

TAC has about employees, with subsidiary companies in the Nordic countries, the UK, Germany, Poland and Singapore, complemented by partners in some 70 countries. Open navigation menu. Close suggestions Search Search. User Settings. Skip carousel. Carousel Previous. Carousel Next. What is Scribd? Explore Ebooks.

Bestsellers Editors' Picks All Ebooks. Explore Audiobooks. Bestsellers Editors' Picks All audiobooks. Explore Magazines. Editors' Picks All magazines. Explore Podcasts All podcasts. Difficulty Beginner Intermediate Advanced. Explore Documents. Manual Xenta vs