RoboPad Wiki - User contributions [en]

File:Button-node.png

2023-02-27T01:45:55Z

WikiSysop: A screenshot of the Button node.

== Summary ==
A screenshot of the Button node.

IO Config Editor

2023-02-26T01:53:35Z

WikiSysop: Protected "IO Config Editor" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

'''''NOTICE: This page consists of information on a feature currently in [[Beta]]. Information is liable to change or be incomplete.'''''

The Input/Output (IO) Configuration Editor page is the page where you can edit the physical IO configuration of the RoboPad board by configuring '''IO Units'''. You can, for instance, set one of the [[:File:Screenshot from 2022-11-06 23-38-46.png|external pins]] to output a digital electronic signal, which can be controlled via the [[Nodegraph Editor|nodegraph]]. It is accessible via the [[The Management Page|Management Page.]]
[[File:The default IO Configuration Editor page 2023-02-19.png|thumb|The default IO Configuration Editor page as of 2023-02-19]]
Each '''IO Unit''' has a number of settings and will add it's own input and output ports to the [[Chip Node]] in the [[Nodegraph Editor|nodegraph]]. Importantly, for actuators, you are able to specify '''safe values''' - these are the values that the IO Unit will default to when the RoboPad looses connection to your phone or you are on any screen other than the controller screen (it's [[emergency stop state]]). It is very important that you understand how your safe values and IO Units in general interact with the physical circuitry you have added to your RoboPad - for instance, if you are adding an additional motor to your robot using a Generic PWM IO Unit, you will most likely want to ensure that it's safe value is set to 0 so that it will turn off in an emergency situation. Some IO Units do not have safe value settings (such as HBridge motors and unidirectional brushless motors) as all of these configurations are configured to turn off by default.

'''Changing the physical configuration of the RoboPad and the behaviour of it's pins using the IO Configuration Editor should be considered an advanced topic - ensure that you have read and fully understand everything on this wiki page and everything you are doing before attempting to change these settings.'''

=== Emergency Stop Behaviour When Changing IO Unit Configuration ===
It is also important to understand that IO Unit safe values '''remain configured''' on the pins they are set to, '''even when removed''' (using the red "x") until either '''another IO Unit is configured to use that pin''' or the '''device is reset'''. This has been done because it is '''not recommended, expected or suggested''' that a user would change the physical configuration of their RoboPad circuit without first powering it down. Therefore, the firmware assumes that the safest thing to do is retain the last set safe value for any given pin until it is told otherwise (or the device is power cycled, at which point unconfigured pins remain at a high-impedance state).

