Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!
The Surface Pro 3’s Type Cover hits the mark for most uses but the lack of native multimedia keys (Next Track, Previous Track) is a sore point that needed addressing. Read on.
Since we can’t bind key combinations in Windows 8 we’ll use the excellent/free AutoHotkey to bind our multimedia key combinations (e.g. CTRL+RIGHT fires the Next Track action).
- Download and install AutoHotkey from their home page
- Open AutoHotkey
- On the first start it will prompt you to generate a first sample AutoHotkey script
- Copy and paste the following script into the sample script
^Right:: ;the ^ means CTRL
- Save the AutoHotkey script file
- Close and re-open AutoHotkey to enable the new multimedia key combinations
I bit the bullet and purchased the 600-class Quick Release Universal Retractable Gear Set to upgrade from the Crab Leg Landing Gear Set on my Predator 650 build.
Upgrading to a servo-driven landing leg set means the legs can be toggled to raise/lower from a spare channel on the receiver, I envision using this for aerial photography where footage is currently obstructed by the crab legs.
I chose the 600-class retractable gear set as I wanted only a single channel sacrificed on the receiver and didn’t want to run two 450-class sets – which is designed for smaller frames – in parallel.
To mount the retractable gear set to the frame I purchased 4 x Shock absorbing CNC aluminum tube clamp (10mm) which will fit the 10mm rails on the underbelly of the Predator 650 frame. A perk of this particular landing gear set is below the servo bar is ideal space to mount a camera gimbal, this be be done without modification.
I’ll update this post when the item arrives 🙂
[5 days later…]
Retractable landing legs arrived and they’re big! I’m thinking the 450-class set would have been fine, but I have not installed them yet so am still confident I made the right choice. Also the 4 additional tube clamps were unnecessary as the frame includes its own set.
The bulkhead that houses the servo’s has holes punched into it to suit a larger frame, they’re too far apart to be usable with the Predator 650 so I’ve drilled my own holes in line with the underbelly rails of the 650-frame.
Additionally since there’s so much space on either side of the bulkhead I’ll move my battery from the underbelly of the frame – was strapped behind the 4-in-1 ESC and FPV camera – up onto the bar and install a 2nd 4500mAh 4S battery to balance the weight out.
Before I shelled out for the dedicated Aircraft Navigation Lamp Set (install guide here) from HobbyKing I wanted to add some basic LED lighting to the motor arms of my X525 build, I still use these LED’s as one displays the Motor Arm status, the other the GPS Lock, that and the dedicated navigation lights don’t talk to Arducopter.
Update: The voltage of the LED strip has to be 5V. Too low, your strip will burn. Too high and it might not turn on (thanks Wei).
Here’s what you need and how to install it.
What you need
- 1 x red LED strip for the front-left arm
- 1 x green LED strip for the front-right arm
- 2 x white LED strip for the rear arms
- 1 x LED strip in your preferred colour for GPS Lock (I went for blue, but you could also use yellow)
- 1 x LED strip in your preferred colour for Motor Arm (I went for red, ala The Danger Zone)
Connecting the LED’s to the APM board
If you went out and bought the 3 LED strip’s mentioned above you can connect the LED servo cable’s directly to the APM board’s analog input’s after a quick change of one of the leads to the JR connector.
We can connect these particular LED strip’s directly to the APM board as the LED’s draw less than the maximum permissible current of the AVR chip on the APM of 40mA per input, the LED strips we’re looking at draw 33mA per input.
Update: The current limit is 40mA per pin or 200mA total. Any higher and you risk damage to the APM (thanks Wei).
By moving the positive lead (red cable) over one spot to occupy the signal line APM can power the LED lights on/off when it chooses, left unchanged the LED strip will be connected to the +5V rail and be always on; which looks cool but is useless.
- Using a small sharp knife lift up the tab on the positive lead (aka red cable) of the JR connector that holds the pin in place
- Pull on the positive lead while the tab is lifted to remove it from the JR connector
- Re-insert the positive lead into the space typically used for the signal line (the next available space) of the JR connector
- Make sure the tab is down and the positive lead is secured by giving it a pull
If you’re using the current release of APM then you’re on AC 3.1.5 (Arducopter 3.1.5) and the following will apply, read further for the AC 3.2 changes which will apply when AC 3.2 is officially released.
AC 3.1.5 (today)
- A4: AUX led
- A6: GPS – will flash with no GPS lock, solid with GPS lock
- A7 through A11: Motor LED’s (always on)
AC 3.2 (future)
- A4 : Motor LED
- A6 : GPS – will flash with no GPS lock, solid with GPS lock
- A7: Arming LED
- A8 through A11: Motor LED’s (always on)
Note: Need to confirm A8 through A11 for AC 3.2 and above as this is not currently documented on External LEDs from Arducopter Wiki.
Connect your LiPo battery and power up your APM board, lights on, enjoy night flying! When you’re ready consider upgrading to the Aircraft Navigation Lamp Set (install guide here) mentioned earlier as you can then add real-world lighting sequences to your build.
I got around to connecting the Hobbyking Aircraft Navigation Lamp Set to my APM 1.6 clone board today, here’s a run through of the wiring guide for connecting each LED to the distribution box as well as placement for an X-frame quadcopter. There’s also a guide for controlling the lighting modes with the Turnigy 9XR transmitter and a dummy list of available lighting modes.
Included with the Aircraft Navigation Lamp Set is the following:
- 5 x white LED’s with 2-pin micro moxel connectors
- 2 x red LED’s with 2-pin micro moxel connectors
- 1 x green LED with 2-pin micro moxel connector
- 8 x plastic LED grips for mounting the LED to frames
- 1 x distribution Unit with micro molex connectors for the LED’s
- 1 x servo cable with 3-pin micro molex connector for powering and controlling the LED’s
The total draw of the LED lights and distribution unit is less than 100 mAh and is self-powered from the receiver channel it is controlled from.
Available lighting modes
You can choose from the following lighting modes:
- Coloured arms always on, strobes and beacon flashing, landing lights fade in/out
- Coloured arms, strobes and beacon flashing, landing lights fade in/out
- Coloured arms flash twice on each arm
- Coloured arms flash twice on each arm at higher frequency
- Coloured arms and strobes always on, beacon light is flashing, landing lights fade in/out
- All lights flashing at high frequency
- All lights flashing at slow frequency
- All lights on
- All lights off
Guide to connecting LED’s to assigned connectors
- Strobe light on front-right arm
- Landing light on rear-right arm
- Beacon light on front of main frame
- Strobe light on front-left arm
- Red light on front-left arm
- Landing light on rear-left arm
- Beacon light on rear of main frame
- Green light on front-right arm
Controlling the lighting modes with the Turnigy 9XR transmitter
Ensure you’ve connected the supplied servo cable from the AUX connector on the distribution unit to an available channel on your receiver (I chose channel 8) before proceeding.
- Power on the Turnigy 9XR
- Hold the Menu button for a second to open the Menu screen
- Switch to the Mixer screen on tab 5/11 by pressing the right arrow button
- Using the down button only highlight ‘100%’ on the available channel on your receiver that you connected the distribution unit to (I chose channel 8 so went down to CH8)
- Hold down the Menu button to display the Edit Mix screen for this channel
- Ensure the Source is set to FULL
- Press the down button only to highlight the Switch option
- Using the left and right buttons only change the value to TRN
- Press the Exit button only to return to the previous screen
- Press the Exit button repeatedly until you are on the initial status screen
You’re done! Connect the LiPo battery to your quadcopter and flick the TRN switch on the far-right of the Turnigy 9XR controller to switch through the lighting modes.
Notice: This parts list is ongoing, if you know the dimensions of a missing part or think this can be better drop a comment below 🙂
- 44 x M2 x 6mm
- 46 x M3 x 6mm (button heads)
- 40 x M3 x 6mm (flat heads)
- 12 x M3 x 10mm
- 2 x […]
- 2 x […]
- # x M2.5 x 22mm
- 1 x 23*25*248mm carbon tube
- 6 x 25mm aluminium blocks
- 6 x M2.5 x 40mm
- 6 x M2.5 nuts
Hook and Rod
- 2 x 10mm tubes for undercarriage (rail mounting system for battery, gimbal, etc.)
- 4 x […]
- Build the motor arms first and mount them to the rear section prior to attaching the rear landing legs to the frame.
- Do not lose a single screw. A single screw. There are no spares available from the supplier at this time.
- ArduPilot Mega 2.6
- uBlox LEA-6H GPS with Compass
- GPS Mast for uBlox LEA-6H
- Power Module for ArduPilot (4S)
- Turnigy Multistar 2814-800Kv 123 (HobbyKing didn’t stock the 2814-800Kv so I pulled the trigger on the smaller 2214-800Kv, not ideal as the motor mounts don’t all line up but close enough, in hindsight should have waited for the 2814-800Kv)
- NTM 28 Carbon Fibre Motor Mount (as above, used the cross mount from this kit to mount the Turnigy motors with holes 16mm & 19mm to the Predator 650 motors mounts with holes 19mm & 25mm, no motor mount screws are provided so used screws scavenged from previous builds to mount the the cross mount to the motor mounts, if you get the 2814-800Kv motors mentioned above you mount directly onto the motor mounts)
- 12 x 4.5 Slow Fly Nylon Propellers (Scavenged from retired X525 build)
- Turnigy 9XR Transmitter Mode 1 (No Module) (Scavenged from retired X525 build)
- FrSky DF 2.4Ghz Combo Pack for JR w/ Module & RX (Scavenged from retired X525 build)
- 3DR Radio Set (433mhz for Europe) (Scavenged from retired X525 build)
- Fatshark 600TVL High Resolution FPV Tuned CMOS Camera
- BOSCAM 5.8Ghz 8-channel 200Mw video transmitter
- BOSCAM 5.8Ghz 8-channel FPV goggles (superseded by Skyzone 5.8GHz FPV Goggles)
- Signal loss Alarm & Lost Plane Finder
- On-Board Lipoly Low Voltage Alarm 2s~3s
- Wire Mesh Guard Black 10mm (use the mesh to protect the motor leads when exposed at the end of each motor mount)
- 3.5mm Male/Female Bullet Brushless Motor Extension Lead 200mm
For the past several months I have been receiving regular e-mail notifications from my DS213+ that a system update is ready to be applied, I’d proceed to open Control Panel > Update & Restore with an Administrator level User account and hit Update. Nothing would happen…
Here’s the fix straight from Synology Support which is not mentioned on any well ranked forums or posts when searching for this error. I’ve pasted the original from Synology Support as well as an English-friendly version.
If you have updated your NAS to DSM 5.0 and above there is no security/malware concern to be worried about. If you are receiving e-mail notifications that a new system update is available but it does not appear on the Update & Restore screen please do the following:
- Open Control Panel > Network as an Administrator level User account
- Under the DNS options on this screen set the following primary and secondary DNS entriesPrimary: 18.104.22.168
- Click Save Changes
- Open Control > Update & Restore and click Update Now
Original response from Synology Support:
If you have managed to update system to DSM 5.0 there has security concern that needs to be worried. On the other hand regarding e-mail you received has a new software for update but no update was available on system, please apply Google DNS 22.214.171.124 or 126.96.36.199. for your DiskStation under Control Panel > Network > General (Preferred DNS Server) for changes to take effect. Then, check if the issue resolves then. – Technical Support, Synology
Update: This post seems relevant for DSM 5.1 users too…
I’ve been helping out store owners in maintaining their stores for a little while now and the trend for Plugin and Theme developers to introduce persistent WordPress Administration notices for non-critical site activities or inappropriate site wide notices is becoming too common. I want to bring this to the attention of other WordPress users so that this can be addressed.
A ‘good’ developer will limit persistent notices to critical site activities only (e.g. caching Plugins, major database updates).
In the above case WooThemes Subscription and Envato’s Theme notices are considered critical; subscription sales won’t work and the Theme will be missing core functionality without addressing those notices.
Configuring default options for a CSV exporter or installing a Plugin update helper isn’t a critical activity.
A ‘great’ developer will still add the ability to dismiss these notices even in the case of a critical site activity.
Envato’s Theme and SkyVerge have added a dismiss option with their exporter setup notice but in SkyVerge’s case the notice does not need to be on all screens or considered an error. Dropping the error CSS class and limiting this setup notice to just the Plugins, Dashboard > Updates and own CSV Export screens would be better.
WooThemes don’t offer a dismiss option at all which makes for unnecessary nagging and screen clutter and goes against the WordPress Plugin Guidelines.
It’s fine to put an error message at the top of the admin for special cases, but it should be linked to a way to fix the error and it should be infrequent. Any form of “nagging” is absolutely prohibited.
That’s my rant. I’ll add an option to the next release of Store Toolkit for WooCommerce to hide that persistent notice so this post isn’t all for a lost cause.
Error 500 – Server error!
Fun times with Apache… Recent releases of XAMPP for Windows hide additional Apache overrides outside of the reach of …/apache/conf/httpd.conf. If you’re like me and exhausted all prior Google results to get Permalinks working with XAMPP give this one a go.
- Open …/apache/conf/extra/httpd-xampp.conf
- Replace all instances of AllowOverride None and AllowOverride AuthConfig with AllowOverride All
- Save changes
- Open XAMPP Control Panel and restart the Apache service or open the Windows Services dialog and restart the Apache2.4 Service
- Breathe and give that Error 500 tab a refresh
Woop! In case this doesn’t work it’s likely you’ve missed one of the basics:
- Open …/apache/httpd.conf
- Uncomment #LoadModule rewrite_module modules/mod_rewrite.so
- Replace all instances of AllowOverride None and AllowOverride AuthConfig with AllowOverride All
- Save changes
- As above, restart the Apache Service.