404
+ +Page not found
+ + +'+ escapeHtml(title) + '
' + escapeHtml(summary) +'
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Welcome to HDZero VTX Docs!
+
What is HDZero?
+PUSH YOUR SKILLS TO THE LIMIT
+HDZero offers industry-leading low latency, giving you more time to react and the best possible chance of hitting that next gap. With its smooth, consistent FPV video feed, you'll experience the same locked-in feeling you get with analog video–but with the clarity of HD.
+MAKE IT AN EVENT
+HDZero supports the standard 5.8ghz video channels, meaning you can have up to 8 simultaneous pilots flying either full-quality HDZero or analog video. When you're ready to take a break and spectate, you can tune in to any channel and view the pilot's feed with no loss of quality, giving you the same feeling of being in the air yourself.
+UPGRADE YOUR FLEET
+From 1S whoops to long-range wings, HDZero offers a variety of VTX and camera options to suit every build. You may even be able to use the gear you already have–the HDZero receiver will work with any FPV goggle with an HDMI input. HDZero can grow with your needs and fit perfectly into your preferred FPV craft.
+RAPIDLY EVOLVING SYSTEM
+HDZero is rapidly evolving. Please always use the latest firmware that is located at www.hd-zero.com/document.
+ +
+
+
+
+
+ Next »
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/js/html5shiv.min.js b/js/html5shiv.min.js
new file mode 100644
index 0000000..1a01c94
--- /dev/null
+++ b/js/html5shiv.min.js
@@ -0,0 +1,4 @@
+/**
+* @preserve HTML5 Shiv 3.7.3 | @afarkas @jdalton @jon_neal @rem | MIT/GPL2 Licensed
+*/
+!function(a,b){function c(a,b){var c=a.createElement("p"),d=a.getElementsByTagName("head")[0]||a.documentElement;return c.innerHTML="x",d.insertBefore(c.lastChild,d.firstChild)}function d(){var a=t.elements;return"string"==typeof a?a.split(" "):a}function e(a,b){var c=t.elements;"string"!=typeof c&&(c=c.join(" ")),"string"!=typeof a&&(a=a.join(" ")),t.elements=c+" "+a,j(b)}function f(a){var b=s[a[q]];return b||(b={},r++,a[q]=r,s[r]=b),b}function g(a,c,d){if(c||(c=b),l)return c.createElement(a);d||(d=f(c));var e;return e=d.cache[a]?d.cache[a].cloneNode():p.test(a)?(d.cache[a]=d.createElem(a)).cloneNode():d.createElem(a),!e.canHaveChildren||o.test(a)||e.tagUrn?e:d.frag.appendChild(e)}function h(a,c){if(a||(a=b),l)return a.createDocumentFragment();c=c||f(a);for(var e=c.frag.cloneNode(),g=0,h=d(),i=h.length;i>g;g++)e.createElement(h[g]);return e}function i(a,b){b.cache||(b.cache={},b.createElem=a.createElement,b.createFrag=a.createDocumentFragment,b.frag=b.createFrag()),a.createElement=function(c){return t.shivMethods?g(c,a,b):b.createElem(c)},a.createDocumentFragment=Function("h,f","return function(){var n=f.cloneNode(),c=n.createElement;h.shivMethods&&("+d().join().replace(/[\w\-:]+/g,function(a){return b.createElem(a),b.frag.createElement(a),'c("'+a+'")'})+");return n}")(t,b.frag)}function j(a){a||(a=b);var d=f(a);return!t.shivCSS||k||d.hasCSS||(d.hasCSS=!!c(a,"article,aside,dialog,figcaption,figure,footer,header,hgroup,main,nav,section{display:block}mark{background:#FF0;color:#000}template{display:none}")),l||i(a,d),a}var k,l,m="3.7.3",n=a.html5||{},o=/^<|^(?:button|map|select|textarea|object|iframe|option|optgroup)$/i,p=/^(?:a|b|code|div|fieldset|h1|h2|h3|h4|h5|h6|i|label|li|ol|p|q|span|strong|style|table|tbody|td|th|tr|ul)$/i,q="_html5shiv",r=0,s={};!function(){try{var a=b.createElement("a");a.innerHTML="
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Search Results
+ + + +
+ Searching...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/search/lunr.js b/search/lunr.js
new file mode 100644
index 0000000..aca0a16
--- /dev/null
+++ b/search/lunr.js
@@ -0,0 +1,3475 @@
+/**
+ * lunr - http://lunrjs.com - A bit like Solr, but much smaller and not as bright - 2.3.9
+ * Copyright (C) 2020 Oliver Nightingale
+ * @license MIT
+ */
+
+;(function(){
+
+/**
+ * A convenience function for configuring and constructing
+ * a new lunr Index.
+ *
+ * A lunr.Builder instance is created and the pipeline setup
+ * with a trimmer, stop word filter and stemmer.
+ *
+ * This builder object is yielded to the configuration function
+ * that is passed as a parameter, allowing the list of fields
+ * and other builder parameters to be customised.
+ *
+ * All documents _must_ be added within the passed config function.
+ *
+ * @example
+ * var idx = lunr(function () {
+ * this.field('title')
+ * this.field('body')
+ * this.ref('id')
+ *
+ * documents.forEach(function (doc) {
+ * this.add(doc)
+ * }, this)
+ * })
+ *
+ * @see {@link lunr.Builder}
+ * @see {@link lunr.Pipeline}
+ * @see {@link lunr.trimmer}
+ * @see {@link lunr.stopWordFilter}
+ * @see {@link lunr.stemmer}
+ * @namespace {function} lunr
+ */
+var lunr = function (config) {
+ var builder = new lunr.Builder
+
+ builder.pipeline.add(
+ lunr.trimmer,
+ lunr.stopWordFilter,
+ lunr.stemmer
+ )
+
+ builder.searchPipeline.add(
+ lunr.stemmer
+ )
+
+ config.call(builder, builder)
+ return builder.build()
+}
+
+lunr.version = "2.3.9"
+/*!
+ * lunr.utils
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A namespace containing utils for the rest of the lunr library
+ * @namespace lunr.utils
+ */
+lunr.utils = {}
+
+/**
+ * Print a warning message to the console.
+ *
+ * @param {String} message The message to be printed.
+ * @memberOf lunr.utils
+ * @function
+ */
+lunr.utils.warn = (function (global) {
+ /* eslint-disable no-console */
+ return function (message) {
+ if (global.console && console.warn) {
+ console.warn(message)
+ }
+ }
+ /* eslint-enable no-console */
+})(this)
+
+/**
+ * Convert an object to a string.
+ *
+ * In the case of `null` and `undefined` the function returns
+ * the empty string, in all other cases the result of calling
+ * `toString` on the passed object is returned.
+ *
+ * @param {Any} obj The object to convert to a string.
+ * @return {String} string representation of the passed object.
+ * @memberOf lunr.utils
+ */
+lunr.utils.asString = function (obj) {
+ if (obj === void 0 || obj === null) {
+ return ""
+ } else {
+ return obj.toString()
+ }
+}
+
+/**
+ * Clones an object.
+ *
+ * Will create a copy of an existing object such that any mutations
+ * on the copy cannot affect the original.
+ *
+ * Only shallow objects are supported, passing a nested object to this
+ * function will cause a TypeError.
+ *
+ * Objects with primitives, and arrays of primitives are supported.
+ *
+ * @param {Object} obj The object to clone.
+ * @return {Object} a clone of the passed object.
+ * @throws {TypeError} when a nested object is passed.
+ * @memberOf Utils
+ */
+lunr.utils.clone = function (obj) {
+ if (obj === null || obj === undefined) {
+ return obj
+ }
+
+ var clone = Object.create(null),
+ keys = Object.keys(obj)
+
+ for (var i = 0; i < keys.length; i++) {
+ var key = keys[i],
+ val = obj[key]
+
+ if (Array.isArray(val)) {
+ clone[key] = val.slice()
+ continue
+ }
+
+ if (typeof val === 'string' ||
+ typeof val === 'number' ||
+ typeof val === 'boolean') {
+ clone[key] = val
+ continue
+ }
+
+ throw new TypeError("clone is not deep and does not support nested objects")
+ }
+
+ return clone
+}
+lunr.FieldRef = function (docRef, fieldName, stringValue) {
+ this.docRef = docRef
+ this.fieldName = fieldName
+ this._stringValue = stringValue
+}
+
+lunr.FieldRef.joiner = "/"
+
+lunr.FieldRef.fromString = function (s) {
+ var n = s.indexOf(lunr.FieldRef.joiner)
+
+ if (n === -1) {
+ throw "malformed field ref string"
+ }
+
+ var fieldRef = s.slice(0, n),
+ docRef = s.slice(n + 1)
+
+ return new lunr.FieldRef (docRef, fieldRef, s)
+}
+
+lunr.FieldRef.prototype.toString = function () {
+ if (this._stringValue == undefined) {
+ this._stringValue = this.fieldName + lunr.FieldRef.joiner + this.docRef
+ }
+
+ return this._stringValue
+}
+/*!
+ * lunr.Set
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A lunr set.
+ *
+ * @constructor
+ */
+lunr.Set = function (elements) {
+ this.elements = Object.create(null)
+
+ if (elements) {
+ this.length = elements.length
+
+ for (var i = 0; i < this.length; i++) {
+ this.elements[elements[i]] = true
+ }
+ } else {
+ this.length = 0
+ }
+}
+
+/**
+ * A complete set that contains all elements.
+ *
+ * @static
+ * @readonly
+ * @type {lunr.Set}
+ */
+lunr.Set.complete = {
+ intersect: function (other) {
+ return other
+ },
+
+ union: function () {
+ return this
+ },
+
+ contains: function () {
+ return true
+ }
+}
+
+/**
+ * An empty set that contains no elements.
+ *
+ * @static
+ * @readonly
+ * @type {lunr.Set}
+ */
+lunr.Set.empty = {
+ intersect: function () {
+ return this
+ },
+
+ union: function (other) {
+ return other
+ },
+
+ contains: function () {
+ return false
+ }
+}
+
+/**
+ * Returns true if this set contains the specified object.
+ *
+ * @param {object} object - Object whose presence in this set is to be tested.
+ * @returns {boolean} - True if this set contains the specified object.
+ */
+lunr.Set.prototype.contains = function (object) {
+ return !!this.elements[object]
+}
+
+/**
+ * Returns a new set containing only the elements that are present in both
+ * this set and the specified set.
+ *
+ * @param {lunr.Set} other - set to intersect with this set.
+ * @returns {lunr.Set} a new set that is the intersection of this and the specified set.
+ */
+
+lunr.Set.prototype.intersect = function (other) {
+ var a, b, elements, intersection = []
+
+ if (other === lunr.Set.complete) {
+ return this
+ }
+
+ if (other === lunr.Set.empty) {
+ return other
+ }
+
+ if (this.length < other.length) {
+ a = this
+ b = other
+ } else {
+ a = other
+ b = this
+ }
+
+ elements = Object.keys(a.elements)
+
+ for (var i = 0; i < elements.length; i++) {
+ var element = elements[i]
+ if (element in b.elements) {
+ intersection.push(element)
+ }
+ }
+
+ return new lunr.Set (intersection)
+}
+
+/**
+ * Returns a new set combining the elements of this and the specified set.
+ *
+ * @param {lunr.Set} other - set to union with this set.
+ * @return {lunr.Set} a new set that is the union of this and the specified set.
+ */
+
+lunr.Set.prototype.union = function (other) {
+ if (other === lunr.Set.complete) {
+ return lunr.Set.complete
+ }
+
+ if (other === lunr.Set.empty) {
+ return this
+ }
+
+ return new lunr.Set(Object.keys(this.elements).concat(Object.keys(other.elements)))
+}
+/**
+ * A function to calculate the inverse document frequency for
+ * a posting. This is shared between the builder and the index
+ *
+ * @private
+ * @param {object} posting - The posting for a given term
+ * @param {number} documentCount - The total number of documents.
+ */
+lunr.idf = function (posting, documentCount) {
+ var documentsWithTerm = 0
+
+ for (var fieldName in posting) {
+ if (fieldName == '_index') continue // Ignore the term index, its not a field
+ documentsWithTerm += Object.keys(posting[fieldName]).length
+ }
+
+ var x = (documentCount - documentsWithTerm + 0.5) / (documentsWithTerm + 0.5)
+
+ return Math.log(1 + Math.abs(x))
+}
+
+/**
+ * A token wraps a string representation of a token
+ * as it is passed through the text processing pipeline.
+ *
+ * @constructor
+ * @param {string} [str=''] - The string token being wrapped.
+ * @param {object} [metadata={}] - Metadata associated with this token.
+ */
+lunr.Token = function (str, metadata) {
+ this.str = str || ""
+ this.metadata = metadata || {}
+}
+
+/**
+ * Returns the token string that is being wrapped by this object.
+ *
+ * @returns {string}
+ */
+lunr.Token.prototype.toString = function () {
+ return this.str
+}
+
+/**
+ * A token update function is used when updating or optionally
+ * when cloning a token.
+ *
+ * @callback lunr.Token~updateFunction
+ * @param {string} str - The string representation of the token.
+ * @param {Object} metadata - All metadata associated with this token.
+ */
+
+/**
+ * Applies the given function to the wrapped string token.
+ *
+ * @example
+ * token.update(function (str, metadata) {
+ * return str.toUpperCase()
+ * })
+ *
+ * @param {lunr.Token~updateFunction} fn - A function to apply to the token string.
+ * @returns {lunr.Token}
+ */
+lunr.Token.prototype.update = function (fn) {
+ this.str = fn(this.str, this.metadata)
+ return this
+}
+
+/**
+ * Creates a clone of this token. Optionally a function can be
+ * applied to the cloned token.
+ *
+ * @param {lunr.Token~updateFunction} [fn] - An optional function to apply to the cloned token.
+ * @returns {lunr.Token}
+ */
+lunr.Token.prototype.clone = function (fn) {
+ fn = fn || function (s) { return s }
+ return new lunr.Token (fn(this.str, this.metadata), this.metadata)
+}
+/*!
+ * lunr.tokenizer
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A function for splitting a string into tokens ready to be inserted into
+ * the search index. Uses `lunr.tokenizer.separator` to split strings, change
+ * the value of this property to change how strings are split into tokens.
+ *
+ * This tokenizer will convert its parameter to a string by calling `toString` and
+ * then will split this string on the character in `lunr.tokenizer.separator`.
+ * Arrays will have their elements converted to strings and wrapped in a lunr.Token.
+ *
+ * Optional metadata can be passed to the tokenizer, this metadata will be cloned and
+ * added as metadata to every token that is created from the object to be tokenized.
+ *
+ * @static
+ * @param {?(string|object|object[])} obj - The object to convert into tokens
+ * @param {?object} metadata - Optional metadata to associate with every token
+ * @returns {lunr.Token[]}
+ * @see {@link lunr.Pipeline}
+ */
+lunr.tokenizer = function (obj, metadata) {
+ if (obj == null || obj == undefined) {
+ return []
+ }
+
+ if (Array.isArray(obj)) {
+ return obj.map(function (t) {
+ return new lunr.Token(
+ lunr.utils.asString(t).toLowerCase(),
+ lunr.utils.clone(metadata)
+ )
+ })
+ }
+
+ var str = obj.toString().toLowerCase(),
+ len = str.length,
+ tokens = []
+
+ for (var sliceEnd = 0, sliceStart = 0; sliceEnd <= len; sliceEnd++) {
+ var char = str.charAt(sliceEnd),
+ sliceLength = sliceEnd - sliceStart
+
+ if ((char.match(lunr.tokenizer.separator) || sliceEnd == len)) {
+
+ if (sliceLength > 0) {
+ var tokenMetadata = lunr.utils.clone(metadata) || {}
+ tokenMetadata["position"] = [sliceStart, sliceLength]
+ tokenMetadata["index"] = tokens.length
+
+ tokens.push(
+ new lunr.Token (
+ str.slice(sliceStart, sliceEnd),
+ tokenMetadata
+ )
+ )
+ }
+
+ sliceStart = sliceEnd + 1
+ }
+
+ }
+
+ return tokens
+}
+
+/**
+ * The separator used to split a string into tokens. Override this property to change the behaviour of
+ * `lunr.tokenizer` behaviour when tokenizing strings. By default this splits on whitespace and hyphens.
+ *
+ * @static
+ * @see lunr.tokenizer
+ */
+lunr.tokenizer.separator = /[\s\-]+/
+/*!
+ * lunr.Pipeline
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * lunr.Pipelines maintain an ordered list of functions to be applied to all
+ * tokens in documents entering the search index and queries being ran against
+ * the index.
+ *
+ * An instance of lunr.Index created with the lunr shortcut will contain a
+ * pipeline with a stop word filter and an English language stemmer. Extra
+ * functions can be added before or after either of these functions or these
+ * default functions can be removed.
+ *
+ * When run the pipeline will call each function in turn, passing a token, the
+ * index of that token in the original list of all tokens and finally a list of
+ * all the original tokens.
+ *
+ * The output of functions in the pipeline will be passed to the next function
+ * in the pipeline. To exclude a token from entering the index the function
+ * should return undefined, the rest of the pipeline will not be called with
+ * this token.
+ *
+ * For serialisation of pipelines to work, all functions used in an instance of
+ * a pipeline should be registered with lunr.Pipeline. Registered functions can
+ * then be loaded. If trying to load a serialised pipeline that uses functions
+ * that are not registered an error will be thrown.
+ *
+ * If not planning on serialising the pipeline then registering pipeline functions
+ * is not necessary.
+ *
+ * @constructor
+ */
+lunr.Pipeline = function () {
+ this._stack = []
+}
+
+lunr.Pipeline.registeredFunctions = Object.create(null)
+
+/**
+ * A pipeline function maps lunr.Token to lunr.Token. A lunr.Token contains the token
+ * string as well as all known metadata. A pipeline function can mutate the token string
+ * or mutate (or add) metadata for a given token.
+ *
+ * A pipeline function can indicate that the passed token should be discarded by returning
+ * null, undefined or an empty string. This token will not be passed to any downstream pipeline
+ * functions and will not be added to the index.
+ *
+ * Multiple tokens can be returned by returning an array of tokens. Each token will be passed
+ * to any downstream pipeline functions and all will returned tokens will be added to the index.
+ *
+ * Any number of pipeline functions may be chained together using a lunr.Pipeline.
+ *
+ * @interface lunr.PipelineFunction
+ * @param {lunr.Token} token - A token from the document being processed.
+ * @param {number} i - The index of this token in the complete list of tokens for this document/field.
+ * @param {lunr.Token[]} tokens - All tokens for this document/field.
+ * @returns {(?lunr.Token|lunr.Token[])}
+ */
+
+/**
+ * Register a function with the pipeline.
+ *
+ * Functions that are used in the pipeline should be registered if the pipeline
+ * needs to be serialised, or a serialised pipeline needs to be loaded.
+ *
+ * Registering a function does not add it to a pipeline, functions must still be
+ * added to instances of the pipeline for them to be used when running a pipeline.
+ *
+ * @param {lunr.PipelineFunction} fn - The function to check for.
+ * @param {String} label - The label to register this function with
+ */
+lunr.Pipeline.registerFunction = function (fn, label) {
+ if (label in this.registeredFunctions) {
+ lunr.utils.warn('Overwriting existing registered function: ' + label)
+ }
+
+ fn.label = label
+ lunr.Pipeline.registeredFunctions[fn.label] = fn
+}
+
+/**
+ * Warns if the function is not registered as a Pipeline function.
+ *
+ * @param {lunr.PipelineFunction} fn - The function to check for.
+ * @private
+ */
+lunr.Pipeline.warnIfFunctionNotRegistered = function (fn) {
+ var isRegistered = fn.label && (fn.label in this.registeredFunctions)
+
+ if (!isRegistered) {
+ lunr.utils.warn('Function is not registered with pipeline. This may cause problems when serialising the index.\n', fn)
+ }
+}
+
+/**
+ * Loads a previously serialised pipeline.
+ *
+ * All functions to be loaded must already be registered with lunr.Pipeline.
+ * If any function from the serialised data has not been registered then an
+ * error will be thrown.
+ *
+ * @param {Object} serialised - The serialised pipeline to load.
+ * @returns {lunr.Pipeline}
+ */
+lunr.Pipeline.load = function (serialised) {
+ var pipeline = new lunr.Pipeline
+
+ serialised.forEach(function (fnName) {
+ var fn = lunr.Pipeline.registeredFunctions[fnName]
+
+ if (fn) {
+ pipeline.add(fn)
+ } else {
+ throw new Error('Cannot load unregistered function: ' + fnName)
+ }
+ })
+
+ return pipeline
+}
+
+/**
+ * Adds new functions to the end of the pipeline.
+ *
+ * Logs a warning if the function has not been registered.
+ *
+ * @param {lunr.PipelineFunction[]} functions - Any number of functions to add to the pipeline.
+ */
+lunr.Pipeline.prototype.add = function () {
+ var fns = Array.prototype.slice.call(arguments)
+
+ fns.forEach(function (fn) {
+ lunr.Pipeline.warnIfFunctionNotRegistered(fn)
+ this._stack.push(fn)
+ }, this)
+}
+
+/**
+ * Adds a single function after a function that already exists in the
+ * pipeline.
+ *
+ * Logs a warning if the function has not been registered.
+ *
+ * @param {lunr.PipelineFunction} existingFn - A function that already exists in the pipeline.
+ * @param {lunr.PipelineFunction} newFn - The new function to add to the pipeline.
+ */
+lunr.Pipeline.prototype.after = function (existingFn, newFn) {
+ lunr.Pipeline.warnIfFunctionNotRegistered(newFn)
+
+ var pos = this._stack.indexOf(existingFn)
+ if (pos == -1) {
+ throw new Error('Cannot find existingFn')
+ }
+
+ pos = pos + 1
+ this._stack.splice(pos, 0, newFn)
+}
+
+/**
+ * Adds a single function before a function that already exists in the
+ * pipeline.
+ *
+ * Logs a warning if the function has not been registered.
+ *
+ * @param {lunr.PipelineFunction} existingFn - A function that already exists in the pipeline.
+ * @param {lunr.PipelineFunction} newFn - The new function to add to the pipeline.
+ */
+lunr.Pipeline.prototype.before = function (existingFn, newFn) {
+ lunr.Pipeline.warnIfFunctionNotRegistered(newFn)
+
+ var pos = this._stack.indexOf(existingFn)
+ if (pos == -1) {
+ throw new Error('Cannot find existingFn')
+ }
+
+ this._stack.splice(pos, 0, newFn)
+}
+
+/**
+ * Removes a function from the pipeline.
+ *
+ * @param {lunr.PipelineFunction} fn The function to remove from the pipeline.
+ */
+lunr.Pipeline.prototype.remove = function (fn) {
+ var pos = this._stack.indexOf(fn)
+ if (pos == -1) {
+ return
+ }
+
+ this._stack.splice(pos, 1)
+}
+
+/**
+ * Runs the current list of functions that make up the pipeline against the
+ * passed tokens.
+ *
+ * @param {Array} tokens The tokens to run through the pipeline.
+ * @returns {Array}
+ */
+lunr.Pipeline.prototype.run = function (tokens) {
+ var stackLength = this._stack.length
+
+ for (var i = 0; i < stackLength; i++) {
+ var fn = this._stack[i]
+ var memo = []
+
+ for (var j = 0; j < tokens.length; j++) {
+ var result = fn(tokens[j], j, tokens)
+
+ if (result === null || result === void 0 || result === '') continue
+
+ if (Array.isArray(result)) {
+ for (var k = 0; k < result.length; k++) {
+ memo.push(result[k])
+ }
+ } else {
+ memo.push(result)
+ }
+ }
+
+ tokens = memo
+ }
+
+ return tokens
+}
+
+/**
+ * Convenience method for passing a string through a pipeline and getting
+ * strings out. This method takes care of wrapping the passed string in a
+ * token and mapping the resulting tokens back to strings.
+ *
+ * @param {string} str - The string to pass through the pipeline.
+ * @param {?object} metadata - Optional metadata to associate with the token
+ * passed to the pipeline.
+ * @returns {string[]}
+ */
+lunr.Pipeline.prototype.runString = function (str, metadata) {
+ var token = new lunr.Token (str, metadata)
+
+ return this.run([token]).map(function (t) {
+ return t.toString()
+ })
+}
+
+/**
+ * Resets the pipeline by removing any existing processors.
+ *
+ */
+lunr.Pipeline.prototype.reset = function () {
+ this._stack = []
+}
+
+/**
+ * Returns a representation of the pipeline ready for serialisation.
+ *
+ * Logs a warning if the function has not been registered.
+ *
+ * @returns {Array}
+ */
+lunr.Pipeline.prototype.toJSON = function () {
+ return this._stack.map(function (fn) {
+ lunr.Pipeline.warnIfFunctionNotRegistered(fn)
+
+ return fn.label
+ })
+}
+/*!
+ * lunr.Vector
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A vector is used to construct the vector space of documents and queries. These
+ * vectors support operations to determine the similarity between two documents or
+ * a document and a query.
+ *
+ * Normally no parameters are required for initializing a vector, but in the case of
+ * loading a previously dumped vector the raw elements can be provided to the constructor.
+ *
+ * For performance reasons vectors are implemented with a flat array, where an elements
+ * index is immediately followed by its value. E.g. [index, value, index, value]. This
+ * allows the underlying array to be as sparse as possible and still offer decent
+ * performance when being used for vector calculations.
+ *
+ * @constructor
+ * @param {Number[]} [elements] - The flat list of element index and element value pairs.
+ */
+lunr.Vector = function (elements) {
+ this._magnitude = 0
+ this.elements = elements || []
+}
+
+
+/**
+ * Calculates the position within the vector to insert a given index.
+ *
+ * This is used internally by insert and upsert. If there are duplicate indexes then
+ * the position is returned as if the value for that index were to be updated, but it
+ * is the callers responsibility to check whether there is a duplicate at that index
+ *
+ * @param {Number} insertIdx - The index at which the element should be inserted.
+ * @returns {Number}
+ */
+lunr.Vector.prototype.positionForIndex = function (index) {
+ // For an empty vector the tuple can be inserted at the beginning
+ if (this.elements.length == 0) {
+ return 0
+ }
+
+ var start = 0,
+ end = this.elements.length / 2,
+ sliceLength = end - start,
+ pivotPoint = Math.floor(sliceLength / 2),
+ pivotIndex = this.elements[pivotPoint * 2]
+
+ while (sliceLength > 1) {
+ if (pivotIndex < index) {
+ start = pivotPoint
+ }
+
+ if (pivotIndex > index) {
+ end = pivotPoint
+ }
+
+ if (pivotIndex == index) {
+ break
+ }
+
+ sliceLength = end - start
+ pivotPoint = start + Math.floor(sliceLength / 2)
+ pivotIndex = this.elements[pivotPoint * 2]
+ }
+
+ if (pivotIndex == index) {
+ return pivotPoint * 2
+ }
+
+ if (pivotIndex > index) {
+ return pivotPoint * 2
+ }
+
+ if (pivotIndex < index) {
+ return (pivotPoint + 1) * 2
+ }
+}
+
+/**
+ * Inserts an element at an index within the vector.
+ *
+ * Does not allow duplicates, will throw an error if there is already an entry
+ * for this index.
+ *
+ * @param {Number} insertIdx - The index at which the element should be inserted.
+ * @param {Number} val - The value to be inserted into the vector.
+ */
+lunr.Vector.prototype.insert = function (insertIdx, val) {
+ this.upsert(insertIdx, val, function () {
+ throw "duplicate index"
+ })
+}
+
+/**
+ * Inserts or updates an existing index within the vector.
+ *
+ * @param {Number} insertIdx - The index at which the element should be inserted.
+ * @param {Number} val - The value to be inserted into the vector.
+ * @param {function} fn - A function that is called for updates, the existing value and the
+ * requested value are passed as arguments
+ */
+lunr.Vector.prototype.upsert = function (insertIdx, val, fn) {
+ this._magnitude = 0
+ var position = this.positionForIndex(insertIdx)
+
+ if (this.elements[position] == insertIdx) {
+ this.elements[position + 1] = fn(this.elements[position + 1], val)
+ } else {
+ this.elements.splice(position, 0, insertIdx, val)
+ }
+}
+
+/**
+ * Calculates the magnitude of this vector.
+ *
+ * @returns {Number}
+ */
+lunr.Vector.prototype.magnitude = function () {
+ if (this._magnitude) return this._magnitude
+
+ var sumOfSquares = 0,
+ elementsLength = this.elements.length
+
+ for (var i = 1; i < elementsLength; i += 2) {
+ var val = this.elements[i]
+ sumOfSquares += val * val
+ }
+
+ return this._magnitude = Math.sqrt(sumOfSquares)
+}
+
+/**
+ * Calculates the dot product of this vector and another vector.
+ *
+ * @param {lunr.Vector} otherVector - The vector to compute the dot product with.
+ * @returns {Number}
+ */
+lunr.Vector.prototype.dot = function (otherVector) {
+ var dotProduct = 0,
+ a = this.elements, b = otherVector.elements,
+ aLen = a.length, bLen = b.length,
+ aVal = 0, bVal = 0,
+ i = 0, j = 0
+
+ while (i < aLen && j < bLen) {
+ aVal = a[i], bVal = b[j]
+ if (aVal < bVal) {
+ i += 2
+ } else if (aVal > bVal) {
+ j += 2
+ } else if (aVal == bVal) {
+ dotProduct += a[i + 1] * b[j + 1]
+ i += 2
+ j += 2
+ }
+ }
+
+ return dotProduct
+}
+
+/**
+ * Calculates the similarity between this vector and another vector.
+ *
+ * @param {lunr.Vector} otherVector - The other vector to calculate the
+ * similarity with.
+ * @returns {Number}
+ */
+lunr.Vector.prototype.similarity = function (otherVector) {
+ return this.dot(otherVector) / this.magnitude() || 0
+}
+
+/**
+ * Converts the vector to an array of the elements within the vector.
+ *
+ * @returns {Number[]}
+ */
+lunr.Vector.prototype.toArray = function () {
+ var output = new Array (this.elements.length / 2)
+
+ for (var i = 1, j = 0; i < this.elements.length; i += 2, j++) {
+ output[j] = this.elements[i]
+ }
+
+ return output
+}
+
+/**
+ * A JSON serializable representation of the vector.
+ *
+ * @returns {Number[]}
+ */
+lunr.Vector.prototype.toJSON = function () {
+ return this.elements
+}
+/* eslint-disable */
+/*!
+ * lunr.stemmer
+ * Copyright (C) 2020 Oliver Nightingale
+ * Includes code from - http://tartarus.org/~martin/PorterStemmer/js.txt
+ */
+
+/**
+ * lunr.stemmer is an english language stemmer, this is a JavaScript
+ * implementation of the PorterStemmer taken from http://tartarus.org/~martin
+ *
+ * @static
+ * @implements {lunr.PipelineFunction}
+ * @param {lunr.Token} token - The string to stem
+ * @returns {lunr.Token}
+ * @see {@link lunr.Pipeline}
+ * @function
+ */
+lunr.stemmer = (function(){
+ var step2list = {
+ "ational" : "ate",
+ "tional" : "tion",
+ "enci" : "ence",
+ "anci" : "ance",
+ "izer" : "ize",
+ "bli" : "ble",
+ "alli" : "al",
+ "entli" : "ent",
+ "eli" : "e",
+ "ousli" : "ous",
+ "ization" : "ize",
+ "ation" : "ate",
+ "ator" : "ate",
+ "alism" : "al",
+ "iveness" : "ive",
+ "fulness" : "ful",
+ "ousness" : "ous",
+ "aliti" : "al",
+ "iviti" : "ive",
+ "biliti" : "ble",
+ "logi" : "log"
+ },
+
+ step3list = {
+ "icate" : "ic",
+ "ative" : "",
+ "alize" : "al",
+ "iciti" : "ic",
+ "ical" : "ic",
+ "ful" : "",
+ "ness" : ""
+ },
+
+ c = "[^aeiou]", // consonant
+ v = "[aeiouy]", // vowel
+ C = c + "[^aeiouy]*", // consonant sequence
+ V = v + "[aeiou]*", // vowel sequence
+
+ mgr0 = "^(" + C + ")?" + V + C, // [C]VC... is m>0
+ meq1 = "^(" + C + ")?" + V + C + "(" + V + ")?$", // [C]VC[V] is m=1
+ mgr1 = "^(" + C + ")?" + V + C + V + C, // [C]VCVC... is m>1
+ s_v = "^(" + C + ")?" + v; // vowel in stem
+
+ var re_mgr0 = new RegExp(mgr0);
+ var re_mgr1 = new RegExp(mgr1);
+ var re_meq1 = new RegExp(meq1);
+ var re_s_v = new RegExp(s_v);
+
+ var re_1a = /^(.+?)(ss|i)es$/;
+ var re2_1a = /^(.+?)([^s])s$/;
+ var re_1b = /^(.+?)eed$/;
+ var re2_1b = /^(.+?)(ed|ing)$/;
+ var re_1b_2 = /.$/;
+ var re2_1b_2 = /(at|bl|iz)$/;
+ var re3_1b_2 = new RegExp("([^aeiouylsz])\\1$");
+ var re4_1b_2 = new RegExp("^" + C + v + "[^aeiouwxy]$");
+
+ var re_1c = /^(.+?[^aeiou])y$/;
+ var re_2 = /^(.+?)(ational|tional|enci|anci|izer|bli|alli|entli|eli|ousli|ization|ation|ator|alism|iveness|fulness|ousness|aliti|iviti|biliti|logi)$/;
+
+ var re_3 = /^(.+?)(icate|ative|alize|iciti|ical|ful|ness)$/;
+
+ var re_4 = /^(.+?)(al|ance|ence|er|ic|able|ible|ant|ement|ment|ent|ou|ism|ate|iti|ous|ive|ize)$/;
+ var re2_4 = /^(.+?)(s|t)(ion)$/;
+
+ var re_5 = /^(.+?)e$/;
+ var re_5_1 = /ll$/;
+ var re3_5 = new RegExp("^" + C + v + "[^aeiouwxy]$");
+
+ var porterStemmer = function porterStemmer(w) {
+ var stem,
+ suffix,
+ firstch,
+ re,
+ re2,
+ re3,
+ re4;
+
+ if (w.length < 3) { return w; }
+
+ firstch = w.substr(0,1);
+ if (firstch == "y") {
+ w = firstch.toUpperCase() + w.substr(1);
+ }
+
+ // Step 1a
+ re = re_1a
+ re2 = re2_1a;
+
+ if (re.test(w)) { w = w.replace(re,"$1$2"); }
+ else if (re2.test(w)) { w = w.replace(re2,"$1$2"); }
+
+ // Step 1b
+ re = re_1b;
+ re2 = re2_1b;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ re = re_mgr0;
+ if (re.test(fp[1])) {
+ re = re_1b_2;
+ w = w.replace(re,"");
+ }
+ } else if (re2.test(w)) {
+ var fp = re2.exec(w);
+ stem = fp[1];
+ re2 = re_s_v;
+ if (re2.test(stem)) {
+ w = stem;
+ re2 = re2_1b_2;
+ re3 = re3_1b_2;
+ re4 = re4_1b_2;
+ if (re2.test(w)) { w = w + "e"; }
+ else if (re3.test(w)) { re = re_1b_2; w = w.replace(re,""); }
+ else if (re4.test(w)) { w = w + "e"; }
+ }
+ }
+
+ // Step 1c - replace suffix y or Y by i if preceded by a non-vowel which is not the first letter of the word (so cry -> cri, by -> by, say -> say)
+ re = re_1c;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ w = stem + "i";
+ }
+
+ // Step 2
+ re = re_2;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ suffix = fp[2];
+ re = re_mgr0;
+ if (re.test(stem)) {
+ w = stem + step2list[suffix];
+ }
+ }
+
+ // Step 3
+ re = re_3;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ suffix = fp[2];
+ re = re_mgr0;
+ if (re.test(stem)) {
+ w = stem + step3list[suffix];
+ }
+ }
+
+ // Step 4
+ re = re_4;
+ re2 = re2_4;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ re = re_mgr1;
+ if (re.test(stem)) {
+ w = stem;
+ }
+ } else if (re2.test(w)) {
+ var fp = re2.exec(w);
+ stem = fp[1] + fp[2];
+ re2 = re_mgr1;
+ if (re2.test(stem)) {
+ w = stem;
+ }
+ }
+
+ // Step 5
+ re = re_5;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ re = re_mgr1;
+ re2 = re_meq1;
+ re3 = re3_5;
+ if (re.test(stem) || (re2.test(stem) && !(re3.test(stem)))) {
+ w = stem;
+ }
+ }
+
+ re = re_5_1;
+ re2 = re_mgr1;
+ if (re.test(w) && re2.test(w)) {
+ re = re_1b_2;
+ w = w.replace(re,"");
+ }
+
+ // and turn initial Y back to y
+
+ if (firstch == "y") {
+ w = firstch.toLowerCase() + w.substr(1);
+ }
+
+ return w;
+ };
+
+ return function (token) {
+ return token.update(porterStemmer);
+ }
+})();
+
+lunr.Pipeline.registerFunction(lunr.stemmer, 'stemmer')
+/*!
+ * lunr.stopWordFilter
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * lunr.generateStopWordFilter builds a stopWordFilter function from the provided
+ * list of stop words.
+ *
+ * The built in lunr.stopWordFilter is built using this generator and can be used
+ * to generate custom stopWordFilters for applications or non English languages.
+ *
+ * @function
+ * @param {Array} token The token to pass through the filter
+ * @returns {lunr.PipelineFunction}
+ * @see lunr.Pipeline
+ * @see lunr.stopWordFilter
+ */
+lunr.generateStopWordFilter = function (stopWords) {
+ var words = stopWords.reduce(function (memo, stopWord) {
+ memo[stopWord] = stopWord
+ return memo
+ }, {})
+
+ return function (token) {
+ if (token && words[token.toString()] !== token.toString()) return token
+ }
+}
+
+/**
+ * lunr.stopWordFilter is an English language stop word list filter, any words
+ * contained in the list will not be passed through the filter.
+ *
+ * This is intended to be used in the Pipeline. If the token does not pass the
+ * filter then undefined will be returned.
+ *
+ * @function
+ * @implements {lunr.PipelineFunction}
+ * @params {lunr.Token} token - A token to check for being a stop word.
+ * @returns {lunr.Token}
+ * @see {@link lunr.Pipeline}
+ */
+lunr.stopWordFilter = lunr.generateStopWordFilter([
+ 'a',
+ 'able',
+ 'about',
+ 'across',
+ 'after',
+ 'all',
+ 'almost',
+ 'also',
+ 'am',
+ 'among',
+ 'an',
+ 'and',
+ 'any',
+ 'are',
+ 'as',
+ 'at',
+ 'be',
+ 'because',
+ 'been',
+ 'but',
+ 'by',
+ 'can',
+ 'cannot',
+ 'could',
+ 'dear',
+ 'did',
+ 'do',
+ 'does',
+ 'either',
+ 'else',
+ 'ever',
+ 'every',
+ 'for',
+ 'from',
+ 'get',
+ 'got',
+ 'had',
+ 'has',
+ 'have',
+ 'he',
+ 'her',
+ 'hers',
+ 'him',
+ 'his',
+ 'how',
+ 'however',
+ 'i',
+ 'if',
+ 'in',
+ 'into',
+ 'is',
+ 'it',
+ 'its',
+ 'just',
+ 'least',
+ 'let',
+ 'like',
+ 'likely',
+ 'may',
+ 'me',
+ 'might',
+ 'most',
+ 'must',
+ 'my',
+ 'neither',
+ 'no',
+ 'nor',
+ 'not',
+ 'of',
+ 'off',
+ 'often',
+ 'on',
+ 'only',
+ 'or',
+ 'other',
+ 'our',
+ 'own',
+ 'rather',
+ 'said',
+ 'say',
+ 'says',
+ 'she',
+ 'should',
+ 'since',
+ 'so',
+ 'some',
+ 'than',
+ 'that',
+ 'the',
+ 'their',
+ 'them',
+ 'then',
+ 'there',
+ 'these',
+ 'they',
+ 'this',
+ 'tis',
+ 'to',
+ 'too',
+ 'twas',
+ 'us',
+ 'wants',
+ 'was',
+ 'we',
+ 'were',
+ 'what',
+ 'when',
+ 'where',
+ 'which',
+ 'while',
+ 'who',
+ 'whom',
+ 'why',
+ 'will',
+ 'with',
+ 'would',
+ 'yet',
+ 'you',
+ 'your'
+])
+
+lunr.Pipeline.registerFunction(lunr.stopWordFilter, 'stopWordFilter')
+/*!
+ * lunr.trimmer
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * lunr.trimmer is a pipeline function for trimming non word
+ * characters from the beginning and end of tokens before they
+ * enter the index.
+ *
+ * This implementation may not work correctly for non latin
+ * characters and should either be removed or adapted for use
+ * with languages with non-latin characters.
+ *
+ * @static
+ * @implements {lunr.PipelineFunction}
+ * @param {lunr.Token} token The token to pass through the filter
+ * @returns {lunr.Token}
+ * @see lunr.Pipeline
+ */
+lunr.trimmer = function (token) {
+ return token.update(function (s) {
+ return s.replace(/^\W+/, '').replace(/\W+$/, '')
+ })
+}
+
+lunr.Pipeline.registerFunction(lunr.trimmer, 'trimmer')
+/*!
+ * lunr.TokenSet
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A token set is used to store the unique list of all tokens
+ * within an index. Token sets are also used to represent an
+ * incoming query to the index, this query token set and index
+ * token set are then intersected to find which tokens to look
+ * up in the inverted index.
+ *
+ * A token set can hold multiple tokens, as in the case of the
+ * index token set, or it can hold a single token as in the
+ * case of a simple query token set.
+ *
+ * Additionally token sets are used to perform wildcard matching.
+ * Leading, contained and trailing wildcards are supported, and
+ * from this edit distance matching can also be provided.
+ *
+ * Token sets are implemented as a minimal finite state automata,
+ * where both common prefixes and suffixes are shared between tokens.
+ * This helps to reduce the space used for storing the token set.
+ *
+ * @constructor
+ */
+lunr.TokenSet = function () {
+ this.final = false
+ this.edges = {}
+ this.id = lunr.TokenSet._nextId
+ lunr.TokenSet._nextId += 1
+}
+
+/**
+ * Keeps track of the next, auto increment, identifier to assign
+ * to a new tokenSet.
+ *
+ * TokenSets require a unique identifier to be correctly minimised.
+ *
+ * @private
+ */
+lunr.TokenSet._nextId = 1
+
+/**
+ * Creates a TokenSet instance from the given sorted array of words.
+ *
+ * @param {String[]} arr - A sorted array of strings to create the set from.
+ * @returns {lunr.TokenSet}
+ * @throws Will throw an error if the input array is not sorted.
+ */
+lunr.TokenSet.fromArray = function (arr) {
+ var builder = new lunr.TokenSet.Builder
+
+ for (var i = 0, len = arr.length; i < len; i++) {
+ builder.insert(arr[i])
+ }
+
+ builder.finish()
+ return builder.root
+}
+
+/**
+ * Creates a token set from a query clause.
+ *
+ * @private
+ * @param {Object} clause - A single clause from lunr.Query.
+ * @param {string} clause.term - The query clause term.
+ * @param {number} [clause.editDistance] - The optional edit distance for the term.
+ * @returns {lunr.TokenSet}
+ */
+lunr.TokenSet.fromClause = function (clause) {
+ if ('editDistance' in clause) {
+ return lunr.TokenSet.fromFuzzyString(clause.term, clause.editDistance)
+ } else {
+ return lunr.TokenSet.fromString(clause.term)
+ }
+}
+
+/**
+ * Creates a token set representing a single string with a specified
+ * edit distance.
+ *
+ * Insertions, deletions, substitutions and transpositions are each
+ * treated as an edit distance of 1.
+ *
+ * Increasing the allowed edit distance will have a dramatic impact
+ * on the performance of both creating and intersecting these TokenSets.
+ * It is advised to keep the edit distance less than 3.
+ *
+ * @param {string} str - The string to create the token set from.
+ * @param {number} editDistance - The allowed edit distance to match.
+ * @returns {lunr.Vector}
+ */
+lunr.TokenSet.fromFuzzyString = function (str, editDistance) {
+ var root = new lunr.TokenSet
+
+ var stack = [{
+ node: root,
+ editsRemaining: editDistance,
+ str: str
+ }]
+
+ while (stack.length) {
+ var frame = stack.pop()
+
+ // no edit
+ if (frame.str.length > 0) {
+ var char = frame.str.charAt(0),
+ noEditNode
+
+ if (char in frame.node.edges) {
+ noEditNode = frame.node.edges[char]
+ } else {
+ noEditNode = new lunr.TokenSet
+ frame.node.edges[char] = noEditNode
+ }
+
+ if (frame.str.length == 1) {
+ noEditNode.final = true
+ }
+
+ stack.push({
+ node: noEditNode,
+ editsRemaining: frame.editsRemaining,
+ str: frame.str.slice(1)
+ })
+ }
+
+ if (frame.editsRemaining == 0) {
+ continue
+ }
+
+ // insertion
+ if ("*" in frame.node.edges) {
+ var insertionNode = frame.node.edges["*"]
+ } else {
+ var insertionNode = new lunr.TokenSet
+ frame.node.edges["*"] = insertionNode
+ }
+
+ if (frame.str.length == 0) {
+ insertionNode.final = true
+ }
+
+ stack.push({
+ node: insertionNode,
+ editsRemaining: frame.editsRemaining - 1,
+ str: frame.str
+ })
+
+ // deletion
+ // can only do a deletion if we have enough edits remaining
+ // and if there are characters left to delete in the string
+ if (frame.str.length > 1) {
+ stack.push({
+ node: frame.node,
+ editsRemaining: frame.editsRemaining - 1,
+ str: frame.str.slice(1)
+ })
+ }
+
+ // deletion
+ // just removing the last character from the str
+ if (frame.str.length == 1) {
+ frame.node.final = true
+ }
+
+ // substitution
+ // can only do a substitution if we have enough edits remaining
+ // and if there are characters left to substitute
+ if (frame.str.length >= 1) {
+ if ("*" in frame.node.edges) {
+ var substitutionNode = frame.node.edges["*"]
+ } else {
+ var substitutionNode = new lunr.TokenSet
+ frame.node.edges["*"] = substitutionNode
+ }
+
+ if (frame.str.length == 1) {
+ substitutionNode.final = true
+ }
+
+ stack.push({
+ node: substitutionNode,
+ editsRemaining: frame.editsRemaining - 1,
+ str: frame.str.slice(1)
+ })
+ }
+
+ // transposition
+ // can only do a transposition if there are edits remaining
+ // and there are enough characters to transpose
+ if (frame.str.length > 1) {
+ var charA = frame.str.charAt(0),
+ charB = frame.str.charAt(1),
+ transposeNode
+
+ if (charB in frame.node.edges) {
+ transposeNode = frame.node.edges[charB]
+ } else {
+ transposeNode = new lunr.TokenSet
+ frame.node.edges[charB] = transposeNode
+ }
+
+ if (frame.str.length == 1) {
+ transposeNode.final = true
+ }
+
+ stack.push({
+ node: transposeNode,
+ editsRemaining: frame.editsRemaining - 1,
+ str: charA + frame.str.slice(2)
+ })
+ }
+ }
+
+ return root
+}
+
+/**
+ * Creates a TokenSet from a string.
+ *
+ * The string may contain one or more wildcard characters (*)
+ * that will allow wildcard matching when intersecting with
+ * another TokenSet.
+ *
+ * @param {string} str - The string to create a TokenSet from.
+ * @returns {lunr.TokenSet}
+ */
+lunr.TokenSet.fromString = function (str) {
+ var node = new lunr.TokenSet,
+ root = node
+
+ /*
+ * Iterates through all characters within the passed string
+ * appending a node for each character.
+ *
+ * When a wildcard character is found then a self
+ * referencing edge is introduced to continually match
+ * any number of any characters.
+ */
+ for (var i = 0, len = str.length; i < len; i++) {
+ var char = str[i],
+ final = (i == len - 1)
+
+ if (char == "*") {
+ node.edges[char] = node
+ node.final = final
+
+ } else {
+ var next = new lunr.TokenSet
+ next.final = final
+
+ node.edges[char] = next
+ node = next
+ }
+ }
+
+ return root
+}
+
+/**
+ * Converts this TokenSet into an array of strings
+ * contained within the TokenSet.
+ *
+ * This is not intended to be used on a TokenSet that
+ * contains wildcards, in these cases the results are
+ * undefined and are likely to cause an infinite loop.
+ *
+ * @returns {string[]}
+ */
+lunr.TokenSet.prototype.toArray = function () {
+ var words = []
+
+ var stack = [{
+ prefix: "",
+ node: this
+ }]
+
+ while (stack.length) {
+ var frame = stack.pop(),
+ edges = Object.keys(frame.node.edges),
+ len = edges.length
+
+ if (frame.node.final) {
+ /* In Safari, at this point the prefix is sometimes corrupted, see:
+ * https://github.com/olivernn/lunr.js/issues/279 Calling any
+ * String.prototype method forces Safari to "cast" this string to what
+ * it's supposed to be, fixing the bug. */
+ frame.prefix.charAt(0)
+ words.push(frame.prefix)
+ }
+
+ for (var i = 0; i < len; i++) {
+ var edge = edges[i]
+
+ stack.push({
+ prefix: frame.prefix.concat(edge),
+ node: frame.node.edges[edge]
+ })
+ }
+ }
+
+ return words
+}
+
+/**
+ * Generates a string representation of a TokenSet.
+ *
+ * This is intended to allow TokenSets to be used as keys
+ * in objects, largely to aid the construction and minimisation
+ * of a TokenSet. As such it is not designed to be a human
+ * friendly representation of the TokenSet.
+ *
+ * @returns {string}
+ */
+lunr.TokenSet.prototype.toString = function () {
+ // NOTE: Using Object.keys here as this.edges is very likely
+ // to enter 'hash-mode' with many keys being added
+ //
+ // avoiding a for-in loop here as it leads to the function
+ // being de-optimised (at least in V8). From some simple
+ // benchmarks the performance is comparable, but allowing
+ // V8 to optimize may mean easy performance wins in the future.
+
+ if (this._str) {
+ return this._str
+ }
+
+ var str = this.final ? '1' : '0',
+ labels = Object.keys(this.edges).sort(),
+ len = labels.length
+
+ for (var i = 0; i < len; i++) {
+ var label = labels[i],
+ node = this.edges[label]
+
+ str = str + label + node.id
+ }
+
+ return str
+}
+
+/**
+ * Returns a new TokenSet that is the intersection of
+ * this TokenSet and the passed TokenSet.
+ *
+ * This intersection will take into account any wildcards
+ * contained within the TokenSet.
+ *
+ * @param {lunr.TokenSet} b - An other TokenSet to intersect with.
+ * @returns {lunr.TokenSet}
+ */
+lunr.TokenSet.prototype.intersect = function (b) {
+ var output = new lunr.TokenSet,
+ frame = undefined
+
+ var stack = [{
+ qNode: b,
+ output: output,
+ node: this
+ }]
+
+ while (stack.length) {
+ frame = stack.pop()
+
+ // NOTE: As with the #toString method, we are using
+ // Object.keys and a for loop instead of a for-in loop
+ // as both of these objects enter 'hash' mode, causing
+ // the function to be de-optimised in V8
+ var qEdges = Object.keys(frame.qNode.edges),
+ qLen = qEdges.length,
+ nEdges = Object.keys(frame.node.edges),
+ nLen = nEdges.length
+
+ for (var q = 0; q < qLen; q++) {
+ var qEdge = qEdges[q]
+
+ for (var n = 0; n < nLen; n++) {
+ var nEdge = nEdges[n]
+
+ if (nEdge == qEdge || qEdge == '*') {
+ var node = frame.node.edges[nEdge],
+ qNode = frame.qNode.edges[qEdge],
+ final = node.final && qNode.final,
+ next = undefined
+
+ if (nEdge in frame.output.edges) {
+ // an edge already exists for this character
+ // no need to create a new node, just set the finality
+ // bit unless this node is already final
+ next = frame.output.edges[nEdge]
+ next.final = next.final || final
+
+ } else {
+ // no edge exists yet, must create one
+ // set the finality bit and insert it
+ // into the output
+ next = new lunr.TokenSet
+ next.final = final
+ frame.output.edges[nEdge] = next
+ }
+
+ stack.push({
+ qNode: qNode,
+ output: next,
+ node: node
+ })
+ }
+ }
+ }
+ }
+
+ return output
+}
+lunr.TokenSet.Builder = function () {
+ this.previousWord = ""
+ this.root = new lunr.TokenSet
+ this.uncheckedNodes = []
+ this.minimizedNodes = {}
+}
+
+lunr.TokenSet.Builder.prototype.insert = function (word) {
+ var node,
+ commonPrefix = 0
+
+ if (word < this.previousWord) {
+ throw new Error ("Out of order word insertion")
+ }
+
+ for (var i = 0; i < word.length && i < this.previousWord.length; i++) {
+ if (word[i] != this.previousWord[i]) break
+ commonPrefix++
+ }
+
+ this.minimize(commonPrefix)
+
+ if (this.uncheckedNodes.length == 0) {
+ node = this.root
+ } else {
+ node = this.uncheckedNodes[this.uncheckedNodes.length - 1].child
+ }
+
+ for (var i = commonPrefix; i < word.length; i++) {
+ var nextNode = new lunr.TokenSet,
+ char = word[i]
+
+ node.edges[char] = nextNode
+
+ this.uncheckedNodes.push({
+ parent: node,
+ char: char,
+ child: nextNode
+ })
+
+ node = nextNode
+ }
+
+ node.final = true
+ this.previousWord = word
+}
+
+lunr.TokenSet.Builder.prototype.finish = function () {
+ this.minimize(0)
+}
+
+lunr.TokenSet.Builder.prototype.minimize = function (downTo) {
+ for (var i = this.uncheckedNodes.length - 1; i >= downTo; i--) {
+ var node = this.uncheckedNodes[i],
+ childKey = node.child.toString()
+
+ if (childKey in this.minimizedNodes) {
+ node.parent.edges[node.char] = this.minimizedNodes[childKey]
+ } else {
+ // Cache the key for this node since
+ // we know it can't change anymore
+ node.child._str = childKey
+
+ this.minimizedNodes[childKey] = node.child
+ }
+
+ this.uncheckedNodes.pop()
+ }
+}
+/*!
+ * lunr.Index
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * An index contains the built index of all documents and provides a query interface
+ * to the index.
+ *
+ * Usually instances of lunr.Index will not be created using this constructor, instead
+ * lunr.Builder should be used to construct new indexes, or lunr.Index.load should be
+ * used to load previously built and serialized indexes.
+ *
+ * @constructor
+ * @param {Object} attrs - The attributes of the built search index.
+ * @param {Object} attrs.invertedIndex - An index of term/field to document reference.
+ * @param {Object' + noResultsText + '
'); + } +} + +function doSearch () { + var query = document.getElementById('mkdocs-search-query').value; + if (query.length > min_search_length) { + if (!window.Worker) { + displayResults(search(query)); + } else { + searchWorker.postMessage({query: query}); + } + } else { + // Clear results for short queries + displayResults([]); + } +} + +function initSearch () { + var search_input = document.getElementById('mkdocs-search-query'); + if (search_input) { + search_input.addEventListener("keyup", doSearch); + } + var term = getSearchTermFromLocation(); + if (term) { + search_input.value = term; + doSearch(); + } +} + +function onWorkerMessage (e) { + if (e.data.allowSearch) { + initSearch(); + } else if (e.data.results) { + var results = e.data.results; + displayResults(results); + } else if (e.data.config) { + min_search_length = e.data.config.min_search_length-1; + } +} + +if (!window.Worker) { + console.log('Web Worker API not supported'); + // load index in main thread + $.getScript(joinUrl(base_url, "search/worker.js")).done(function () { + console.log('Loaded worker'); + init(); + window.postMessage = function (msg) { + onWorkerMessage({data: msg}); + }; + }).fail(function (jqxhr, settings, exception) { + console.error('Could not load worker.js'); + }); +} else { + // Wrap search in a web worker + var searchWorker = new Worker(joinUrl(base_url, "search/worker.js")); + searchWorker.postMessage({init: true}); + searchWorker.onmessage = onWorkerMessage; +} diff --git a/search/search_index.json b/search/search_index.json new file mode 100644 index 0000000..cfca5bd --- /dev/null +++ b/search/search_index.json @@ -0,0 +1 @@ +{"config":{"indexing":"full","lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-\\.]+"},"docs":[{"location":"","text":"Welcome to HDZero VTX Docs! What is HDZero? PUSH YOUR SKILLS TO THE LIMIT HDZero offers industry-leading low latency, giving you more time to react and the best possible chance of hitting that next gap. With its smooth, consistent FPV video feed, you'll experience the same locked-in feeling you get with analog video\u2013but with the clarity of HD. MAKE IT AN EVENT HDZero supports the standard 5.8ghz video channels, meaning you can have up to 8 simultaneous pilots flying either full-quality HDZero or analog video. When you're ready to take a break and spectate, you can tune in to any channel and view the pilot's feed with no loss of quality, giving you the same feeling of being in the air yourself. UPGRADE YOUR FLEET From 1S whoops to long-range wings, HDZero offers a variety of VTX and camera options to suit every build. You may even be able to use the gear you already have\u2013the HDZero receiver will work with any FPV goggle with an HDMI input. HDZero can grow with your needs and fit perfectly into your preferred FPV craft. RAPIDLY EVOLVING SYSTEM HDZero is rapidly evolving. Please always use the latest firmware that is located at www.hd-zero.com/document .","title":"Home"},{"location":"#welcome-to-hdzero-vtx-docs","text":"","title":"Welcome to HDZero VTX Docs!"},{"location":"#what-is-hdzero","text":"PUSH YOUR SKILLS TO THE LIMIT HDZero offers industry-leading low latency, giving you more time to react and the best possible chance of hitting that next gap. With its smooth, consistent FPV video feed, you'll experience the same locked-in feeling you get with analog video\u2013but with the clarity of HD. MAKE IT AN EVENT HDZero supports the standard 5.8ghz video channels, meaning you can have up to 8 simultaneous pilots flying either full-quality HDZero or analog video. When you're ready to take a break and spectate, you can tune in to any channel and view the pilot's feed with no loss of quality, giving you the same feeling of being in the air yourself. UPGRADE YOUR FLEET From 1S whoops to long-range wings, HDZero offers a variety of VTX and camera options to suit every build. You may even be able to use the gear you already have\u2013the HDZero receiver will work with any FPV goggle with an HDMI input. HDZero can grow with your needs and fit perfectly into your preferred FPV craft. RAPIDLY EVOLVING SYSTEM HDZero is rapidly evolving. Please always use the latest firmware that is located at www.hd-zero.com/document .","title":"What is HDZero?"},{"location":"about/","text":"About When the PR submitted by the open source community to hdzero-vtx will affect users, corresponding modifications should be submitted to this project at the same time. If troubleshoot does not cover your case and you solve the problem, you can submit your experience in this project to help more users.","title":"About"},{"location":"about/#about","text":"When the PR submitted by the open source community to hdzero-vtx will affect users, corresponding modifications should be submitted to this project at the same time. If troubleshoot does not cover your case and you solve the problem, you can submit your experience in this project to help more users.","title":"About"},{"location":"camera_targets/","text":"Camera Targets TODO","title":"Camera Target"},{"location":"camera_targets/#camera-targets","text":"TODO","title":"Camera Targets"},{"location":"vtx_targets/","text":"VTX Targets Summy VTX Name Whoop(EOL) Whoop Lite Race V1(EOL) Race V2(EOL) Race V3 Freestyle V1 (EOL) Freestyle V2 Dimension(mm x mm) 32x32 32x32 27x45 34x34 28x32 40x40 29x30 Mounting Pattern 25.5x25.5 M2 25.5x25.5 M2 (Soft) 20x20 M4(Soft) 20x20 M4(Soft) 20x20 M4(Soft) 30x30 M3(Soft) 20x20 M2 Weight(grams) 5.3 4.5 7 6 5.5 28 22.3 Power Input 7V-17V 1S-3S 7V-17V 7V-17V 4V-12V 2S-6S (2rd batch or later) 7-25V Power Consumption 5~6W 5~6W 5~6W 5~6W 5~6W 6~15W 6~15W RF Power Output 25mW,200mW 25mW,200mW 25mW,200mW 25mW,200mW 25mW,200mW 25mW,200mW (500mW, 1W if with HAM license 25mW,200mW (500mW, 1W if with HAM license Secured U.FL No Yes Yes Yes Yes Yes Yes Antenna Included Not included Not included Not included Not included Not included Polarized(RHCP) Polarized(RHCP) Tramp/SmartAudio No SmartAudio SmartAudio SmartAudio Tramp SmartAudio SmartAudio Keypad Yes No Yes Yes No Yes Yes Application Whoop TinyWhoop Race Race Race Freestyle Freestyle General Consideration for VTX installation Caution: UFL Connectors Are Fragile All HDZero VTXes use an U.FL connector for its smaller footprint and lighter weight. However, it is not a mechanically strong connector. Treat it as if it\u2019s made of glass. Here are notes for installing and uninstalling an antenna: Never run a cable from the UFL connector straight off the side of a board. Instead, run the antenna cable towards the middle of the board, and secure it in one of the following ways: Hot glue or E6000 glue Avoid using glue on top of the hot components on the board. Preferably, apply glue to the side of the board where the cable leaves the top of the board. Kapton tape to secure it to the surface of the VTX Zip tie it to a nearby standoff Unless you need maximum RF performance or minimum weight, consider a UFL->SMA pigtail for larger builds. This allows you to thoroughly secure the SMA connector to your quad to prevent movement of the antenna cable. When removing the antenna, go very slowly and pull gently on the antenna so that one side of the UFL slides off first. There are tools designed to remove/insert UFL connectors from their sockets, which can help avoid damage to the UFL connector or socket. Please visit the following link for more information: https://www.facebook.com/groups/hdzero/permalink/448657693828864/ Powering the VTX: BEC or VBAT Using a battery eliminator circuit (BEC) is highly recommended to avoid voltage spikes, which can damage the VTX. Although you can power the VTX directly from the battery (VBAT), a BEC will provide more consistent power and will help absorb any voltage spikes, protecting your VTX from over-voltage conditions. It is important to select a BEC that provides voltage that is within the range of what the VTX accepts, and that is capable of supplying enough current to power the VTX. Whether you are using a BEC that is built into your flight controller or a standalone BEC, be sure to check its voltage and current ratings and compare them to the required voltage and current for your VTX. All the FCs that include an integrated BEC for DJI VTXes should also work for HDZero VTXes. To summarize: All HDZero VTXes, except Freestyle Batch 2 VTX or later, do not support 6S VBAT. Check your FC specs to see if you can run your VTX from the FC\u2019s BEC; If not, you could run the VTX from a suitable standalone BEC; If not, solder a capacitor between the +V and Ground on the VTX. Running on VBAT is always the last choice due to the challenging voltage environment in a quad. Mounting Considerations It is very important to keep some distance between the VTX and ESC/FC boards for the following reasons: The RF portion of VTX is vulnerable to electronic noise caused by ESC/motors; The RF signal can be bounced back from surfaces of boards or carbon fiber plate, and fed back to the power amplifier in the VTX. This will deteriorate the RF signal integrity and could damage the amplifier. To avoid these concerns, follow this guidance for mounting the VTX: If the VTX is mounted on the top of the stack, please keep 5mm distance from the top carbon fiber plate. Avoid mounting the VTX in the middle of the stack. If the VTX is mounted on the bottom of the stack, the VTX needs to be upside down (U.FL socket faces down) and needs to have a minimum of 5mm distance from the bottom carbon fiber plate. Targets HDZero Whoop video Transmitter (EOL) The HDZero Whoop VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz. The power input range is 7V \u2013 17V (2S \u2013 4S). Due to the small clearance of mounting holes, make sure the mounting nuts or gummies will not overlap into the small components around the holes. This VTX is designed for low-speed whoop application. Compared to the other HDZero VTXes, it is more vulnerable to be damaged by crash due to: (1) the UFL connector is easily peeled off due to no antenna retention, and (2) it is not easy for soft mounting. Though the VTX can be mounted on a racing and other high-speed quad, it is highly recommended to consider HDZero Race (V1 or V2) for such application. This VTX does not support SmartAudio or Tramp. Notes: Read first: General Consideration for VTX installation Soft mount Pay extra attention not to damage the small components when trying to remove the serrate corner HDZero Whoop Lite Video Transmitter The HDZero Whoop lite VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz. The power input range is 2.8V \u2013 13V (1S-3S). This VTX does not have reserve polarity protection circuit, it will be permanently damaged if voltage input is reservedly connected. This is number one failure cause. When it is powered by a 5V pad of FC/BEC, make sure that 5V has 1.5A current output. When it is powered by an 1S battery directly, note that a rapid throttle up may cause voltage drop below to 2.8V instantly, and that will cause video drop. There is no need for an external capacitor when it connects with FC/BEC or 1S battery. However, it is strongly suggested to put on capacitor when powered by a 3S battery. This VTX has protection cases mounted on both sides. These metal cases are grounded, and to provide protection from crash. They can be removed for tiny whoop quad which cares about every added gram. This VTX includes M3/M2 gummies for soft mounting, and zip ties for antenna retention. Though the VTX can be mounted on a racing and other high-speed quad, it is highly recommended to consider HDZero Race (V1 or V2) for such application. No. Description 1 MIPI Connector 2 Status LEDs 3 Power/UART/SA solder pads 4 u.FL Connector 5 Protection Case 6 Protection case clipper Solder pad: Pad Function G Ground V 2.8V-13V RX FC.TX TX FC.RX SA FC.SA(TX), Optional Notes: Read first: General Consideration for VTX installation This VTX does not support using keypad to tune channel and RF output power level. Ir is designed to work with flight controller. HDZero Race V1 Video Transmitter (EOL) The HDZero Race VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz. The power input range is 7V \u2013 17V (2S \u2013 4S). No. Description 1 Power/UART Connector 2 FW Update Connector 3 MIPI Connector 4 u.FL Antenna Connector 5 u.FL Antenna Retention Holes 6 Power on LED(red) 7 Status LED(blue) 8 Mounting Holes (20x20 M4) 9 Zip Ties (4x) 10 u.FL Antenna Retention Scews(4x)/Nut(4x)/Plate 11 Rubber Grommet(M4 to M3 4x) 12 Power/UART harness (20cm) and a PH2.0 connector (6P) Power/UART Connector Cable Color Connected with Ground Black Ground Power Red Power T1 Green FC.RX R1 Yellow FC.TX T2 White DO NOT CONNECT R2/SA, Optional Gray FC.SA(TX) Connection between Race V1 VTX and FC There are 3 methods to connect the VTX and flight controller: Plug the included harness, cut the cables to appropriate length, and solder them on FC Use solder pads on the back of the connector For FCs having BEC and UART connector, install harness to the included PH2.0 connector (Shown above), and connect the harness with FC without any soldering. Warning: Check that pinout matches the FC pinout before installing to be safe if plugging directly. Mounting an u.FL antenna or pigtail There are 2 methods to mount antenna on VTX: Use included retention screws, nuts and plate. Use included zip-ties. HDZero Race V2 Video Transmitter (EOL) The HDZero Race VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz. It works with the Shark Byte RX5.1 goggle module to transmit video, and with a remote controller to wirelessly control the parameters for the transmitter and camera. The power input range is 7V \u2013 17V (2S \u2013 4S). No. Description 1 Power in (G=Ground, V=7-17V) 2 T1/R1 UART Connection to FC 3 T2, Reserved, R2/SA, SA Pin 4 u.FL Antenna Connector 5 u.FL Antenna Retention Holes 6 MIPI Connector 7 MIPI Connector Retention Holes 8 Firmware Update Connector 9 Power On LED (red) 10 Status LED (blue) 11 u.FL Antenna Retention Screws/Nut/Plate 12 Rubber Grommet (M4 to M3), 1mm O-Ring 13 Zip ties 14 Connecting wire 15 20x20 M4 mounting hoNoles Mounting a u.FL antenna or pigtial There are 2 methods to mount the antenna on VTX: Use included retention screws, nuts and plate; Use included zip-ties. Connecting MIPI cable Use the included zip-tie to secure MIPI cable and protect MIPI connector. Notes: Read first: General Consideration for VTX installation Make sure to use a wider top plate to fully c over this VTX for protection. HDZero Race V3 Video Transmitter Designed for FPV racing, the HDZero Race V3 VTX is our 3rd generation digital video transmitter. With a voltage range starting at 4V, it can be powered by the 5V 1.5A regulator of most FC's or up to 12V for FC's that include a HD VTX plug. It is small (28x32x5mm) and light (5.5 grams). With a width of only 28mm, the VTX is now a similar width to many FC's, which improves durability and reduces weight. The antenna is securely attached with a metal bar and screws. No soldering needed \u2013 just plug the wire harness into a compatible HD-ready FC. The HDZero Race V3 VTX is designed with durability in mind, rather than weight. It is made with a 1.6mm thick PCB, in comparison to the 1.0mm PCB used in the Whoop lite VTX. Moreover, it uses more large package size components for stability consideration. For the smaller components, an additional glue coating is applied to increase crash protection. The HDZero Race V3 VTX offers high-quality video in 540p90, 720p60 and 1080p30 resolutions with 25/200mW switchable power on 5.8GHz. No. Description 1 VTX-R3 board 2 SmartAudio/Tramp (Optional) 3 Wire harness to connect with FC Red = BEC 4-12V Black = GND White = VTX UART TX (Connect to FC RX) Yellow = VTX UART RX (Connect to FC TX) 4 Rubber Grommet (M4 to M3) 5 Metal bar and screws for securing antenna Connection The right figure shows the typical connection with FC supports MSP VTX protocol. The Race V3 supports direct connect with Ghost RX via its SA/Tramp port(TBD) HDZero Freestyle V1 Video Transmitter(EOL) The HDZero Freestyle V1 VTX offers unprecedented range and performance for the HDZero 5.8GHz digital FPV system. With its high maximum output power and robust construction, this VTX is perfect for freestyle and long-range builds. With a tested maximum range of more than 18 miles, the Freestyle V1 VTX will transmit a digital FPV feed as far as you're willing to fly. Not interested in long range? You'll also see better performance in urban environments and around obstacles, with none of the color noise or multipath interference issues of analog video. No. Description 1 Secured MIPI Connector 2 Keypad Connector 3 M3 Mouting Hole 4 Secured u.FL Connector 5 FW Update Connector 6 Power/UART Connector 7* BEC Power In (2S-6S) 8 BEC Power Out Pad 9 RHCP Antenna 10 Power/UART Harness *: BEC is included for first Batch only. Power/UART Connector Cable Color Connected with Ground Black Ground Power Red Power* RX Green FC TX TX Yellow FC RX SA Blue FX SA (TX), Optional *: The 1st batch supports 4S MAX. The 1st batch of Freestyle V1 VTX, supports 2S-4S, A BEC supporting 2S-6S is included. The 2nd batch and later, supports 2S-6S, and the BEC is not included. Important Notes: Do not directly power this VTX with a 5S/6S battery for the 1st batch. Use 2S-4S VBAT, or included BEC, or FC with built-in BEC The Freestyle VTX consumes up to 15W. If it is connected with FC that has a built-in BEC output, make sure the BEC can provide enough current. For example, if the BEC provides 10V, it needs a minimum of 1.5A current output. Removing the heat sink is not recommended because it is part of the design. Rotate the antenna as shown above before detaching it to reduce the risk of peeling off the UFL connector. HDZero Freestyle V2 Video Transmitter The HDZero Freestyle V2 VTX is our 2nd generation 5.8GHz digital video transmitter which can be fitted into most 3-5-inch HD drones. All sockets are well protected by the CNC case that provides durability, RF shielding and improved signal integrity. A wire harness is included for solderless connection for power and MSP UART port. The antenna and MIPI cable are secured by the included retention bar and screws. No. Description 1 Secured MIPI Connector 2 M2 Mouting Hole 3 Secured u.FL Connector 4 Keypad Connector 5 FW Update Connector 6 Power/UART Connector 7 Power/UART Harness Power/UART Connector Cable Color Connected with Ground Black Ground Power Red Power RX Yellow FC TX TX White FC RX SA Blue FC SA(TX), Optional","title":"VTX Target"},{"location":"vtx_targets/#vtx-targets","text":"","title":"VTX Targets"},{"location":"vtx_targets/#summy","text":"VTX Name Whoop(EOL) Whoop Lite Race V1(EOL) Race V2(EOL) Race V3 Freestyle V1 (EOL) Freestyle V2 Dimension(mm x mm) 32x32 32x32 27x45 34x34 28x32 40x40 29x30 Mounting Pattern 25.5x25.5 M2 25.5x25.5 M2 (Soft) 20x20 M4(Soft) 20x20 M4(Soft) 20x20 M4(Soft) 30x30 M3(Soft) 20x20 M2 Weight(grams) 5.3 4.5 7 6 5.5 28 22.3 Power Input 7V-17V 1S-3S 7V-17V 7V-17V 4V-12V 2S-6S (2rd batch or later) 7-25V Power Consumption 5~6W 5~6W 5~6W 5~6W 5~6W 6~15W 6~15W RF Power Output 25mW,200mW 25mW,200mW 25mW,200mW 25mW,200mW 25mW,200mW 25mW,200mW (500mW, 1W if with HAM license 25mW,200mW (500mW, 1W if with HAM license Secured U.FL No Yes Yes Yes Yes Yes Yes Antenna Included Not included Not included Not included Not included Not included Polarized(RHCP) Polarized(RHCP) Tramp/SmartAudio No SmartAudio SmartAudio SmartAudio Tramp SmartAudio SmartAudio Keypad Yes No Yes Yes No Yes Yes Application Whoop TinyWhoop Race Race Race Freestyle Freestyle","title":"Summy"},{"location":"vtx_targets/#general-consideration-for-vtx-installation","text":"","title":"General Consideration for VTX installation"},{"location":"vtx_targets/#caution-ufl-connectors-are-fragile","text":"All HDZero VTXes use an U.FL connector for its smaller footprint and lighter weight. However, it is not a mechanically strong connector. Treat it as if it\u2019s made of glass. Here are notes for installing and uninstalling an antenna: Never run a cable from the UFL connector straight off the side of a board. Instead, run the antenna cable towards the middle of the board, and secure it in one of the following ways: Hot glue or E6000 glue Avoid using glue on top of the hot components on the board. Preferably, apply glue to the side of the board where the cable leaves the top of the board. Kapton tape to secure it to the surface of the VTX Zip tie it to a nearby standoff Unless you need maximum RF performance or minimum weight, consider a UFL->SMA pigtail for larger builds. This allows you to thoroughly secure the SMA connector to your quad to prevent movement of the antenna cable. When removing the antenna, go very slowly and pull gently on the antenna so that one side of the UFL slides off first. There are tools designed to remove/insert UFL connectors from their sockets, which can help avoid damage to the UFL connector or socket. Please visit the following link for more information: https://www.facebook.com/groups/hdzero/permalink/448657693828864/","title":"Caution: UFL Connectors Are Fragile"},{"location":"vtx_targets/#powering-the-vtx-bec-or-vbat","text":"Using a battery eliminator circuit (BEC) is highly recommended to avoid voltage spikes, which can damage the VTX. Although you can power the VTX directly from the battery (VBAT), a BEC will provide more consistent power and will help absorb any voltage spikes, protecting your VTX from over-voltage conditions. It is important to select a BEC that provides voltage that is within the range of what the VTX accepts, and that is capable of supplying enough current to power the VTX. Whether you are using a BEC that is built into your flight controller or a standalone BEC, be sure to check its voltage and current ratings and compare them to the required voltage and current for your VTX. All the FCs that include an integrated BEC for DJI VTXes should also work for HDZero VTXes. To summarize: All HDZero VTXes, except Freestyle Batch 2 VTX or later, do not support 6S VBAT. Check your FC specs to see if you can run your VTX from the FC\u2019s BEC; If not, you could run the VTX from a suitable standalone BEC; If not, solder a capacitor between the +V and Ground on the VTX. Running on VBAT is always the last choice due to the challenging voltage environment in a quad.","title":"Powering the VTX: BEC or VBAT"},{"location":"vtx_targets/#mounting-considerations","text":"It is very important to keep some distance between the VTX and ESC/FC boards for the following reasons: The RF portion of VTX is vulnerable to electronic noise caused by ESC/motors; The RF signal can be bounced back from surfaces of boards or carbon fiber plate, and fed back to the power amplifier in the VTX. This will deteriorate the RF signal integrity and could damage the amplifier. To avoid these concerns, follow this guidance for mounting the VTX: If the VTX is mounted on the top of the stack, please keep 5mm distance from the top carbon fiber plate. Avoid mounting the VTX in the middle of the stack. If the VTX is mounted on the bottom of the stack, the VTX needs to be upside down (U.FL socket faces down) and needs to have a minimum of 5mm distance from the bottom carbon fiber plate.","title":"Mounting Considerations"},{"location":"vtx_targets/#targets","text":"","title":"Targets"},{"location":"vtx_targets/#hdzero-whoop-video-transmitter-eol","text":"The HDZero Whoop VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz. The power input range is 7V \u2013 17V (2S \u2013 4S). Due to the small clearance of mounting holes, make sure the mounting nuts or gummies will not overlap into the small components around the holes. This VTX is designed for low-speed whoop application. Compared to the other HDZero VTXes, it is more vulnerable to be damaged by crash due to: (1) the UFL connector is easily peeled off due to no antenna retention, and (2) it is not easy for soft mounting. Though the VTX can be mounted on a racing and other high-speed quad, it is highly recommended to consider HDZero Race (V1 or V2) for such application. This VTX does not support SmartAudio or Tramp. Notes: Read first: General Consideration for VTX installation Soft mount Pay extra attention not to damage the small components when trying to remove the serrate corner","title":"HDZero Whoop video Transmitter (EOL)"},{"location":"vtx_targets/#hdzero-whoop-lite-video-transmitter","text":"The HDZero Whoop lite VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz. The power input range is 2.8V \u2013 13V (1S-3S). This VTX does not have reserve polarity protection circuit, it will be permanently damaged if voltage input is reservedly connected. This is number one failure cause. When it is powered by a 5V pad of FC/BEC, make sure that 5V has 1.5A current output. When it is powered by an 1S battery directly, note that a rapid throttle up may cause voltage drop below to 2.8V instantly, and that will cause video drop. There is no need for an external capacitor when it connects with FC/BEC or 1S battery. However, it is strongly suggested to put on capacitor when powered by a 3S battery. This VTX has protection cases mounted on both sides. These metal cases are grounded, and to provide protection from crash. They can be removed for tiny whoop quad which cares about every added gram. This VTX includes M3/M2 gummies for soft mounting, and zip ties for antenna retention. Though the VTX can be mounted on a racing and other high-speed quad, it is highly recommended to consider HDZero Race (V1 or V2) for such application. No. Description 1 MIPI Connector 2 Status LEDs 3 Power/UART/SA solder pads 4 u.FL Connector 5 Protection Case 6 Protection case clipper Solder pad: Pad Function G Ground V 2.8V-13V RX FC.TX TX FC.RX SA FC.SA(TX), Optional Notes: Read first: General Consideration for VTX installation This VTX does not support using keypad to tune channel and RF output power level. Ir is designed to work with flight controller.","title":"HDZero Whoop Lite Video Transmitter"},{"location":"vtx_targets/#hdzero-race-v1-video-transmitter-eol","text":"The HDZero Race VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz. The power input range is 7V \u2013 17V (2S \u2013 4S). No. Description 1 Power/UART Connector 2 FW Update Connector 3 MIPI Connector 4 u.FL Antenna Connector 5 u.FL Antenna Retention Holes 6 Power on LED(red) 7 Status LED(blue) 8 Mounting Holes (20x20 M4) 9 Zip Ties (4x) 10 u.FL Antenna Retention Scews(4x)/Nut(4x)/Plate 11 Rubber Grommet(M4 to M3 4x) 12 Power/UART harness (20cm) and a PH2.0 connector (6P) Power/UART Connector Cable Color Connected with Ground Black Ground Power Red Power T1 Green FC.RX R1 Yellow FC.TX T2 White DO NOT CONNECT R2/SA, Optional Gray FC.SA(TX)","title":"HDZero Race V1 Video Transmitter (EOL)"},{"location":"vtx_targets/#connection-between-race-v1-vtx-and-fc","text":"There are 3 methods to connect the VTX and flight controller: Plug the included harness, cut the cables to appropriate length, and solder them on FC Use solder pads on the back of the connector For FCs having BEC and UART connector, install harness to the included PH2.0 connector (Shown above), and connect the harness with FC without any soldering. Warning: Check that pinout matches the FC pinout before installing to be safe if plugging directly.","title":"Connection between Race V1 VTX and FC"},{"location":"vtx_targets/#mounting-an-ufl-antenna-or-pigtail","text":"There are 2 methods to mount antenna on VTX: Use included retention screws, nuts and plate. Use included zip-ties.","title":"Mounting an u.FL antenna or pigtail"},{"location":"vtx_targets/#hdzero-race-v2-video-transmitter-eol","text":"The HDZero Race VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz. It works with the Shark Byte RX5.1 goggle module to transmit video, and with a remote controller to wirelessly control the parameters for the transmitter and camera. The power input range is 7V \u2013 17V (2S \u2013 4S). No. Description 1 Power in (G=Ground, V=7-17V) 2 T1/R1 UART Connection to FC 3 T2, Reserved, R2/SA, SA Pin 4 u.FL Antenna Connector 5 u.FL Antenna Retention Holes 6 MIPI Connector 7 MIPI Connector Retention Holes 8 Firmware Update Connector 9 Power On LED (red) 10 Status LED (blue) 11 u.FL Antenna Retention Screws/Nut/Plate 12 Rubber Grommet (M4 to M3), 1mm O-Ring 13 Zip ties 14 Connecting wire 15 20x20 M4 mounting hoNoles","title":"HDZero Race V2 Video Transmitter (EOL)"},{"location":"vtx_targets/#mounting-a-ufl-antenna-or-pigtial","text":"There are 2 methods to mount the antenna on VTX: Use included retention screws, nuts and plate; Use included zip-ties.","title":"Mounting a u.FL antenna or pigtial"},{"location":"vtx_targets/#connecting-mipi-cable","text":"Use the included zip-tie to secure MIPI cable and protect MIPI connector. Notes: Read first: General Consideration for VTX installation Make sure to use a wider top plate to fully c over this VTX for protection.","title":"Connecting MIPI cable"},{"location":"vtx_targets/#hdzero-race-v3-video-transmitter","text":"Designed for FPV racing, the HDZero Race V3 VTX is our 3rd generation digital video transmitter. With a voltage range starting at 4V, it can be powered by the 5V 1.5A regulator of most FC's or up to 12V for FC's that include a HD VTX plug. It is small (28x32x5mm) and light (5.5 grams). With a width of only 28mm, the VTX is now a similar width to many FC's, which improves durability and reduces weight. The antenna is securely attached with a metal bar and screws. No soldering needed \u2013 just plug the wire harness into a compatible HD-ready FC. The HDZero Race V3 VTX is designed with durability in mind, rather than weight. It is made with a 1.6mm thick PCB, in comparison to the 1.0mm PCB used in the Whoop lite VTX. Moreover, it uses more large package size components for stability consideration. For the smaller components, an additional glue coating is applied to increase crash protection. The HDZero Race V3 VTX offers high-quality video in 540p90, 720p60 and 1080p30 resolutions with 25/200mW switchable power on 5.8GHz. No. Description 1 VTX-R3 board 2 SmartAudio/Tramp (Optional) 3 Wire harness to connect with FC Red = BEC 4-12V Black = GND White = VTX UART TX (Connect to FC RX) Yellow = VTX UART RX (Connect to FC TX) 4 Rubber Grommet (M4 to M3) 5 Metal bar and screws for securing antenna","title":"HDZero Race V3 Video Transmitter"},{"location":"vtx_targets/#connection","text":"The right figure shows the typical connection with FC supports MSP VTX protocol. The Race V3 supports direct connect with Ghost RX via its SA/Tramp port(TBD)","title":"Connection"},{"location":"vtx_targets/#hdzero-freestyle-v1-video-transmittereol","text":"The HDZero Freestyle V1 VTX offers unprecedented range and performance for the HDZero 5.8GHz digital FPV system. With its high maximum output power and robust construction, this VTX is perfect for freestyle and long-range builds. With a tested maximum range of more than 18 miles, the Freestyle V1 VTX will transmit a digital FPV feed as far as you're willing to fly. Not interested in long range? You'll also see better performance in urban environments and around obstacles, with none of the color noise or multipath interference issues of analog video. No. Description 1 Secured MIPI Connector 2 Keypad Connector 3 M3 Mouting Hole 4 Secured u.FL Connector 5 FW Update Connector 6 Power/UART Connector 7* BEC Power In (2S-6S) 8 BEC Power Out Pad 9 RHCP Antenna 10 Power/UART Harness *: BEC is included for first Batch only. Power/UART Connector Cable Color Connected with Ground Black Ground Power Red Power* RX Green FC TX TX Yellow FC RX SA Blue FX SA (TX), Optional *: The 1st batch supports 4S MAX. The 1st batch of Freestyle V1 VTX, supports 2S-4S, A BEC supporting 2S-6S is included. The 2nd batch and later, supports 2S-6S, and the BEC is not included. Important Notes: Do not directly power this VTX with a 5S/6S battery for the 1st batch. Use 2S-4S VBAT, or included BEC, or FC with built-in BEC The Freestyle VTX consumes up to 15W. If it is connected with FC that has a built-in BEC output, make sure the BEC can provide enough current. For example, if the BEC provides 10V, it needs a minimum of 1.5A current output. Removing the heat sink is not recommended because it is part of the design. Rotate the antenna as shown above before detaching it to reduce the risk of peeling off the UFL connector.","title":"HDZero Freestyle V1 Video Transmitter(EOL)"},{"location":"vtx_targets/#hdzero-freestyle-v2-video-transmitter","text":"The HDZero Freestyle V2 VTX is our 2nd generation 5.8GHz digital video transmitter which can be fitted into most 3-5-inch HD drones. All sockets are well protected by the CNC case that provides durability, RF shielding and improved signal integrity. A wire harness is included for solderless connection for power and MSP UART port. The antenna and MIPI cable are secured by the included retention bar and screws. No. Description 1 Secured MIPI Connector 2 M2 Mouting Hole 3 Secured u.FL Connector 4 Keypad Connector 5 FW Update Connector 6 Power/UART Connector 7 Power/UART Harness Power/UART Connector Cable Color Connected with Ground Black Ground Power Red Power RX Yellow FC TX TX White FC RX SA Blue FC SA(TX), Optional","title":"HDZero Freestyle V2 Video Transmitter"},{"location":"vtx_troubleshoot/","text":"Troubleshoot No RF output Description VRX/Goggle cannot scan the VTX signal Solutions 1. Re-update firmware Update to the latest version. Make sure the firmware types matches your VTX. 2. Check the red and blue LED status 1). The red LED is off or unstable The red light is directly driven by the system's 5V power supply. If the red light is not lit stably, it is usually because there is a problem with the power supply. Make sure the voltage and maximum current of the power supply are within the specifications. Check if any components are cracked. There may be a fault with your VTX's power supply system, you can use a multimeter to measure the voltage test pad to verify it if you have the hardware knowledge. 2). The blue LED never lights up Your VTX 5680 chip starts correctly. When the 5680 is initializing, it will first configure the blue LED to be on to indicate that the 5680 mcu has started. If you plug in the Quad battery while the FC is connected to the PC, the VTX may fail to boot although this does not happen often. There may be a fault with your VTX's power supply system, you can use a multimeter to measure the voltage test power to verify it if you have the hardware knowledge. 3). The blue light turns off after a few seconds after powering on At the end of VTX initialization, if the camera is not detected, the blue light will go out. In particular, the foxeer digisight v3 camera cannot be detected but this does not affect the VTX output RF. Replace other camera or mipi cable. Check whether the pins of the mipi socket are intact and ensure that the mipi cable is fastened. Check whether the pins of the 5680 chip are clean. 4). The blue LED stays on Replace other camera or mipi cable. Check whether the pins of the mipi socket are intact and ensure that the mipi cable is fastened. Check whether the pins of the 5680 chip are clean. Use the colorbar firmware to test to make sure the RF part works properly. 5). The blue LED flash as 2Hz Your VTX may be in 0mw mode. You can exit using the following methods. Quad + VTX power on Connect Quad to betaflight configurator Enter vtx page, set power from 0mw to others 6). The blue LED flash as 4Hz For HDZ Freestyle V1/V2, if the VTX overheats, the RF will be automatically shut down until the Quad is armed or repower. 7). The blue LED flashes 2 times per second Your VTX's RF chip dm6300 is damaged, at least it no longer responds to dm5680. Received video exception Desciption There is noise at the edge of the object. Color is wrong. Solutions 1. Re-update firmware Update to the latest version. Make sure the firmware types matches your VTX. 2. Enter the camera menu, reset and save 3. Check VTX PCB Check whether the pins of the mipi socket are intact and ensure that the mipi cable is fastened. Check whether the pins of the 5680 chip are clean. 4. Cross testing Replace the VTX, camera, and mipi cables respectively to identify where the problem lies. 5. Check power supply An unclean power supply may cause the camera to have the wrong color. Please use a DC stabilized voltage source for testing or use a battery for direct power supply. OSD is not display Description Solutions 1. Re-update firmware Update to the latest version. Make sure the firmware types matches your VTX. 2. Check hardware connections VTX TX connects to FC RX VTX RX connects to FC TX Do not connect VTX to the FC's soft serial port. Try other FC UART ports. 3. Check FC configuration 1). Set the function of the FC serial port occupied by VTX, save and restart. For Betaflight, you need to set uart peripheral to VTX(MSP+DISPLAYPORT). The picture below shows setting UART3 to OSD. For iNav, you need to set uart Peripheral to MSP DisplayPort . The picture below shows setting UART5 to OSD. 2). Unsupported OSD items There are some OSD items that require hardware support to actually be enabled, which depends on FC rather than VTX. For example, OSD items related to GPS can only be displayed when FC actually detects the GPS module. OSD display unstable Description OSD flashing OSD VTX channel/pwr display ?:?:? OSD refresh slowly Wrong OSD location Solutions 1. Re-update firmware Update to the latest version. Make sure the firmware types matches your VTX. 2. Reduce OSD items If too many OSD items are turned on, the carrying capacity of the uart may be exceeded, which may cause individual OSD items to be unable to be displayed. 3. Close SmartAudio It is normal for the OSD to flash when SmartAudio is configuring VTX. Please turn off SmartAudio if you don't need it. Snowflakes at close range Description Solutions 1. Re-update firmware Update to the latest version. Make sure the firmware types matches your VTX. 2. Check VTX configuration Make sure pit mode is off 3. Avoid RF interference There may be interference sources in the current channel. Switch to other channels. The RF power of the remote control tuner is too high. Make sure the turner is at least 20cm away from Goggle or VRX. When VTX and VRX or Goggle are too close (less than 1 meter), it is normal for a small amount of snowflakes to appear. 4. Build Quad Correctly Check whether the VTX antenna is installed securely. Try to make sure that the antenna is not blocked by the carbon fiber of the quad or the battery. Replace other antenna for VTX. The top of VTX should be at least 1cm away from the carbon fiber. Add filter capacitors to your Quad. 5. Check VTX hardware Check the front and back of the VTX to see if any components are cracked or falling off. Check whether the PA is damaged. For Freestyle V1 VTX, when the power is off, measure whether the two test points named 5V0 on the front are short-circuited to ground. If short-circuited, it means the PA is damaged. For other VTXes. Measure the voltage from test point PD to GND in the power-on state. Generally, when PD is less than 0.2V, the PA is considered to be working abnormally. HDZero Whoop VTX HDZero WhoopLite VTX HDZero Race V1 VTX HDZero Race V2 VTX HDAZero Race V3 VTX VTX cannot update firmware Description PC/Goggle/VRX cannot detect VTX. VRX does not start updating VRX. Foxeer VTX cannot be updated by HDZero Programmer or Goggle Solutions 1. Make sure the SD card is formatted as FAT32. 2. Make sure the PIN pin of the upgrade socket is intact. Bad socket good socket 3. Updated HDZero Programmer to support Foxeer VTX. 4. Goggle does not currently support updating Foxeer VTX. 5. If you have a keypad plugged in, remove it. VTX interferes with GPS Description After turning on VTX RF, the GPS will lose 4~5 stars. Solutions 1. The VTX installation location is far away from the GPS module. 2. Keep the VTX antenna away from the GPS module. FC dropping to bootloader Description Suolutions Add a 200ohm resistor between the wire from FC UART.TX to VTX UART.RX","title":"Troubleshoot"},{"location":"vtx_troubleshoot/#troubleshoot","text":"","title":"Troubleshoot"},{"location":"vtx_troubleshoot/#no-rf-output","text":"","title":"No RF output"},{"location":"vtx_troubleshoot/#description","text":"VRX/Goggle cannot scan the VTX signal","title":"Description"},{"location":"vtx_troubleshoot/#solutions","text":"","title":"Solutions"},{"location":"vtx_troubleshoot/#1-re-update-firmware","text":"Update to the latest version. Make sure the firmware types matches your VTX.","title":"1. Re-update firmware"},{"location":"vtx_troubleshoot/#2-check-the-red-and-blue-led-status","text":"","title":"2. Check the red and blue LED status"},{"location":"vtx_troubleshoot/#1-the-red-led-is-off-or-unstable","text":"The red light is directly driven by the system's 5V power supply. If the red light is not lit stably, it is usually because there is a problem with the power supply. Make sure the voltage and maximum current of the power supply are within the specifications. Check if any components are cracked. There may be a fault with your VTX's power supply system, you can use a multimeter to measure the voltage test pad to verify it if you have the hardware knowledge.","title":"1). The red LED is off or unstable"},{"location":"vtx_troubleshoot/#2-the-blue-led-never-lights-up","text":"Your VTX 5680 chip starts correctly. When the 5680 is initializing, it will first configure the blue LED to be on to indicate that the 5680 mcu has started. If you plug in the Quad battery while the FC is connected to the PC, the VTX may fail to boot although this does not happen often. There may be a fault with your VTX's power supply system, you can use a multimeter to measure the voltage test power to verify it if you have the hardware knowledge.","title":"2). The blue LED never lights up"},{"location":"vtx_troubleshoot/#3-the-blue-light-turns-off-after-a-few-seconds-after-powering-on","text":"At the end of VTX initialization, if the camera is not detected, the blue light will go out. In particular, the foxeer digisight v3 camera cannot be detected but this does not affect the VTX output RF. Replace other camera or mipi cable. Check whether the pins of the mipi socket are intact and ensure that the mipi cable is fastened. Check whether the pins of the 5680 chip are clean.","title":"3). The blue light turns off after a few seconds after powering on"},{"location":"vtx_troubleshoot/#4-the-blue-led-stays-on","text":"Replace other camera or mipi cable. Check whether the pins of the mipi socket are intact and ensure that the mipi cable is fastened. Check whether the pins of the 5680 chip are clean. Use the colorbar firmware to test to make sure the RF part works properly.","title":"4). The blue LED stays on"},{"location":"vtx_troubleshoot/#5-the-blue-led-flash-as-2hz","text":"Your VTX may be in 0mw mode. You can exit using the following methods. Quad + VTX power on Connect Quad to betaflight configurator Enter vtx page, set power from 0mw to others","title":"5). The blue LED flash as 2Hz"},{"location":"vtx_troubleshoot/#6-the-blue-led-flash-as-4hz","text":"For HDZ Freestyle V1/V2, if the VTX overheats, the RF will be automatically shut down until the Quad is armed or repower.","title":"6). The blue LED flash as 4Hz"},{"location":"vtx_troubleshoot/#7-the-blue-led-flashes-2-times-per-second","text":"Your VTX's RF chip dm6300 is damaged, at least it no longer responds to dm5680.","title":"7). The blue LED flashes 2 times per second"},{"location":"vtx_troubleshoot/#received-video-exception","text":"","title":"Received video exception"},{"location":"vtx_troubleshoot/#desciption","text":"There is noise at the edge of the object. Color is wrong.","title":"Desciption"},{"location":"vtx_troubleshoot/#solutions_1","text":"","title":"Solutions"},{"location":"vtx_troubleshoot/#1-re-update-firmware_1","text":"Update to the latest version. Make sure the firmware types matches your VTX.","title":"1. Re-update firmware"},{"location":"vtx_troubleshoot/#2-enter-the-camera-menu-reset-and-save","text":"","title":"2. Enter the camera menu, reset and save"},{"location":"vtx_troubleshoot/#3-check-vtx-pcb","text":"Check whether the pins of the mipi socket are intact and ensure that the mipi cable is fastened. Check whether the pins of the 5680 chip are clean.","title":"3. Check VTX PCB"},{"location":"vtx_troubleshoot/#4-cross-testing","text":"Replace the VTX, camera, and mipi cables respectively to identify where the problem lies.","title":"4. Cross testing"},{"location":"vtx_troubleshoot/#5-check-power-supply","text":"An unclean power supply may cause the camera to have the wrong color. Please use a DC stabilized voltage source for testing or use a battery for direct power supply.","title":"5. Check power supply"},{"location":"vtx_troubleshoot/#osd-is-not-display","text":"","title":"OSD is not display"},{"location":"vtx_troubleshoot/#description_1","text":"","title":"Description"},{"location":"vtx_troubleshoot/#solutions_2","text":"","title":"Solutions"},{"location":"vtx_troubleshoot/#1-re-update-firmware_2","text":"Update to the latest version. Make sure the firmware types matches your VTX.","title":"1. Re-update firmware"},{"location":"vtx_troubleshoot/#2-check-hardware-connections","text":"VTX TX connects to FC RX VTX RX connects to FC TX Do not connect VTX to the FC's soft serial port. Try other FC UART ports.","title":"2. Check hardware connections"},{"location":"vtx_troubleshoot/#3-check-fc-configuration","text":"","title":"3. Check FC configuration"},{"location":"vtx_troubleshoot/#1-set-the-function-of-the-fc-serial-port-occupied-by-vtx-save-and-restart","text":"For Betaflight, you need to set uart peripheral to VTX(MSP+DISPLAYPORT). The picture below shows setting UART3 to OSD. For iNav, you need to set uart Peripheral to MSP DisplayPort . The picture below shows setting UART5 to OSD.","title":"1). Set the function of the FC serial port occupied by VTX, save and restart."},{"location":"vtx_troubleshoot/#2-unsupported-osd-items","text":"There are some OSD items that require hardware support to actually be enabled, which depends on FC rather than VTX. For example, OSD items related to GPS can only be displayed when FC actually detects the GPS module.","title":"2). Unsupported OSD items"},{"location":"vtx_troubleshoot/#osd-display-unstable","text":"","title":"OSD display unstable"},{"location":"vtx_troubleshoot/#description_2","text":"OSD flashing OSD VTX channel/pwr display ?:?:? OSD refresh slowly Wrong OSD location","title":"Description"},{"location":"vtx_troubleshoot/#solutions_3","text":"","title":"Solutions"},{"location":"vtx_troubleshoot/#1-re-update-firmware_3","text":"Update to the latest version. Make sure the firmware types matches your VTX.","title":"1. Re-update firmware"},{"location":"vtx_troubleshoot/#2-reduce-osd-items","text":"If too many OSD items are turned on, the carrying capacity of the uart may be exceeded, which may cause individual OSD items to be unable to be displayed.","title":"2. Reduce OSD items"},{"location":"vtx_troubleshoot/#3-close-smartaudio","text":"It is normal for the OSD to flash when SmartAudio is configuring VTX. Please turn off SmartAudio if you don't need it.","title":"3. Close SmartAudio"},{"location":"vtx_troubleshoot/#snowflakes-at-close-range","text":"","title":"Snowflakes at close range"},{"location":"vtx_troubleshoot/#description_3","text":"","title":"Description"},{"location":"vtx_troubleshoot/#solutions_4","text":"","title":"Solutions"},{"location":"vtx_troubleshoot/#1-re-update-firmware_4","text":"Update to the latest version. Make sure the firmware types matches your VTX.","title":"1. Re-update firmware"},{"location":"vtx_troubleshoot/#2-check-vtx-configuration","text":"Make sure pit mode is off","title":"2. Check VTX configuration"},{"location":"vtx_troubleshoot/#3-avoid-rf-interference","text":"There may be interference sources in the current channel. Switch to other channels. The RF power of the remote control tuner is too high. Make sure the turner is at least 20cm away from Goggle or VRX. When VTX and VRX or Goggle are too close (less than 1 meter), it is normal for a small amount of snowflakes to appear.","title":"3. Avoid RF interference"},{"location":"vtx_troubleshoot/#4-build-quad-correctly","text":"Check whether the VTX antenna is installed securely. Try to make sure that the antenna is not blocked by the carbon fiber of the quad or the battery. Replace other antenna for VTX. The top of VTX should be at least 1cm away from the carbon fiber. Add filter capacitors to your Quad.","title":"4. Build Quad Correctly"},{"location":"vtx_troubleshoot/#5-check-vtx-hardware","text":"Check the front and back of the VTX to see if any components are cracked or falling off. Check whether the PA is damaged. For Freestyle V1 VTX, when the power is off, measure whether the two test points named 5V0 on the front are short-circuited to ground. If short-circuited, it means the PA is damaged. For other VTXes. Measure the voltage from test point PD to GND in the power-on state. Generally, when PD is less than 0.2V, the PA is considered to be working abnormally. HDZero Whoop VTX HDZero WhoopLite VTX HDZero Race V1 VTX HDZero Race V2 VTX HDAZero Race V3 VTX","title":"5. Check VTX hardware"},{"location":"vtx_troubleshoot/#vtx-cannot-update-firmware","text":"","title":"VTX cannot update firmware"},{"location":"vtx_troubleshoot/#description_4","text":"PC/Goggle/VRX cannot detect VTX. VRX does not start updating VRX. Foxeer VTX cannot be updated by HDZero Programmer or Goggle","title":"Description"},{"location":"vtx_troubleshoot/#solutions_5","text":"","title":"Solutions"},{"location":"vtx_troubleshoot/#1-make-sure-the-sd-card-is-formatted-as-fat32","text":"","title":"1. Make sure the SD card is formatted as FAT32."},{"location":"vtx_troubleshoot/#2-make-sure-the-pin-pin-of-the-upgrade-socket-is-intact","text":"Bad socket good socket","title":"2. Make sure the PIN pin of the upgrade socket is intact."},{"location":"vtx_troubleshoot/#3-updated-hdzero-programmer-to-support-foxeer-vtx","text":"","title":"3. Updated HDZero Programmer to support Foxeer VTX."},{"location":"vtx_troubleshoot/#4-goggle-does-not-currently-support-updating-foxeer-vtx","text":"","title":"4. Goggle does not currently support updating Foxeer VTX."},{"location":"vtx_troubleshoot/#5-if-you-have-a-keypad-plugged-in-remove-it","text":"","title":"5. If you have a keypad plugged in, remove it."},{"location":"vtx_troubleshoot/#vtx-interferes-with-gps","text":"","title":"VTX interferes with GPS"},{"location":"vtx_troubleshoot/#description_5","text":"After turning on VTX RF, the GPS will lose 4~5 stars.","title":"Description"},{"location":"vtx_troubleshoot/#solutions_6","text":"","title":"Solutions"},{"location":"vtx_troubleshoot/#1-the-vtx-installation-location-is-far-away-from-the-gps-module","text":"","title":"1. The VTX installation location is far away from the GPS module."},{"location":"vtx_troubleshoot/#2-keep-the-vtx-antenna-away-from-the-gps-module","text":"","title":"2. Keep the VTX antenna away from the GPS module."},{"location":"vtx_troubleshoot/#fc-dropping-to-bootloader","text":"","title":"FC dropping to bootloader"},{"location":"vtx_troubleshoot/#description_6","text":"","title":"Description"},{"location":"vtx_troubleshoot/#suolutions","text":"","title":"Suolutions"},{"location":"vtx_troubleshoot/#add-a-200ohm-resistor-between-the-wire-from-fc-uarttx-to-vtx-uartrx","text":"","title":"Add a 200ohm resistor between the wire from FC UART.TX to VTX UART.RX"},{"location":"vtx_user_manual/","text":"User Manual Power Different VTXs have different power requirements, please refer to the target for detial. Led All VTXes have two LEDs RED LED power indicator light. The VTX lights up when powered on and goes off when powered off. It will not flash. BLUE LED Working status indicator light. flicker 3x after boot indicates MSP signaling is detected. OFF = camera lost (check camera and cabling) ON/OFF @ 1hz = heat protection ON/OFF @ 4hz = 0MW pitt mode active ON/OFF @ 2hz = 0.1mw pitt mode active Flashes quickly 2 times per second = RF chip(dm6300) failure ON solid = VTX operation normal Keypad Note not all VTXes support keypad. UART VTX is connected to FC through UART to implement OSD and other functions that require remote control cooperation. Do not use soft serial uart. VTX TX <=> FC RX VTX RX <=> FC TX OSD setup Prerequisition Betaflight >= v4.4.0 iNav >= 4.1.0 FlightOne >= 10.1.1.5576 | 10.1 Alpha 29 Update VTX and VRX/Goggle firmware Download the latest firmware from www.hd-zero.com/document . Firmware package(Rev_ddmmyyyy.zip) contains the firmware for all the VTX and VRX/Goggle. You can also get the latest release fw of vtx and goggle from github. Solder/Connect UART to and available on your FC board See UART abve. Flight Controller Configuration(Use betaflight as example) Connect the FC board to computer with an USB cable Start Betaflight Configurator Go to Port TAB Activite VTX (MSP + Displayport) on UART number that is used to connect the VTX Save and Reboot Note: A soft UART is not supported for VTX (MSP + Displayport). As an example: UART3 on picture below is used for VTX (MSP + Displayport). VTX Table You really don't need to care about it because VTX will automatically configure the vtx table of the FC. Stick Command Before using stick command, make sure that fc uart is set correctly. VTX Menu All HDZero VTXes have the following settings for its RF power level management. These settings can be changed using the VTX menu. CHANNEL All VTXes support R1-R8, E1, F1, F2 and F4 channels. You will get an additional 8 channels L1-L8 if you unlock the lowband. POWER The desired RF power level is selectable between 25mW, 200mW (and 500mW or MAX for certain VTXes). The actual RF power level depends on the following settings and FC status. LP_MODE OFF: The output RF power will be set to POWER setting. ON: If PIT_MODE is OFF and the quad is disarmed, the RF power level will be forced to 25mW regardless of POWER setting.The output RF power will be set to POWER setting when quad is armed. 1ST : If PIT_MODE is OFF, the RF power level will be forced to 25mW regardless of POWER setting when QUAD is power on, The output RF power will be set to POWER setting when QUAD is armed. Note that after first arm, the vtx will not enter lp mode again until vbat power is reset. PIT_MODE OFF: The output RF power will be set to POWER setting. P1MW: The output RF power will be 0.1mW (in order to not interfere with other pilots) in this mode. If the quad is armed, RF output power will be automatically set to the POWER within seconds. 0MW: There will be zero RF output in this mode. If quad is armed, RF output power will be automatically set to POWER within seconds. Note that after first arm, the vtx will not enter pit mode again until vbat power is reset. OFFSET_25MW It is to fine tune the RF output power to be exactly 25mW. The range is [-10:10], and step size is about 0.3dB per step. TEAM_RACE OFF: The RF power of VTXs after power-on is determined by other settings. MODE1: VTX RF remains off (0mW) after power-up, and exits 0mW under the following conditions: 1. Quad is armed. 2. Exit 0mw mode through stick command. 3. Configure VTX power to non-0mW through FC UART or SmartAudio. If the UART communication between VTX and FC is disconnected, VTX will turn off the RF until UART communication is restored and repower the VTX. MODE2 : VTX RF remains off(0mW) after power-up, and exits 0mW under the following conditions: 1. Quad is armed. 2. Exit 0mw mode through stick command. 3. Configure VTX power to non-0mW through FC. SHORTCUTS Two different stick commands are provided for switching or exiting 0mW. See the Stick Movement diagram for details. Notes: HDZero VTX will still become hot even on P1mW mode. It is better to keep VTX on 0mW when it will be idle for a while. Though the receiver will not have live video on this mode, it will come back as soon as the quad is armed. Use sticks shortcut to enter 0mW, and to exit 0mW mode. Smartaudio Protocol\uff08Not recommend\uff09 HDZero VTX can be controlled by FC using the TBS SmartAudio V2.1. In this case, the VTX will output RF power and channel commanded by FC directly. To avoid conflict, If SmartAudio is enabled, only OFFSET_25MW and SHORTCUTS are available in the VTX menu. Note: HDZero VTX outputs 0.1mW when SmartAudio PIT mode is ON. HDZero VTX does not support SmartAudio out range PIT mode. When HDZero Race VTX boots up, it will automatically detect the existence of a valid SmartAudio link with FC within 10 seconds. If the link exists, FC will fully control race VTX\u2019s RF output power and working frequency. You don't need to set up the vtx table manually for betaflight, VTX will set it up automatically via uart port. With SmartAudio, the user can change channel number and power level even when quad is in the air. Unlock RF POWER Limit HDZero Freestyle V1/V2 VTX is compliant with FCC 47 CFR 97.215(c). It is limited to 25mW/200mW out of the box, but it is capable of up to 1W if you have the required HAM radio license to use this power output. Download the special firmware from www.hd-zero.com/document to enable higher RF output modes. Here are the steps: Download firmware Unlock_FreestyleVTX.zip. Unzip it to the root directory of SD Card. Use the VRX to flash this firmware to the VTX. Power on the VTX, BLUE LED will flash 3 times after it is done. This step unlocks VTX. Power the VTX off. Unzip normal VTX firmware to the root directory of SD Card. Use the VRX to flash this firmware to the VTX. The higher RF output options will now be available. Please note once the VTX is unlocked, there is no need to unlock it again when there is newer firmware available. Unlock Low band The VTX low band needs to be unlocked before it can be used. Make sure your region allows low band before unlocking. To unlock low band for VTX: Here are the steps: Download Unlock_Lowband.zip from www.hd-zero.com/document . Unzip and flash as firmware update to your VTX. Power on VTX, BLUE LED flashes 5 times and then goes out, unlock completed. Flash the latest release firmware to your VTX. When you switch channels in the VTX menu you will see additional channels from L1 to L8.","title":"User Manual"},{"location":"vtx_user_manual/#user-manual","text":"","title":"User Manual"},{"location":"vtx_user_manual/#power","text":"Different VTXs have different power requirements, please refer to the target for detial.","title":"Power"},{"location":"vtx_user_manual/#led","text":"All VTXes have two LEDs","title":"Led"},{"location":"vtx_user_manual/#red-led","text":"power indicator light. The VTX lights up when powered on and goes off when powered off. It will not flash.","title":"RED LED"},{"location":"vtx_user_manual/#blue-led","text":"Working status indicator light. flicker 3x after boot indicates MSP signaling is detected. OFF = camera lost (check camera and cabling) ON/OFF @ 1hz = heat protection ON/OFF @ 4hz = 0MW pitt mode active ON/OFF @ 2hz = 0.1mw pitt mode active Flashes quickly 2 times per second = RF chip(dm6300) failure ON solid = VTX operation normal","title":"BLUE LED"},{"location":"vtx_user_manual/#keypad","text":"Note not all VTXes support keypad.","title":"Keypad"},{"location":"vtx_user_manual/#uart","text":"VTX is connected to FC through UART to implement OSD and other functions that require remote control cooperation. Do not use soft serial uart. VTX TX <=> FC RX VTX RX <=> FC TX","title":"UART"},{"location":"vtx_user_manual/#osd-setup","text":"","title":"OSD setup"},{"location":"vtx_user_manual/#prerequisition","text":"Betaflight >= v4.4.0 iNav >= 4.1.0 FlightOne >= 10.1.1.5576 | 10.1 Alpha 29","title":"Prerequisition"},{"location":"vtx_user_manual/#update-vtx-and-vrxgoggle-firmware","text":"Download the latest firmware from www.hd-zero.com/document . Firmware package(Rev_ddmmyyyy.zip) contains the firmware for all the VTX and VRX/Goggle. You can also get the latest release fw of vtx and goggle from github.","title":"Update VTX and VRX/Goggle firmware"},{"location":"vtx_user_manual/#solderconnect-uart-to-and-available-on-your-fc-board","text":"See UART abve.","title":"Solder/Connect UART to and available on your FC board"},{"location":"vtx_user_manual/#flight-controller-configurationuse-betaflight-as-example","text":"Connect the FC board to computer with an USB cable Start Betaflight Configurator Go to Port TAB Activite VTX (MSP + Displayport) on UART number that is used to connect the VTX Save and Reboot Note: A soft UART is not supported for VTX (MSP + Displayport). As an example: UART3 on picture below is used for VTX (MSP + Displayport).","title":"Flight Controller Configuration(Use betaflight as example)"},{"location":"vtx_user_manual/#vtx-table","text":"You really don't need to care about it because VTX will automatically configure the vtx table of the FC.","title":"VTX Table"},{"location":"vtx_user_manual/#stick-command","text":"Before using stick command, make sure that fc uart is set correctly.","title":"Stick Command"},{"location":"vtx_user_manual/#vtx-menu","text":"All HDZero VTXes have the following settings for its RF power level management. These settings can be changed using the VTX menu. CHANNEL All VTXes support R1-R8, E1, F1, F2 and F4 channels. You will get an additional 8 channels L1-L8 if you unlock the lowband. POWER The desired RF power level is selectable between 25mW, 200mW (and 500mW or MAX for certain VTXes). The actual RF power level depends on the following settings and FC status. LP_MODE OFF: The output RF power will be set to POWER setting. ON: If PIT_MODE is OFF and the quad is disarmed, the RF power level will be forced to 25mW regardless of POWER setting.The output RF power will be set to POWER setting when quad is armed. 1ST : If PIT_MODE is OFF, the RF power level will be forced to 25mW regardless of POWER setting when QUAD is power on, The output RF power will be set to POWER setting when QUAD is armed. Note that after first arm, the vtx will not enter lp mode again until vbat power is reset. PIT_MODE OFF: The output RF power will be set to POWER setting. P1MW: The output RF power will be 0.1mW (in order to not interfere with other pilots) in this mode. If the quad is armed, RF output power will be automatically set to the POWER within seconds. 0MW: There will be zero RF output in this mode. If quad is armed, RF output power will be automatically set to POWER within seconds. Note that after first arm, the vtx will not enter pit mode again until vbat power is reset. OFFSET_25MW It is to fine tune the RF output power to be exactly 25mW. The range is [-10:10], and step size is about 0.3dB per step. TEAM_RACE OFF: The RF power of VTXs after power-on is determined by other settings. MODE1: VTX RF remains off (0mW) after power-up, and exits 0mW under the following conditions: 1. Quad is armed. 2. Exit 0mw mode through stick command. 3. Configure VTX power to non-0mW through FC UART or SmartAudio. If the UART communication between VTX and FC is disconnected, VTX will turn off the RF until UART communication is restored and repower the VTX. MODE2 : VTX RF remains off(0mW) after power-up, and exits 0mW under the following conditions: 1. Quad is armed. 2. Exit 0mw mode through stick command. 3. Configure VTX power to non-0mW through FC. SHORTCUTS Two different stick commands are provided for switching or exiting 0mW. See the Stick Movement diagram for details. Notes: HDZero VTX will still become hot even on P1mW mode. It is better to keep VTX on 0mW when it will be idle for a while. Though the receiver will not have live video on this mode, it will come back as soon as the quad is armed. Use sticks shortcut to enter 0mW, and to exit 0mW mode.","title":"VTX Menu"},{"location":"vtx_user_manual/#smartaudio-protocolnot-recommend","text":"HDZero VTX can be controlled by FC using the TBS SmartAudio V2.1. In this case, the VTX will output RF power and channel commanded by FC directly. To avoid conflict, If SmartAudio is enabled, only OFFSET_25MW and SHORTCUTS are available in the VTX menu. Note: HDZero VTX outputs 0.1mW when SmartAudio PIT mode is ON. HDZero VTX does not support SmartAudio out range PIT mode. When HDZero Race VTX boots up, it will automatically detect the existence of a valid SmartAudio link with FC within 10 seconds. If the link exists, FC will fully control race VTX\u2019s RF output power and working frequency. You don't need to set up the vtx table manually for betaflight, VTX will set it up automatically via uart port. With SmartAudio, the user can change channel number and power level even when quad is in the air.","title":"Smartaudio Protocol\uff08Not recommend\uff09"},{"location":"vtx_user_manual/#unlock-rf-power-limit","text":"HDZero Freestyle V1/V2 VTX is compliant with FCC 47 CFR 97.215(c). It is limited to 25mW/200mW out of the box, but it is capable of up to 1W if you have the required HAM radio license to use this power output. Download the special firmware from www.hd-zero.com/document to enable higher RF output modes. Here are the steps: Download firmware Unlock_FreestyleVTX.zip. Unzip it to the root directory of SD Card. Use the VRX to flash this firmware to the VTX. Power on the VTX, BLUE LED will flash 3 times after it is done. This step unlocks VTX. Power the VTX off. Unzip normal VTX firmware to the root directory of SD Card. Use the VRX to flash this firmware to the VTX. The higher RF output options will now be available. Please note once the VTX is unlocked, there is no need to unlock it again when there is newer firmware available.","title":"Unlock RF POWER Limit"},{"location":"vtx_user_manual/#unlock-low-band","text":"The VTX low band needs to be unlocked before it can be used. Make sure your region allows low band before unlocking. To unlock low band for VTX: Here are the steps: Download Unlock_Lowband.zip from www.hd-zero.com/document . Unzip and flash as firmware update to your VTX. Power on VTX, BLUE LED flashes 5 times and then goes out, unlock completed. Flash the latest release firmware to your VTX. When you switch channels in the VTX menu you will see additional channels from L1 to L8.","title":"Unlock Low band"}]} \ No newline at end of file diff --git a/search/worker.js b/search/worker.js new file mode 100644 index 0000000..8628dbc --- /dev/null +++ b/search/worker.js @@ -0,0 +1,133 @@ +var base_path = 'function' === typeof importScripts ? '.' : '/search/'; +var allowSearch = false; +var index; +var documents = {}; +var lang = ['en']; +var data; + +function getScript(script, callback) { + console.log('Loading script: ' + script); + $.getScript(base_path + script).done(function () { + callback(); + }).fail(function (jqxhr, settings, exception) { + console.log('Error: ' + exception); + }); +} + +function getScriptsInOrder(scripts, callback) { + if (scripts.length === 0) { + callback(); + return; + } + getScript(scripts[0], function() { + getScriptsInOrder(scripts.slice(1), callback); + }); +} + +function loadScripts(urls, callback) { + if( 'function' === typeof importScripts ) { + importScripts.apply(null, urls); + callback(); + } else { + getScriptsInOrder(urls, callback); + } +} + +function onJSONLoaded () { + data = JSON.parse(this.responseText); + var scriptsToLoad = ['lunr.js']; + if (data.config && data.config.lang && data.config.lang.length) { + lang = data.config.lang; + } + if (lang.length > 1 || lang[0] !== "en") { + scriptsToLoad.push('lunr.stemmer.support.js'); + if (lang.length > 1) { + scriptsToLoad.push('lunr.multi.js'); + } + if (lang.includes("ja") || lang.includes("jp")) { + scriptsToLoad.push('tinyseg.js'); + } + for (var i=0; i < lang.length; i++) { + if (lang[i] != 'en') { + scriptsToLoad.push(['lunr', lang[i], 'js'].join('.')); + } + } + } + loadScripts(scriptsToLoad, onScriptsLoaded); +} + +function onScriptsLoaded () { + console.log('All search scripts loaded, building Lunr index...'); + if (data.config && data.config.separator && data.config.separator.length) { + lunr.tokenizer.separator = new RegExp(data.config.separator); + } + + if (data.index) { + index = lunr.Index.load(data.index); + data.docs.forEach(function (doc) { + documents[doc.location] = doc; + }); + console.log('Lunr pre-built index loaded, search ready'); + } else { + index = lunr(function () { + if (lang.length === 1 && lang[0] !== "en" && lunr[lang[0]]) { + this.use(lunr[lang[0]]); + } else if (lang.length > 1) { + this.use(lunr.multiLanguage.apply(null, lang)); // spread operator not supported in all browsers: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_operator#Browser_compatibility + } + this.field('title'); + this.field('text'); + this.ref('location'); + + for (var i=0; i < data.docs.length; i++) { + var doc = data.docs[i]; + this.add(doc); + documents[doc.location] = doc; + } + }); + console.log('Lunr index built, search ready'); + } + allowSearch = true; + postMessage({config: data.config}); + postMessage({allowSearch: allowSearch}); +} + +function init () { + var oReq = new XMLHttpRequest(); + oReq.addEventListener("load", onJSONLoaded); + var index_path = base_path + '/search_index.json'; + if( 'function' === typeof importScripts ){ + index_path = 'search_index.json'; + } + oReq.open("GET", index_path); + oReq.send(); +} + +function search (query) { + if (!allowSearch) { + console.error('Assets for search still loading'); + return; + } + + var resultDocuments = []; + var results = index.search(query); + for (var i=0; i < results.length; i++){ + var result = results[i]; + doc = documents[result.ref]; + doc.summary = doc.text.substring(0, 200); + resultDocuments.push(doc); + } + return resultDocuments; +} + +if( 'function' === typeof importScripts ) { + onmessage = function (e) { + if (e.data.init) { + init(); + } else if (e.data.query) { + postMessage({ results: search(e.data.query) }); + } else { + console.error("Worker - Unrecognized message: " + e); + } + }; +} diff --git a/sitemap.xml b/sitemap.xml new file mode 100644 index 0000000..0f8724e --- /dev/null +++ b/sitemap.xml @@ -0,0 +1,3 @@ + +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ VTX Targets
+Summy
+| VTX Name | +Whoop(EOL) | +Whoop Lite | +Race V1(EOL) | +Race V2(EOL) | +Race V3 | +Freestyle V1 (EOL) | +Freestyle V2 | +
|---|---|---|---|---|---|---|---|
| Dimension(mm x mm) | +32x32 | +32x32 | +27x45 | +34x34 | +28x32 | +40x40 | +29x30 | +
| Mounting Pattern | +25.5x25.5 M2 |
+25.5x25.5 M2 (Soft) |
+20x20 M4(Soft) |
+20x20 M4(Soft) |
+20x20 M4(Soft) |
+30x30 M3(Soft) |
+20x20 M2 |
+
| Weight(grams) | +5.3 | +4.5 | +7 | +6 | +5.5 | +28 | +22.3 | +
| Power Input | +7V-17V | +1S-3S | +7V-17V | +7V-17V | +4V-12V | +2S-6S (2rd batch or later) | +7-25V | +
| Power Consumption | +5~6W | +5~6W | +5~6W | +5~6W | +5~6W | +6~15W | +6~15W | +
| RF Power Output | +25mW,200mW | +25mW,200mW | +25mW,200mW | +25mW,200mW | +25mW,200mW | +25mW,200mW (500mW, 1W if with HAM license |
+25mW,200mW (500mW, 1W if with HAM license |
+
| Secured U.FL | +No | +Yes | +Yes | +Yes | +Yes | +Yes | +Yes | +
| Antenna Included | +Not included | +Not included | +Not included | +Not included | +Not included | +Polarized(RHCP) | +Polarized(RHCP) | +
| Tramp/SmartAudio | +No | +SmartAudio | +SmartAudio | +SmartAudio | +Tramp | +SmartAudio | +SmartAudio | +
| Keypad | +Yes | +No | +Yes | +Yes | +No | +Yes | +Yes | +
| Application | +Whoop | +TinyWhoop | +Race | +Race | +Race | +Freestyle | +Freestyle | +
General Consideration for VTX installation
+Caution: UFL Connectors Are Fragile
+All HDZero VTXes use an U.FL connector for its smaller footprint and lighter weight. However, it is not a mechanically strong connector. Treat it as if it’s made of glass. Here are notes for installing and uninstalling an antenna:
+-
+
- Never run a cable from the UFL connector straight off the side of a board. Instead, run the antenna cable towards the middle of the board, and secure it in one of the following ways: +
- Hot glue or E6000 glue
-
+
- Avoid using glue on top of the hot components on the board. +
- Preferably, apply glue to the side of the board where the cable leaves the top of the board. +
+ - Kapton tape to secure it to the surface of the VTX +
- Zip tie it to a nearby standoff +
- Unless you need maximum RF performance or minimum weight, consider a UFL->SMA pigtail for larger builds. This allows you to thoroughly secure the SMA connector to your quad to prevent movement of the antenna cable. +
- When removing the antenna, go very slowly and pull gently on the antenna so that one side of the UFL slides off first. There are tools designed to remove/insert UFL connectors from their sockets, which can help avoid damage to the UFL connector or socket. +
Please visit the following link for more information:
+https://www.facebook.com/groups/hdzero/permalink/448657693828864/
+Powering the VTX: BEC or VBAT
+Using a battery eliminator circuit (BEC) is highly recommended to avoid voltage spikes, which can damage the VTX. Although you can power the VTX directly from the battery (VBAT), a BEC will provide more consistent power and will help absorb any voltage spikes, protecting your VTX from over-voltage conditions.
+It is important to select a BEC that provides voltage that is within the range of what the VTX accepts, and that is capable of supplying enough current to power the VTX. Whether you are using a BEC that is built into your flight controller or a standalone BEC, be sure to check its voltage and current ratings and compare them to the required voltage and current for your VTX.
+All the FCs that include an integrated BEC for DJI VTXes should also work for HDZero VTXes.
+To summarize:
+-
+
- All HDZero VTXes, except Freestyle Batch 2 VTX or later, do not support 6S VBAT. +
- Check your FC specs to see if you can run your VTX from the FC’s BEC; +
- If not, you could run the VTX from a suitable standalone BEC; +
- If not, solder a capacitor between the +V and Ground on the VTX. Running on VBAT is always the last choice due to the challenging voltage environment in a quad. +
Mounting Considerations
+It is very important to keep some distance between the VTX and ESC/FC boards for the following reasons:
+-
+
- The RF portion of VTX is vulnerable to electronic noise caused by ESC/motors; +
- The RF signal can be bounced back from surfaces of boards or carbon fiber plate, and fed back to the power amplifier in the VTX. This will deteriorate the RF signal integrity and could damage the amplifier. +
To avoid these concerns, follow this guidance for mounting the VTX:
+-
+
- If the VTX is mounted on the top of the stack, please keep 5mm distance from the top carbon fiber plate. +
- Avoid mounting the VTX in the middle of the stack. +
- If the VTX is mounted on the bottom of the stack, the VTX needs to be upside down (U.FL socket faces down) and needs to have a minimum of 5mm distance from the bottom carbon fiber plate. +
Targets
+HDZero Whoop video Transmitter (EOL)
+The HDZero Whoop VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz.
+The power input range is 7V – 17V (2S – 4S).
+Due to the small clearance of mounting holes, make sure the mounting nuts or gummies will not overlap into +the small components around the holes.
+This VTX is designed for low-speed whoop application. Compared to the other HDZero VTXes, it is more vulnerable to be damaged by crash due to: (1) the UFL connector is easily peeled off due to no antenna retention, and (2) it is not easy for soft mounting. Though the VTX can be mounted on a racing and other high-speed quad, it is highly recommended to consider HDZero Race (V1 or V2) for such application.
+This VTX does not support SmartAudio or Tramp.
+
Notes:
+-
+
- Read first: General Consideration for VTX installation +
- Soft mount +
- Pay extra attention not to damage the small components when trying to remove the serrate corner +
HDZero Whoop Lite Video Transmitter
+The HDZero Whoop lite VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz.
+The power input range is 2.8V – 13V (1S-3S).
+-
+
- This VTX does not have reserve polarity protection circuit, it will be permanently damaged if voltage input is reservedly connected. This is number one failure cause. +
- When it is powered by a 5V pad of FC/BEC, make sure that 5V has 1.5A current output. +
- When it is powered by an 1S battery directly, note that a rapid throttle up may cause voltage drop below to 2.8V instantly, and that will cause video drop. +
- There is no need for an external capacitor when it connects with FC/BEC or 1S battery. However, it is strongly suggested to put on capacitor when powered by a 3S battery. +
This VTX has protection cases mounted on both sides. These metal cases are grounded, and to provide protection from crash. They can be removed for tiny whoop quad which cares about every added gram.
+This VTX includes M3/M2 gummies for soft mounting, and zip ties for antenna retention. Though the VTX can be mounted on a racing and other high-speed quad, it is highly recommended to consider HDZero Race (V1 or V2) for such application.
+
| No. | +Description | +
|---|---|
| 1 | +MIPI Connector | +
| 2 | +Status LEDs | +
| 3 | +Power/UART/SA solder pads | +
| 4 | +u.FL Connector | +
| 5 | +Protection Case | +
| 6 | +Protection case clipper | +
Solder pad:
+| Pad | +Function | +
|---|---|
| G | +Ground | +
| V | +2.8V-13V | +
| RX | +FC.TX | +
| TX | +FC.RX | +
| SA | +FC.SA(TX), Optional | +
Notes:
+-
+
- Read first: General Consideration for VTX installation +
- This VTX does not support using keypad to tune channel and RF output power level. Ir is designed to work with flight controller. +
HDZero Race V1 Video Transmitter (EOL)
+The HDZero Race VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz.
+The power input range is 7V – 17V (2S – 4S).
+
| No. | +Description | +
|---|---|
| 1 | +Power/UART Connector | +
| 2 | +FW Update Connector | +
| 3 | +MIPI Connector | +
| 4 | +u.FL Antenna Connector | +
| 5 | +u.FL Antenna Retention Holes | +
| 6 | +Power on LED(red) | +
| 7 | +Status LED(blue) | +
| 8 | +Mounting Holes (20x20 M4) | +
| 9 | +Zip Ties (4x) | +
| 10 | +u.FL Antenna Retention Scews(4x)/Nut(4x)/Plate |
+
| 11 | +Rubber Grommet(M4 to M3 4x) | +
| 12 | +Power/UART harness (20cm) and a PH2.0 connector (6P) | +
| Power/UART Connector | +Cable Color | +Connected with | +
|---|---|---|
| Ground | +Black | +Ground | +
| Power | +Red | +Power | +
| T1 | +Green | +FC.RX | +
| R1 | +Yellow | +FC.TX | +
| T2 | +White | +DO NOT CONNECT | +
| R2/SA, Optional | +Gray | +FC.SA(TX) | +
Connection between Race V1 VTX and FC
+There are 3 methods to connect the VTX and flight controller:
+-
+
- Plug the included harness, cut the cables to appropriate length, and solder them on FC +
- Use solder pads on the back of the connector +
- For FCs having BEC and UART connector, install harness to the included PH2.0 connector (Shown above), and connect the harness with FC without any soldering. +
Warning: Check that pinout matches the FC pinout before installing to be safe if plugging directly.
+Mounting an u.FL antenna or pigtail
+
There are 2 methods to mount antenna on VTX:
+-
+
- Use included retention screws, nuts and plate. +
- Use included zip-ties. +
HDZero Race V2 Video Transmitter (EOL)
+The HDZero Race VTX is a digital HD 720p 60fps video transmitter capable of delivering up to 200mw on 5.8GHz. It works with the Shark Byte RX5.1 goggle module to transmit video, and with a remote controller to wirelessly control the parameters for the transmitter and camera.
+The power input range is 7V – 17V (2S – 4S).
+
| No. | +Description | +
|---|---|
| 1 | +Power in (G=Ground, V=7-17V) | +
| 2 | +T1/R1 UART Connection to FC | +
| 3 | +T2, Reserved, R2/SA, SA Pin | +
| 4 | +u.FL Antenna Connector | +
| 5 | +u.FL Antenna Retention Holes | +
| 6 | +MIPI Connector | +
| 7 | +MIPI Connector Retention Holes | +
| 8 | +Firmware Update Connector | +
| 9 | +Power On LED (red) | +
| 10 | +Status LED (blue) | +
| 11 | +u.FL Antenna Retention Screws/Nut/Plate | +
| 12 | +Rubber Grommet (M4 to M3), 1mm O-Ring | +
| 13 | +Zip ties | +
| 14 | +Connecting wire | +
| 15 | +20x20 M4 mounting hoNoles | +
Mounting a u.FL antenna or pigtial
+There are 2 methods to mount the antenna on VTX:
+-
+
- Use included retention screws, nuts and plate; +
- Use included zip-ties. +
Connecting MIPI cable
+Use the included zip-tie to secure MIPI cable and protect MIPI connector.
+Notes:
+-
+
- Read first: General Consideration for VTX installation +
- Make sure to use a wider top plate to fully cover this VTX for protection. +
HDZero Race V3 Video Transmitter
+Designed for FPV racing, the HDZero Race V3 VTX is our 3rd generation digital video transmitter. With a voltage range starting at 4V, it can be powered by the 5V 1.5A regulator of most FC's or up to 12V for FC's that include a HD VTX plug. It is small (28x32x5mm) and light (5.5 grams). With a width of only 28mm, the VTX is now a similar width to many FC's, which improves durability and reduces weight. The antenna is securely attached with a metal bar and screws. No soldering needed – just plug the wire harness into a compatible HD-ready FC.
+The HDZero Race V3 VTX is designed with durability in mind, rather than weight. It is made with a 1.6mm thick PCB, in comparison to the 1.0mm PCB used in the Whoop lite VTX. Moreover, it uses more large package size components for stability consideration. For the smaller components, an additional glue coating is applied to increase crash protection.
+The HDZero Race V3 VTX offers high-quality video in 540p90, 720p60 and 1080p30 resolutions with 25/200mW switchable power on 5.8GHz.
+
| No. | +Description | +
|---|---|
| 1 | +VTX-R3 board | +
| 2 | +SmartAudio/Tramp (Optional) | +
| 3 | +Wire harness to connect with FC Red = BEC 4-12V Black = GND White = VTX UART TX (Connect to FC RX) Yellow = VTX UART RX (Connect to FC TX) |
+
| 4 | +Rubber Grommet (M4 to M3) | +
| 5 | +Metal bar and screws for securing antenna | +
Connection
+
The right figure shows the typical connection with FC supports MSP VTX protocol.
+The Race V3 supports direct connect with Ghost RX via its SA/Tramp port(TBD)
+HDZero Freestyle V1 Video Transmitter(EOL)
+The HDZero Freestyle V1 VTX offers unprecedented range and performance for the HDZero 5.8GHz digital FPV system. With its high maximum output power and robust construction, this VTX is perfect for freestyle and long-range builds.
+
With a tested maximum range of more than 18 miles, the Freestyle V1 VTX will transmit a digital FPV feed as far as you're willing to fly. Not interested in long range? You'll also see better performance in urban environments and around obstacles, with none of the color noise or multipath interference issues of analog video.
+
| No. | +Description | +
|---|---|
| 1 | +Secured MIPI Connector | +
| 2 | +Keypad Connector | +
| 3 | +M3 Mouting Hole | +
| 4 | +Secured u.FL Connector | +
| 5 | +FW Update Connector | +
| 6 | +Power/UART Connector | +
| 7* | +BEC Power In (2S-6S) | +
| 8 | +BEC Power Out Pad | +
| 9 | +RHCP Antenna | +
| 10 | +Power/UART Harness | +
*: BEC is included for first Batch only.
+| Power/UART Connector | +Cable Color | +Connected with | +
|---|---|---|
| Ground | +Black | +Ground | +
| Power | +Red | +Power* | +
| RX | +Green | +FC TX | +
| TX | +Yellow | +FC RX | +
| SA | +Blue | +FX SA (TX), Optional | +
*: The 1st batch supports 4S MAX.
+The 1st batch of Freestyle V1 VTX, supports 2S-4S, A BEC supporting 2S-6S is included.
+The 2nd batch and later, supports 2S-6S, and the BEC is not included.
+
Important Notes:
+-
+
- Do not directly power this VTX with a 5S/6S battery for the 1st batch. +
- Use 2S-4S VBAT, or included BEC, or FC with built-in BEC +
- The Freestyle VTX consumes up to 15W. If it is connected with FC that has a built-in BEC output, make sure the BEC can provide enough current. For example, if the BEC provides 10V, it needs a minimum of 1.5A current output. +
- Removing the heat sink is not recommended because it is part of the design. +
- Rotate the antenna as shown above before detaching it to reduce the risk of peeling off the UFL connector. +
HDZero Freestyle V2 Video Transmitter
+The HDZero Freestyle V2 VTX is our 2nd generation 5.8GHz digital video transmitter which can be fitted into most 3-5-inch HD drones. All sockets are well protected by the CNC case that provides durability, RF shielding and improved signal integrity. A wire harness is included for solderless connection for power and MSP UART port. The antenna and MIPI cable are secured by the included retention bar and screws.
+
| No. | +Description | +
|---|---|
| 1 | +Secured MIPI Connector | +
| 2 | +M2 Mouting Hole | +
| 3 | +Secured u.FL Connector | +
| 4 | +Keypad Connector | +
| 5 | +FW Update Connector | +
| 6 | +Power/UART Connector | +
| 7 | +Power/UART Harness | +
| Power/UART Connector | +Cable Color | +Connected with | +
|---|---|---|
| Ground | +Black | +Ground | +
| Power | +Red | +Power | +
| RX | +Yellow | +FC TX | +
| TX | +White | +FC RX | +
| SA | +Blue | +FC SA(TX), Optional | +
+
+
+
+ « Previous
+
+
+ Next »
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/vtx_troubleshoot/index.html b/vtx_troubleshoot/index.html
new file mode 100644
index 0000000..666b52e
--- /dev/null
+++ b/vtx_troubleshoot/index.html
@@ -0,0 +1,398 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Troubleshoot
+No RF output
+Description
+-
+
- VRX/Goggle cannot scan the VTX signal +
Solutions
+1. Re-update firmware
+-
+
- Update to the latest version. +
- Make sure the firmware types matches your VTX. +
2. Check the red and blue LED status
+1). The red LED is off or unstable
+The red light is directly driven by the system's 5V power supply. If the red light is not lit stably, it is usually because there is a problem with the power supply.
+-
+
- Make sure the voltage and maximum current of the power supply are within the specifications. +
- Check if any components are cracked. +
- There may be a fault with your VTX's power supply system, you can use a multimeter to measure the voltage test pad to verify it if you have the hardware knowledge. +
2). The blue LED never lights up
+Your VTX 5680 chip starts correctly.
+When the 5680 is initializing, it will first configure the blue LED to be on to indicate that the 5680 mcu has started.
+-
+
- If you plug in the Quad battery while the FC is connected to the PC, the VTX may fail to boot although this does not happen often. +
- There may be a fault with your VTX's power supply system, you can use a multimeter to measure the voltage test power to verify it if you have the hardware knowledge. +
3). The blue light turns off after a few seconds after powering on
+At the end of VTX initialization, if the camera is not detected, the blue light will go out. In particular, the foxeer digisight v3 camera cannot be detected but this does not affect the VTX output RF.
+-
+
- Replace other camera or mipi cable. +
- Check whether the pins of the mipi socket are intact and ensure that the mipi cable is fastened. +
- Check whether the pins of the 5680 chip are clean. +
4). The blue LED stays on
+-
+
- Replace other camera or mipi cable. +
- Check whether the pins of the mipi socket are intact and ensure that the mipi cable is fastened. +
- Check whether the pins of the 5680 chip are clean. +
- Use the colorbar firmware to test to make sure the RF part works properly. +
5). The blue LED flash as 2Hz
+Your VTX may be in 0mw mode. You can exit using the following methods.
+-
+
- Quad + VTX power on +
- Connect Quad to betaflight configurator +
- Enter vtx page, set power from 0mw to others +
6). The blue LED flash as 4Hz
+For HDZ Freestyle V1/V2, if the VTX overheats, the RF will be automatically shut down until the Quad is armed or repower.
+7). The blue LED flashes 2 times per second
+Your VTX's RF chip dm6300 is damaged, at least it no longer responds to dm5680.
+Received video exception
+Desciption
+-
+
- There is noise at the edge of the object. +
- Color is wrong. +
Solutions
+1. Re-update firmware
+-
+
- Update to the latest version. +
- Make sure the firmware types matches your VTX. +
2. Enter the camera menu, reset and save
+3. Check VTX PCB
+-
+
- Check whether the pins of the mipi socket are intact and ensure that the mipi cable is fastened. +
- Check whether the pins of the 5680 chip are clean. +
4. Cross testing
+Replace the VTX, camera, and mipi cables respectively to identify where the problem lies.
+5. Check power supply
+An unclean power supply may cause the camera to have the wrong color.
+Please use a DC stabilized voltage source for testing or use a battery for direct power supply.
+OSD is not display
+Description
+Solutions
+1. Re-update firmware
+-
+
- Update to the latest version. +
- Make sure the firmware types matches your VTX. +
2. Check hardware connections
+-
+
- VTX TX connects to FC RX +
- VTX RX connects to FC TX +
- Do not connect VTX to the FC's soft serial port. +
- Try other FC UART ports. +
3. Check FC configuration
+1). Set the function of the FC serial port occupied by VTX, save and restart.
+-
+
- For Betaflight, you need to set uart peripheral to VTX(MSP+DISPLAYPORT). The picture below shows setting UART3 to OSD. +
-
+
- For iNav, you need to set uart Peripheral to MSP DisplayPort. The picture below shows setting UART5 to OSD. +
2). Unsupported OSD items
+There are some OSD items that require hardware support to actually be enabled, which depends on FC rather than VTX. For example, OSD items related to GPS can only be displayed when FC actually detects the GPS module.
+OSD display unstable
+Description
+-
+
- OSD flashing +
- OSD VTX channel/pwr display ?:?:? +
- OSD refresh slowly +
- Wrong OSD location +
Solutions
+1. Re-update firmware
+-
+
- Update to the latest version. +
- Make sure the firmware types matches your VTX. +
2. Reduce OSD items
+If too many OSD items are turned on, the carrying capacity of the uart may be exceeded, which may cause individual OSD items to be unable to be displayed.
+3. Close SmartAudio
+It is normal for the OSD to flash when SmartAudio is configuring VTX. Please turn off SmartAudio if you don't need it.
+Snowflakes at close range
+Description
+Solutions
+1. Re-update firmware
+-
+
- Update to the latest version. +
- Make sure the firmware types matches your VTX. +
2. Check VTX configuration
+Make sure pit mode is off
+3. Avoid RF interference
+-
+
- There may be interference sources in the current channel. Switch to other channels. +
- The RF power of the remote control tuner is too high. Make sure the turner is at least 20cm away from Goggle or VRX. +
- When VTX and VRX or Goggle are too close (less than 1 meter), it is normal for a small amount of snowflakes to appear. +
4. Build Quad Correctly
+-
+
- Check whether the VTX antenna is installed securely. Try to make sure that the antenna is not blocked by the carbon fiber of the quad or the battery. +
- Replace other antenna for VTX. +
- The top of VTX should be at least 1cm away from the carbon fiber. +
- Add filter capacitors to your Quad. +
5. Check VTX hardware
+-
+
- Check the front and back of the VTX to see if any components are cracked or falling off. +
- Check whether the PA is damaged. +
- For Freestyle V1 VTX, when the power is off, measure whether the two test points named 5V0 on the front are short-circuited to ground. If short-circuited, it means the PA is damaged.
+
+ - For other VTXes. Measure the voltage from test point PD to GND in the power-on state. Generally, when PD is less than 0.2V, the PA is considered to be working abnormally.
-
+
- HDZero Whoop VTX
+
+ - HDZero WhoopLite VTX
+
+ - HDZero Race V1 VTX
+
+ - HDZero Race V2 VTX
+
+ - HDAZero Race V3 VTX
+
+
+ - HDZero Whoop VTX
+
VTX cannot update firmware
+Description
+-
+
- PC/Goggle/VRX cannot detect VTX. +
- VRX does not start updating VRX. +
- Foxeer VTX cannot be updated by HDZero Programmer or Goggle +
Solutions
+1. Make sure the SD card is formatted as FAT32.
+2. Make sure the PIN pin of the upgrade socket is intact.
+-
+
- Bad socket
+
+ - good socket
+
+
3. Updated HDZero Programmer to support Foxeer VTX.
+4. Goggle does not currently support updating Foxeer VTX.
+5. If you have a keypad plugged in, remove it.
+VTX interferes with GPS
+Description
+After turning on VTX RF, the GPS will lose 4~5 stars.
+Solutions
+1. The VTX installation location is far away from the GPS module.
+2. Keep the VTX antenna away from the GPS module.
+FC dropping to bootloader
+Description
+Suolutions
+Add a 200ohm resistor between the wire from FC UART.TX to VTX UART.RX
+ +
+
+
+
+ « Previous
+
+
+ Next »
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/vtx_user_manual/index.html b/vtx_user_manual/index.html
new file mode 100644
index 0000000..9fd1d2b
--- /dev/null
+++ b/vtx_user_manual/index.html
@@ -0,0 +1,305 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ User Manual
+Power
+Different VTXs have different power requirements, please refer to the target for detial.
+Led
+All VTXes have two LEDs
+RED LED
+power indicator light.
+The VTX lights up when powered on and goes off when powered off. It will not flash.
+BLUE LED
+Working status indicator light.
+-
+
- flicker 3x after boot indicates MSP signaling is detected. +
- OFF = camera lost (check camera and cabling) +
- ON/OFF @ 1hz = heat protection +
- ON/OFF @ 4hz = 0MW pitt mode active +
- ON/OFF @ 2hz = 0.1mw pitt mode active +
- Flashes quickly 2 times per second = RF chip(dm6300) failure +
- ON solid = VTX operation normal +
Keypad
+Note not all VTXes support keypad.
+
UART
+-
+
- VTX is connected to FC through UART to implement OSD and other functions that require remote control cooperation. +
- Do not use soft serial uart. +
- VTX TX <=> FC RX +
- VTX RX <=> FC TX +
OSD setup
+Prerequisition
+-
+
- Betaflight >= v4.4.0 +
- iNav >= 4.1.0 +
- FlightOne >= 10.1.1.5576 | 10.1 Alpha 29 +
Update VTX and VRX/Goggle firmware
+-
+
- Download the latest firmware from www.hd-zero.com/document. +
- Firmware package(Rev_ddmmyyyy.zip) contains the firmware for all the VTX and VRX/Goggle. +
- You can also get the latest release fw of vtx and goggle from github. +
Solder/Connect UART to and available on your FC board
+See UART abve.
+Flight Controller Configuration(Use betaflight as example)
+-
+
- Connect the FC board to computer with an USB cable +
- Start Betaflight Configurator +
- Go to Port TAB +
- Activite VTX (MSP + Displayport) on UART number that is used to connect the VTX +
- Save and Reboot +
Note: A soft UART is not supported for VTX (MSP + Displayport).
+As an example: UART3 on picture below is used for VTX (MSP + Displayport).
+
VTX Table
+You really don't need to care about it because VTX will automatically configure the vtx table of the FC.
+Stick Command
+Before using stick command, make sure that fc uart is set correctly.
+
VTX Menu
+All HDZero VTXes have the following settings for its RF power level management. These settings can be changed using the VTX menu.
+
-
+
- CHANNEL +
- All VTXes support R1-R8, E1, F1, F2 and F4 channels. You will get an additional 8 channels L1-L8 if you unlock the lowband. +
- POWER +
- The desired RF power level is selectable between 25mW, 200mW (and 500mW or MAX for certain VTXes). The actual RF power level depends on the following settings and FC status. +
- LP_MODE +
- OFF: The output RF power will be set to POWER setting. +
- ON: If PIT_MODE is OFF and the quad is disarmed, the RF power level will be forced to 25mW regardless of POWER setting.The output RF power will be set to POWER setting when quad is armed. +
- 1ST: If PIT_MODE is OFF, the RF power level will be forced to 25mW regardless of POWER setting when QUAD is power on, The output RF power will be set to POWER setting when QUAD is armed. +
- Note that after first arm, the vtx will not enter lp mode again until vbat power is reset. +
- PIT_MODE +
- OFF: The output RF power will be set to POWER setting. +
- P1MW: The output RF power will be 0.1mW (in order to not interfere with other pilots) in this mode. If the quad is armed, RF output power will be automatically set to the POWER within seconds. +
- 0MW: There will be zero RF output in this mode. If quad is armed, RF output power will be automatically set to POWER within seconds. +
- Note that after first arm, the vtx will not enter pit mode again until vbat power is reset. +
- OFFSET_25MW +
- It is to fine tune the RF output power to be exactly 25mW. The range is [-10:10], and step size is about 0.3dB per step. +
- TEAM_RACE +
- OFF: The RF power of VTXs after power-on is determined by other settings. +
- MODE1: VTX RF remains off (0mW) after power-up, and exits 0mW under the following conditions: 1. Quad is armed. 2. Exit 0mw mode through stick command. 3. Configure VTX power to non-0mW through FC UART or SmartAudio. If the UART communication between VTX and FC is disconnected, VTX will turn off the RF until UART communication is restored and repower the VTX. +
- MODE2: VTX RF remains off(0mW) after power-up, and exits 0mW under the following conditions: 1. Quad is armed. 2. Exit 0mw mode through stick command. 3. Configure VTX power to non-0mW through FC. +
- SHORTCUTS +
- Two different stick commands are provided for switching or exiting 0mW. See the Stick Movement diagram for details. +
Notes:
+-
+
- HDZero VTX will still become hot even on P1mW mode. It is better to keep VTX on 0mW when it will be idle for a while. Though the receiver will not have live video on this mode, it will come back as soon as the quad is armed. +
- Use sticks shortcut to enter 0mW, and to exit 0mW mode. +
Smartaudio Protocol（Not recommend）
+HDZero VTX can be controlled by FC using the TBS SmartAudio V2.1. In this case, the VTX will output RF power and channel commanded by FC directly. To avoid conflict, If SmartAudio is enabled, only OFFSET_25MW and SHORTCUTS are available in the VTX menu.
+Note:
+-
+
- HDZero VTX outputs 0.1mW when SmartAudio PIT mode is ON. +
- HDZero VTX does not support SmartAudio out range PIT mode. +
- When HDZero Race VTX boots up, it will automatically detect the existence of a valid SmartAudio link with FC within 10 seconds. If the link exists, FC will fully control race VTX’s RF output power and working frequency. +
You don't need to set up the vtx table manually for betaflight, VTX will set it up automatically via uart port.
+With SmartAudio, the user can change channel number and power level even when quad is in the air.
+Unlock RF POWER Limit
+HDZero Freestyle V1/V2 VTX is compliant with FCC 47 CFR 97.215(c). It is limited to 25mW/200mW out of the box, but it is capable of up to 1W if you have the required HAM radio license to use this power output. Download the special firmware from www.hd-zero.com/document to enable higher RF output modes.
+Here are the steps:
+-
+
- Download firmware Unlock_FreestyleVTX.zip. +
- Unzip it to the root directory of SD Card. +
- Use the VRX to flash this firmware to the VTX. +
- Power on the VTX, BLUE LED will flash 3 times after it is done. This step unlocks VTX. +
- Power the VTX off. +
- Unzip normal VTX firmware to the root directory of SD Card. +
- Use the VRX to flash this firmware to the VTX. +
- The higher RF output options will now be available. +
Please note once the VTX is unlocked, there is no need to unlock it again when there is newer firmware available.
+Unlock Low band
+The VTX low band needs to be unlocked before it can be used. Make sure your region allows low band before unlocking. To unlock low band for VTX:
+Here are the steps:
+-
+
- Download Unlock_Lowband.zip from www.hd-zero.com/document. +
- Unzip and flash as firmware update to your VTX. +
- Power on VTX, BLUE LED flashes 5 times and then goes out, unlock completed. +
- Flash the latest release firmware to your VTX. When you switch channels in the VTX menu you will see additional channels from L1 to L8. +
+
+
+
+ « Previous
+
+
+ Next »
+
+
+
+
+
+
+
+
+
+
+
+