=== "Advanced Pins" ===
Some Pins - namely all pins that are not External 1 and External 2 (marked E1 and E2 respectively on the board) are considered ''Advanced Pins''. This is because they may behave in a way outside of expected behaviour. For instance, many of these pins will output arbitrary signals within the first 500 milliseconds of RoboPad boot and as such should not be used for actuators that may cause harm if they were to unexpectedly move. Others (particularly the "Internal" pins) are already connected to some internal electronics on the RoboPad, such as the built-in HBridge that drives the default M1 and M2 outputs. In order to use these pins, you would have to remove the HBridge from the device (which is not advised and will void the product's guarantee).

== Pins ==
[[File:Screenshot from 2022-11-06 23-38-46.png|thumb|Accessible pins, as they are seen on the RoboPad.]]
All pins are capable of driving a small current at 3.3v to external circuitry, below is a list of the different pin names and how they might be used.
{| class="wikitable"
|+Pin names, IDs and additional information
!Pin Name
!ID on Board
!Information
|-
|External 1
|E1
|Non-advanced pin.
|-
|External 2
|E2
|Non-advanced pin.
|-
|TX
|T
|The "Transmit" pin when manually reprogramming the RoboPad.
Subject to pseudo-random signal state for the first 500ms after RoboPad boot.
|-
|RX
|R
|The "Recieve" pin when manually reprogramming the RoboPad.
Subject to pseudo-random signal state for the first 500ms after RoboPad boot.
|-
|Safeboot
|SB
|Pulled '''low''' through an on-board 10kΩ resistor, and meant to be connected to the 3.3v pin (pulling it '''high''') at the 4 seconds after boot point to enable [[Safeboot|safeboot.]]
Subject to pseudo-random signal state for the first 500ms after RoboPad boot.
|-
|Program Enable
|PE
|Used along with the TX and RX pins to manually reprogram the RoboPad.
Subject to pseudo-random signal state for the first 500ms after RoboPad boot.
|-
|Unset
|
|When "Unset" is available, the pin may optionally be non-configured. Choosing this option means no pin is used for the particular option.
|-
|Drive Enable
|Internal
|An internal pin used to enable or disable the built-in HBridge chip.
Subject to pseudo-random signal state for the first 500ms after RoboPad boot.
|-
|Drive Pin 1
Forward
|Internal
|An internal pin attached to the built-in HBridge chip.
Subject to pseudo-random signal state for the first 500ms after RoboPad boot.
|-
|Drive Pin 1
Backward
|Internal
|An internal pin attached to the built-in HBridge chip.
Subject to pseudo-random signal state for the first 500ms after RoboPad boot.
|-
|Drive Pin 2
Forward
|Internal
|An internal pin attached to the built-in HBridge chip.
Subject to pseudo-random signal state for the first 500ms after RoboPad boot.
|-
|Drive Pin 2
Backward
|Internal
|An internal pin attached to the built-in HBridge chip.
Subject to pseudo-random signal state for the first 500ms after RoboPad boot.
|}

== IO Units ==
A variety of IO Units can be added that are suitable for a number of uses, all are listed here.
=== Actuators ===
All actuators add input ports to the [[Chip Node]], allowing signals to be passed from the [[Nodegraph Editor|Node Graph]] to each actuator. On top of this, each actuator will create an output port on the Chip Node, usually labelled ending with ''"Armed"'' - this is an indicator of whether or not the actuator is '''armed'''. The signal to any specific actuator ''must'' pass through that actuator's configured '''safe value''' for it to be considered to be armed - then and only then will the actuator start to process new control signals. As an example, an servo attached using the "PWM Output" with a safety value set to 50% would require a near-50% signal to be sent to it's input before you will be able to see any change in the pin's output.

All actuators output '''3.3 volts''' along their output pins. Make sure that any connected peripherals such as ESCs or H-Bridges operate with 3.3 volt logic.
==== H-Bridge Motor ====
[[File:H-Bridge Motor IO Unit Screenshot 2023-2-20.png|right|frameless|410x410px]]A [[wikipedia:H-bridge|H-Bridge]] is a simple, common circuit that can control the polarity of electricity to an attached electrical component - commonly a motor. In practice this means that a typical brushed DC motor's direction and speed can be controlled from one using two control signals. While you can make one yourself [https://www.robotroom.com/BipolarHBridge.html using transistors] (that site also has a [https://www.robotroom.com/DPDT-Bidirectional-Motor-Switch.html useful example] using switches which might make the concept easier to understand too), they often come in integrated circuit (IC) form factors, such as the Texas Instruments ''L293D'', which packs two H-bridges and comes bundled with some additional features.

Using this IO Unit, the RoboPad will send drive signals suitable for use with a H-bridge through the specified pins (''PinA'' and ''PinB''). It's emergency stop state is to stop all signals and power down associated pins. The nodegraph is expected to supply a value between 0 and 1 to this IO Unit's input port, where 0 is maximum reverse rotation, 0.5 is stationary and 1 is maximum forward rotation.
* '''Name''': The name of this HBridge motor, basically only changes the name of the motor input port on the Chip Node.
* '''Pin A''': One of the two directional signals needed by H-Bridge chips.
* '''Pin B''': One of the two directional signals needed by H-Bridge chips, signalling the opposite direction from that signalled in ''Pin A.''
* '''Enable Pin''': If set to a value other than "Unset", a high signal will be transmitted whenever the H-Bridge is in use; to be connected to a H-Bridge chip's "enable" pin(s).
* '''Forward Scale''': Scales the forward signal (over 50%) before it is transmitted to the motor signal pins - if your motor drives forward faster than backwards, then you can lower this value.
* '''Reverse Scale''': Scales the backward signal (below 50%) before it is transmitted to the motor signal pins - if your motor drives backwards faster than forwards, then you can lower this value.

==== Built-in H-Bridge Motor ====
[[File:Built-in H-Bridge Motor 2023-02-20-b.png|right|frameless|410x410px|The Built-In H-Bridge Motor IO Unit UI]]The "Built-in H-Bridge Motor" IO unit is a specialised version of the "H-Bridge Motor" above, specifically designed to work only with the two built-in H-Bridges on the RoboPad, allowing you to select motors to be attached to the ''M1'' and ''M2'' pin pairs on the board. By default, two of these are configured, one for M1 and one for M2. When in the [[emergency stop state]], these IO Units attempt to send a stop signal to any attached motors, not powering any associated pins. Just as in the "H-Bridge Motor" IO Unit, the nodegraph is expected to supply a value between 0 and 1 to this IO Unit's input port, where 0 is maximum reverse rotation, 0.5 is stationary and 1 is maximum forward rotation.
* '''Name''': The name of this HBridge motor, basically only changes the name of the motor input port on the Chip Node.
* '''Built-in Motor''': Which of the two built-in motor pins this H-Bridge Motor IO Unit references - M1 connects to the M1 pins, M2 to the M2 pins.
* '''Forward Scale''': Scales the forward signal (over 50%) before it is transmitted to the motor signal pins - if your motor drives forward faster than backwards, then you can lower this value.
* '''Backward Scale''': Scales the backward signal (below 50%) before it is transmitted to the motor signal pins - if your motor drives backwards faster than forwards, then you can lower this value.
==== Unidirectional Brushless Motor ====
[[File:UniBrushless 2023-02-21.png|right|frameless|410x410px]]
A [[wikipedia:Brushless_DC_electric_motor|brushless motor]] is a type of motor that uses many (usually three) electromagnetic circuits, pulsed in a specific sequence to generate a moving magnetic field - this field then "pulls" the motor's magnetised rotor with it, allowing for rotation without direct electrical contact (as is found in brushed motors, where metal brushes must transfer power directly to the rotor), resulting in motors that are less prone to wear and generally operate more smoothly and efficiently. The downside of this is that they require [[wikipedia:Electronic_speed_control|electronic speed controllers (ESCs)]] to be driven, which are circuits containing microprocessors that power the motor's coils in the correct sequential pattern. These ESCs take in a control signal, and will often require an arming sequence before they start to energise the motor's coils.

The "Unidirectional Brushless Motor" IO Unit allows the RoboPad to send drive signals (much as a traditional RC radio receiver would) suitable for reception by an ESC that can accept a PWM control signal, and will automatically send the configured arming sequence beforehand in order to initialise the ESC ready for motor control. Note that this only configures one pin as a control signal pin, and as such is designed to work with ''unidirectional'' brushless motor ESCs, i.e. ESCs that allow a single motor to be driven in a single direction at varying speeds. An incoming nodegraph signal of 0 results in the minimum microseconds signal being sent to the ESC, while an incoming nodegraph signal of 1 results in the maximum microseconds signal being sent to the ESC.

* '''Name''': The name of this brushless motor, basically only changes the name of the motor input port on the Chip Node.
* '''Pin''': Which pin will generate the ESC control signal.
* '''Minimum Microseconds [''Advanced'']''': The minimum value the PWM control signal generated has (i.e. what it has when a 0/low signal is sent to the IO Unit via the nodegraph). '''Only change this if you know what you are doing!'''
* '''Maximum Microseconds [''Advanced'']''': The maximum value the PWM control signal generated has (i.e. what it has when a 1/high signal is sent to the IO Unit via the nodegraph). '''Only change this if you know what you are doing!'''
* '''Arm Sequence''': The sequence of signals that must be sent to the ESC to arm it. Refer to your ESC's manual to understand it's arming sequence and select the appropriate option here. If none match, [https://robopad.co.uk/contact.html drop us a line and tell us].

==== Servo Motor ====
[[File:Servo 2023-02-22.png|right|frameless|410x410px]]
A [[wikipedia:Servomotor|servo motor]] is a motor/control board combination integrated circuit that takes a control signal and actuates to a position within its range of movement that aligns with the received signal.

The "Servo Motor" IO Unit allows the RoboPad to send PWM drive signals that a servo motor can interpret. While the control signal provided by the RoboPad is at 3.3v and as such should work fine under most common servos, they will require their own power supply - some servos accept a range of input voltages and will be suitable to power directly from your robot's power source (such as a battery), but others will require power circuitry to ensure that you are providing them a safe and expected voltage. '''Always refer to your motor's manual and/or technical information and verify that it will work with the rest of your electrical circuit.'''

* '''Name''': The name of this servo motor, basically only changes the name of the motor input port on the Chip Node.
* '''Pin''': Which pin will generate the PWM control signal.
* '''Minimum Microseconds''': The minimum value the PWM control signal generated has (i.e. what it has when a 0/low signal is sent to the IO Unit via the nodegraph). '''Only change this if you know what you are doing!'''
* '''Maximum Microseconds''': The maximum value the PWM control signal generated has (i.e. what it has when a 1/high signal is sent to the IO Unit via the nodegraph). '''Only change this if you know what you are doing!'''
* '''Disconnect Behaviour''': What this IO Unit should do in the [[emergency stop state]]. By default this is "Stay in place" meaning that the control signal will remain at what it last sent - this makes sense for most servo-based actuators as in an emergency stop state, you would not want the servo moving. However, in some cases you may want the servo to move to a pre-defined position. In that case this can be set to "Return to disconnect %" which will set the servo control signal to ''Disconnect Percent'' (defined below) in the emergency stop state.
* '''Disconnect Percent''': The percent, relative from the ''minimum microseconds'' value (0%) to the ''maximum microseconds'' value (100%) to return to when entering the [[emergency stop state]] if ''Disconnect Behaviour'' is set to "Return to disconnect %".

==== Digital Output ====
[[File:Digital Output 2023-02-22.png|right|frameless|410x410px]]
The simplest IO Unit actuator, the "Digital Out" IO Unit sets a physical pin as a binary digital output, similar to those you might find on an [https://reference.arduino.cc/reference/en/language/functions/digital-io/digitalwrite/ arduino]. As a control signal comes into the IO Unit via the nodegraph, if the value is over 0.5 then a logical high (at 3.3 volts) is sent out of the selected pin, if the value is below 0.5 then a logical low (at 0 volts) is sent out of the selected pin.

* '''Name''': The name of this digital output, basically only changes the name of the input port on the Chip Node.
* '''Pin''': Which pin will generate the digital signal.
* '''Safety Value''': What value to output when in the [[emergency stop state]] if the ''Stop Behaviour'' is configured as "Return to safe".
* '''Stop Behaviour''': What this IO Unit should do when the RoboPad goes into the [[emergency stop state]]. By default "Return to safe", meaning that it will transmit the value set in ''Safety Value''.

==== PWM Output ====
[[File:PWM Output IO Unit.png|right|frameless|410x410px]]
The "PWM Output" IO Unit sets a physical pin as a PWM pseudo-analog output, similar to those you can configure on an [https://docs.arduino.cc/learn/microcontrollers/analog-output arduino]. As the signal (between 0 and 1) comes into the IO Unit via the nodegraph, the value is then ouput as a PWM signal from the RoboPad "between" 0 and 3.3 volts.

* '''Name''': The name of this PWM output, basically only changes the name of the input port on the Chip Node.
* '''Pin''': Which pin will generate the PWM control signal.
* '''Safety Value''': The percent, relative from the ''minimum microseconds'' value (0%) to the ''maximum microseconds'' value (100%) to return to when entering the [[emergency stop state]] if ''Stop Behaviour'' is set to "Return to safe".
* '''Stop Behaviour''': What value to output when in the [[emergency stop state]] if the ''Stop Behaviour'' is configured as "Return to safe".

Beta

2022-12-09T20:44:16Z

WikiSysop: Updated link to firmware page

Welcome to the beta page. This page will explain some of the key changes currently being trialled in the RoboPad Beta, available at https://robopad.co.uk/firmware. Any pages on this wiki that are marked with a red "beta" box at the top of the page indicate that the page discusses a function only present in the RoboPad beta firmware.

It is suggested that you do not use the beta firmware if you have no use for the features it adds, as it is not as rigorously tested as the release firmware and may cause the RoboPad to act in an unexpected (and potentially unsafe) way, or may damage stored nodegraph and configuration files. You should always exercise caution when using a RoboPad device, however, extra caution should be used when using one running beta firmware.

==== Features Under Test ====

* Input/Output (IO) Configuration
** The RoboPad now has a new page, the '''IO Configuration''' page, accessible at 192.168.4.1/ioConfig, or via the button under the '''IO Management''' section of the '''Management''' page.
** This page allows you to add new external actuators by selecting them from the "Add" menu and configuring the output pins that it uses, as they correspond to the physically lablled pins on the RoboPad.
** Further information will be vailable at the IO Configuration page.

==== Warnings ====
At the moment the RoboPad does not check that pins have been over-mapped. Take extra care to make sure that you have not selected the same pin more than once over any of the added IO units.

Pins used under the "Advanced" option can act unpredictably for the first 100ms after RoboPad turn-on - please refrain from using any of these pins to move any kind of actuator that can cause physical harm, stick to LEDs and the like.

Main Page

2022-04-13T18:59:47Z

WikiSysop:

Welcome to the RoboPad Wiki!

Here you will find the most complete repository of information relating to the [https://www.robopad.co.uk RoboPad] robot remote control system produced by Blayze Tech Ltd.

This wiki (as well as the RoboPad product) is currently in it's early stages, so details and feature examples might be light on the ground. Make sure you check back every so often to see how the wiki grows!

For now, you may be interested in the links below, particularly if you are a new RoboPad user.

== Getting started ==
* [https://guide.robopad.co.uk User Manual]
* [https://wiki.robopad.co.uk/index.php/Quickstart Quickstart Guide]
* [https://wiki.robopad.co.uk/index.php/Nodegraph_Editor Nodegraph Information]
* [https://wiki.robopad.co.uk/index.php/Firmware_Releases Latest Firmware]
* [https://wiki.robopad.co.uk/index.php/Forgotten_Password Help! I've Forgotten My Password!]

RoboPad Wiki:Privacy policy

2022-04-13T18:58:48Z

WikiSysop:

Blayze Tech Limited takes your privacy very seriously and will never disclose, share or sell your data without your consent; unless required to do so by law. We only retain your data for as long as is necessary and for the purpose(s) specified in this policy. Where you have consented to us providing you with promotional offers and marketing, you are free to withdraw this consent at any time.

You can view our Privacy Policy on our website https://blayzetech.com/privacy

Key Contacts

Our Data Protection Officer is responsible for helping ensure we treat your personal data appropriately. They can be contacted through the following means:

Email:

dpo@blayze.tech

Post: 

Data Protection Officer,
Blayze Tech Limited,
Initial Business Centre,
Wilson Business Park,
Monsall Road,
Manchester,
M40 8WN.
England

Complaints

If you feel you need to make a complaint about how we are processing your personal data, you can contact the Information Commissioner’s Office as the relevant supervisory authority.

Website - https://ico.org.uk/concerns/handling/

Helpline - 0303 123 1113

Email - casework@ico.org.uk

Post - Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF

Blayze Tech Limited is registered in England and Wales with Company Number 12551617
Registered office: Initial Business Centre, Wilson Business Park, Monsall Road, Manchester, England, M40 8WN

RoboPad Wiki:Privacy policy

2022-04-13T18:58:35Z

WikiSysop:

Blayze Tech Limited takes your privacy very seriously and will never disclose, share or sell your data without your consent; unless required to do so by law. We only retain your data for as long as is necessary and for the purpose(s) specified in this policy. Where you have consented to us providing you with promotional offers and marketing, you are free to withdraw this consent at any time.

You can view our Privacy Policy on our website https://blayzetech.com/privacy

Key Contacts

Our Data Protection Officer is responsible for helping ensure we treat your personal data appropriately. They can be contacted through the following means:

Email:

dpo@blayze.tech

Post: 

Data Protection Officer

Blayze Tech Limited,
Initial Business Centre,
Wilson Business Park,
Monsall Road,
Manchester,
M40 8WN.
England

Complaints

If you feel you need to make a complaint about how we are processing your personal data, you can contact the Information Commissioner’s Office as the relevant supervisory authority.

Website - https://ico.org.uk/concerns/handling/

Helpline - 0303 123 1113

Email - casework@ico.org.uk

Post - Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF

Blayze Tech Limited is registered in England and Wales with Company Number 12551617
Registered office: Initial Business Centre, Wilson Business Park, Monsall Road, Manchester, England, M40 8WN

RoboPad Wiki:Privacy policy

2022-04-13T18:58:09Z

WikiSysop:

Blayze Tech Limited takes your privacy very seriously and will never disclose, share or sell your data without your consent; unless required to do so by law. We only retain your data for as long as is necessary and for the purpose(s) specified in this policy. Where you have consented to us providing you with promotional offers and marketing, you are free to withdraw this consent at any time.

You can view our Privacy Policy on our website https://blayzetech.com/privacy

Key Contacts

Our Data Protection Officer is responsible for helping ensure we treat your personal data appropriately. They can be contacted through the following means:

Email:

dpo@blayze.tech

Post: 

Data Protection Officer

Blayze Tech Limited
Initial Business Centre
Wilson Business Park
Monsall Road
Manchester
M40 8WN

Complaints

If you feel you need to make a complaint about how we are processing your personal data, you can contact the Information Commissioner’s Office as the relevant supervisory authority.

Website - https://ico.org.uk/concerns/handling/

Helpline - 0303 123 1113

Email - casework@ico.org.uk

Post - Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF

Blayze Tech Limited is registered in England and Wales with Company Number 12551617
Registered office: Initial Business Centre, Wilson Business Park, Monsall Road, Manchester, England, M40 8WN

RoboPad Wiki:Privacy policy

2022-04-13T18:57:10Z

WikiSysop:

Blayze Tech Limited takes your privacy very seriously and will never disclose, share or sell your data without your consent; unless required to do so by law. We only retain your data for as long as is necessary and for the purpose(s) specified in this policy. Where you have consented to us providing you with promotional offers and marketing, you are free to withdraw this consent at any time.

You can view our Privacy Policy on our website https://blayzetech.com/privacy

Key Contacts

Our Data Protection Officer is responsible for helping ensure we treat your personal data appropriately. They can be contacted through the following means:

Email:

dpo@blayze.tech

Post: 

Data Protection Officer
Blayze Tech Limited
Initial Business Centre
Wilson Business Park
Monsall Road
Manchester
M40 8WN

Complaints

If you feel you need to make a complaint about how we are processing your personal data, you can contact the Information Commissioner’s Office as the relevant supervisory authority.
Website - https://ico.org.uk/concerns/handling/
Helpline - 0303 123 1113
Email - casework@ico.org.uk
Post - Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF

Blayze Tech Limited is registered in England and Wales with Company Number 12551617
Registered office: Initial Business Centre, Wilson Business Park, Monsall Road, Manchester, England, M40 8WN

RoboPad Wiki:Privacy policy

2022-04-13T18:55:50Z

WikiSysop:

Blayze Tech Limited takes your privacy very seriously and will never disclose, share or sell your data without your consent; unless required to do so by law. We only retain your data for as long as is necessary and for the purpose(s) specified in this policy. Where you have consented to us providing you with promotional offers and marketing, you are free to withdraw this consent at any time.

You can view our Privacy Policy on website https://blayzetech.com/privacy

Key Contacts

Our Data Protection Officer is responsible for helping ensure we treat your personal data appropriately. They can be contacted through the following means:

Email:

dpo@blayze.tech

Post: 

Data Protection Officer
Blayze Tech Limited
Initial Business Centre
Wilson Business Park
Monsall Road
Manchester
M40 8WN

Complaints

If you feel you need to make a complaint about how we are processing your personal data, you can contact the Information Commissioner’s Office as the relevant supervisory authority.
Website - https://ico.org.uk/concerns/handling/
Helpline - 0303 123 1113
Email - casework@ico.org.uk
Post - Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF

Blayze Tech Limited is registered in England and Wales with Company Number 12551617
Registered office: Initial Business Centre, Wilson Business Park, Monsall Road, Manchester, England, M40 8WN

RoboPad Wiki:Privacy policy

2022-04-13T18:50:41Z

WikiSysop: Created blank page

MediaWiki:Common.css

2022-04-13T18:31:35Z

WikiSysop:

/* CSS placed here will be applied to all skins */

MediaWiki:Common.css

2022-04-13T18:31:03Z

WikiSysop:

/* CSS placed here will be applied to all skins */
1. ca-talk { display:none!important; }

MediaWiki:Common.css

2022-04-13T18:30:10Z

WikiSysop: Created page with "/* CSS placed here will be applied to all skins */ ca-talk { display:none!important; }"

/* CSS placed here will be applied to all skins */
ca-talk { display:none!important; }

Main Page

2022-04-13T17:58:31Z

WikiSysop:

Welcome to the RoboPad Wiki!

Here you will find the most complete repository of information relating to the [https://www.robopad.co.uk RoboPad] robot remote control system produced by Blayze Tech Ltd.

This wiki (as well as the RoboPad product) is currently in it's early stages, so details and feature examples might be light on the ground. Make sure you check back every so often to see how the wiki grows!

For now, you may be interested in the links below, particularly if you are a new RoboPad user:..2212123456

== Getting started ==
* [https://guide.robopad.co.uk User Manual]
* [https://wiki.robopad.co.uk/index.php/Quickstart Quickstart Guide]
* [https://wiki.robopad.co.uk/index.php/Nodegraph_Editor Nodegraph Information]
* [https://wiki.robopad.co.uk/index.php/Firmware_Releases Latest Firmware]
* [https://wiki.robopad.co.uk/index.php/Forgotten_Password Help! I've Forgotten My Password!]

Main Page

2022-02-22T14:18:21Z

WikiSysop: Adds first draft of main page.

Main Page

2022-02-22T14:15:56Z

WikiSysop: test change

MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.fxghfx

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]