#VL53L0X

[cyrusmehdipour]

Controlling Plastic Injection Machine Nozzle Movement with a Digital Las...

[makerportal]

•VL53L0X• . . . This tiny sensor located at the center of the board is an infrared time-of-flight sensor. It uses a 940nm laser to determine the range of an object based on the light reflected back to the sensor. This module can measure from about 50mm - 2200mm, at rates of up to ~20Hz. . . . #arduino #engineering #arduinouno #arduinoproject #tof #engineer #breadboard #microcontroller #maker #laser #electronics #educate #teacher #diy #apple #android #stem #makerspace #vl53l0x #science #design #researcher #innovate #company #timeofflight #application #physics #robot #diyelectronics #makerportal (at New York, New York) https://www.instagram.com/p/B_ciRJ6DjzU/?igshid=praajuvpqcd4

[draegerit]

Laser Distanz Sensor VL53LXX-V2 #vl53l0x #vl53lxx #sensor #distance #arduino #arduinoproject #arduinouno #techy #tech #maker #electronic #components #diy #DraegerIT (hier: Stefan Draeger Software) https://www.instagram.com/p/B7vmBMUIiDG/?igshid=1bvrw8hv4x0li

[planetarduino]

The Baldcorder is James Lewis’ tricorder-like device for measuring light levels and temperature

As part of element14’s Build Inside the Box Challenge, James Lewis (AKA Bald Engineer) decided to make his own DIY tricoder from Star Trek. In the series, a tricoder is a ubiquitous scanning tool that can perform various scans of the environment through its onboard sensors, as well as record and analyze them later — all in a handheld format. Lewis’ design incorporates a MKR Zero as the microcontroller, a phototransistor to detect light levels, and an analog temperature sensor to sense ambient temperatures. 

The enclosure itself was based on a tricorder toy and recreated in Fusion 360. It features a hinge mechanism for easy opening and closing, as well as handling the wiring harness that connects both halves of the device. Once it was 3D-printed, Lewis moved onto the electronics.

A VL53L0X time of flight sensor was used to detect if the hinge was open, and thus if the OLED information screens should be turned on. Lewis utilized the SAM D21’s onboard capacitive touch controller to add four buttons onto his device for simple inputs. Finally, the DIY tricorder can play looped WAV files via its onboard SD card and DAC, along with an external op-amp and speaker circuit. 

To read more about how the Bald Engineer created this fun project and view its associated schematics, code, and design files, be sure to check out its write-up here on element14’s website. You can also see the build log and demonstration below! 

The post The Baldcorder is James Lewis’ tricorder-like device for measuring light levels and temperature appeared first on Arduino Blog.

The Baldcorder is James Lewis’ tricorder-like device for measuring light levels and temperature was originally published on PlanetArduino

[kjunichi]

Raspberry Pi Zero で自律飛行ドローンを作るぞ（第１回：浮上まで） - Qiita [はてなブックマーク]

Raspberry Pi Zero で自律飛行ドローンを作るぞ（第１回：浮上まで） - Qiita

概要 Raspberry Pi で３つのi2cデバイスを同時に動かしてみた　で使った １．距離センサ(VL53L0X) ２．ジャイロ加速度センサ(MPU-6050) ３．PWMドライバ(PCA9685) を Raspberry Pi Zero で制御して自律飛行ドローン(クワッドコプター)を作ってみようと思いました。 これだけでは自律は難しいですが、改善しながらコツコ...

from kjw_junichiのはてなブックマーク http://bit.ly/2vCcX9z

[ericvanderburg]

Driver for VL53L0X Time-Of-Flight (ToF) Sensor and NXP K20DX128

http://i.securitythinkingcap.com/QwcZKm

[theodorasresearchjournal-blog]

Final Circuit, Schematics + Code

This is sort of a two-part schematic; the first image indicates the connections made to the Arduino itself, outside of the pins used by the shield. The second schematic shows the shield and the respective parts being driven by it. This is due to the nearly non-existent documentation for the Escudo in terms of parts file that could be added to Fritzing. The official schematic offered by Sparkfun seems to detail the individual parts of the board rather than the shield itself as a standalone object (it can be accessed via the link here: https://cdn.sparkfun.com/datasheets/Components/EL/EL_Escudo_Dos/EL%20Escudo%20Dos%20v21.pdf). In light of not being able to implement the actual part, I edited the one photo they offer as guidance for hooking up the shield to fit my own circuit:

I also could not manage to find parts for the screw terminal to DC power adapter and DC power supply anywhere. Essentially, the Neopixels are powered exactly as recommended in the Adafruit official guide, using the same parts:

Circuit overview: 

The gesture and distance sensors are connected to the Arduino via SCL and SDA; this was an ideal setup as the El Escudo shield needs to make use of all the digital pins on the Arduino. They are externally powered with 5V via a 4xAA battery pack. The Neopixel strip is driven from pin A3 and connected to an external 5V supply. The shield itself drives 6 strands of El Wire and makes use of a 12V inverter 

PARTS: 6 x El Wire strands, 12V inverter, El Escudo Dos Shield, Side Light Neopixel Strip, DC Power Supply, Screw Terminal to DC adapter, 1000uF Capacitor, 470ohm resistor, Adafruit VL53L0X time of flight distance sensor, Adafruit APDS9960 gesture, proximity and RGB sensor, 12V power supply. 

Code overview:

The code makes use of switch cases - each case is a different animation effect or a different level of how lit the painting might be (dependent on the sensor, the values either trigger the painting to gradually light up or trigger more complex, dynamic visuals). The values received by the distance sensor make the wire strands light up one by one according to how close the distance recorded is to it through the use of if statements. The code also links the animation sequences to the gesture values recorded by the gesture sensor (up, down , left and right each trigger their own light effect).

[cyrusmehdipour]

DIY Digital Laser Ruler Tutorial with VL53L0X GY-53, SSD1306, and Wemos ...

[draegerit]

Arduino Lektion #103: Laser Distanz Sensor VL53LXX-V2

In diesem Beitrag möchte ich den Laser Distanz Sensor VL53LXX-V2 vorstellen. Dieser Sensor kann eine Distanz von bis zu 4m messen und arbeitet dabei mit einer Abtastgeschwindigkeit von 50Hz.

Laser Distanz Sensor - VL53LXX-V2

Bezug

Den Laser Distanz Sensor kann man über ebay.de für ca. 8€ inkl. Versandkosten beziehen oder deutlich günstiger über aliexpress.com (4,19$ inkl. Versandkosten). Ich habe den Sensor über aliexpress.com bestellt und habe ca. 5 Wochen auf diesen Sensor warten dürfen. Dafür aber weniger als die hälfte bezahlt. Lieferumfang Der Sensor wird in einer kleinen Antistatik Tüte geliefert und enthält neben dem Sensor noch eine Stiftleiste.

Lieferumfang - Laser Distanz Sensor VL53LXX-V2

Technische Daten des VL53LXX-V2

Betriebsspannung 3.3V bis 5.5V Messbereich Minimal 40mm Maximal 4m Messbereichsgenauigkeit ±5% Wellenlänge des Lasers 940nm Betriebsstemperatur -20°C bis 80°C Abmessungen ohne Löcher 15mm x 10mm mit Löcher 25mm x 10mm Druchmesser der Löcher 3mm

Aufbau & Schaltung

Bevor der Sensor verwendet werden kann muss dieser mit der Stiftleiste verbunden werden. Um die Stiftleiste korrekt (also im 90° Winkel) an den Sensor zu löten habe ich zusätzlich ein 170 Pin Breadboard und die überzähligen Stifte verwendet.

anlöten der Stiftleiste an den Laser Distanz Sensor Aufbau Der Sensor verfügt über 6 Pins welche wie folgt an den Arduino UNO angeschlossen werden. VL53LXX-V2 Arduino UNO VIN 5V GND GND SCL analoger Pin A5 SDA analoger Pin A4 GPIO01   XSHUT   Die Pins GPIO01 & XSHUT werden in meinen Beispielen zunächst nicht verwendet. Schaltung

Aufbau der Schaltung - Laser Distanz Sensor am Arduino UNO

Quellcode

Bibliothek Bibliotheken erleichtern einem Programmierer die arbeiten enorm, besonders wenn man wie wir mit Hardware arbeitet und so die einzelnen Adressen und Speicherbereiche be-/verarbeiten muss. Daher gibt es auch für diesen Sensor eine Bibliothek welche wir uns in die Entwicklungsumgebung (in meinem Fall wie immer die Arduino IDE) einbinden. Den Bibliotheksverwalter erreicht man über das Hauptmenü "Sketch" > "Bibliothek einbinden" > "Bibliotheken verwalten...". In diesem Dialog wird zunächst nach der Bibiothek mit dem Suchbegriff "vl53l" (1) gesucht. Ich verwende die Bibliothek von Sparkfun und wähle den zweiten Eintrag aus den Suchergebnissen (2) nach dem betätigen der Schaltfläche "Installieren" kann (nach Abschluss) der Dialog geschlossen werden (3).

Installieren der Bibliothek für das verwenden des Laser Distanz Sensors Beispiel - Ausgabe der Daten auf dem seriellen Monitor Der Bibliothek liegt ein Beispiel bei wie man diesen Sensor in der Arduino IDE programmiert. Das werde ich hier nutzen und etwas umschreiben und kommentieren. #include "Adafruit_VL53L0X.h" Adafruit_VL53L0X lox = Adafruit_VL53L0X(); //Um die Debug Ausgaben zu aktivieren //muss dieser Wert auf "true" gesetzt werden. #define debugSensor false //Es werden 10 Messungen durchgeführt. const int MAX_DATA = 10; //der Index der aktuellen Messung int readDataIndex = -1; //das Array für die Daten int data = {}; //zählen der fehlerhaften Messungen int failureMeasures = 0; void setup() { //begin der seriellen Kommunikation mit 115200 baud Serial.begin(115200); //Warten auf den Seriellen Port while (! Serial) { delay(1); } //Wenn der Serielle Port bereit ist dann eine Ausgabe auf diesen tätigen //und prüfen ob der Sensor korrekt angeschlossen ist (ob dieser Ansprechbar ist) Serial.println("GY-VL53L0X test"); if (!lox.begin()) { Serial.println("Fehler beim lesen des Sensors!"); while(1); //eine Endlos Schleife } } void loop() { //instanziieren des Sensors zum empfangen von Daten VL53L0X_RangingMeasurementData_t measure; lox.rangingTest(&measure, debugSensor); //lesen des Sensor Status //der Sensor kann verschiedene Status annehmen, //jedoch interessiert für uns nur der Wert "4" int sensorStatus = measure.RangeStatus; //Wenn Daten empfangen wurden dann... if (sensorStatus != VL53L0X_DEVICEERROR_MSRCNOTARGET) { //den Zähler für das Array um eins erhöhen readDataIndex++; //zuweisen des Wertes in das Array data = measure.RangeMilliMeter; //Wenn das Array "fertig" befüllt ist, dann... if(readDataIndex == MAX_DATA){ //eine Variable für die Berechnung des Durchschnittswertes int averageData = 0; //über das Array itereieren und die Daten zusammenzählen for(int i=0;i MAX_DATA){ Serial.println(""); } //eine Pause von 5ms einlegen delay(5); } Video

Vergleich mit einem Ultraschallsensor HC-SR04

Den Ultraschallsensor HC-SR04 habe ich bereits im Beitrag Arduino Lektion 9: Ultraschall Modul HC-SR04 vorgestellt. Da beide Sensoren (GY-VL53L0XV2 & HC-SR04) den Abstand von Objekten messen können, möchte ich kurz beide Sensoren testen. Man kann sehr gut erkennen das der Ultraschallsensor den Abstand nicht so genau misst wie der Laser Distanzsensor.

Fazit

Der Laser Distanzsensor GY-VL53L0XV2 ist günstig in der Anschaffung und durch das einfache einbinden einer Bibliothek auch genauso einfach zu programmieren. Jedoch ist dieser nicht ganz so genau und hatte in meinem Test eine Abweichung von bis zu mehreren Zentimeter.   Read the full article

[planetarduino]

This MKR Zero system gives early warning of potential sump pump problems

As most homeowners with a basement will tell you, keeping track of the sump pump is an important part of maintenance, as neglecting it can lead to the basement turning into a swimming pool. This is the exact predicament that a recent element14 Build Inside the Box winner, Mike Moore, ran into with his house because freezing pipes and an unreliable pump often became problematic. He went with multiple approaches to solve this, including water level detection, temperature monitoring, and even checking if the pump has ceased working. 

The first component used was a TCST1103 photo interrupter, and its job is to send a signal if a bobbing piece of plastic gets between its emitter and receiver, which would indicate the water level has risen too high. For more granular and continuous measurements, Moore also implemented a VL53L0X time-of-flight sensor that sends a laser beam towards the water and waits for a reflection. Because water can distort this reading, a couple of readings get taken and then averaged together. Temperatures are read by a simple MCP9701 IC that was placed inside of a plastic tube and stuck to the side of the pit. Finally, detecting if the pump is running is handled by an MCP604 IC. 

All these sensors are controlled with an Arduino MKR Zero that can sound an alarm if something’s wrong, and power is provided via a portable high-capacity battery bank. In the future, Moore plans to add SD card logging so he can view long-term trends in the data readings.

To see more about his project, you can view the element14 Presents video below and check out Moore’s write-up here.

The post This MKR Zero system gives early warning of potential sump pump problems appeared first on Arduino Blog.

This MKR Zero system gives early warning of potential sump pump problems was originally published on PlanetArduino

[pauljacobevans]

Find Your Way with Tiny Laser Beams

For their final project in embedded microcontroller class, [Aaheli, Jun, and Naomi] turned their focus toward assistive technology and created an Electronic Travel Aid (ETA) for the visually impaired that uses haptic feedback to report the presence of obstacles. We have seen a few of these types of devices in the past, and they almost always use ultrasonic sensors to gauge distance. Not so with this ETA; it uses six VL53L0X time-of-flight (ToF) sensors mounted at slightly different angles from each other, which provides a wide sensing map. It is capable of detecting objects in a one-meter-wide swath at a …read more http://pje.fyi/Q8KmbG

[thenashesizer-blog]

Lewis - Notes from meeting with James Medd + Mike Cook - 14-12-17

Mostly we caught James up with discussions to date…

Key agreed points that came out…

Ableton Live - Lewis to contact Ableton, alert them to the project and request support via user licences for The Nashesizer team and ongoing advice from the Ableton technical team who are likely most knowledgeable about what we’re attempting.

We’re agreed that two-way OSC over Serial via USB between Live and The Nashesizer is essential. We could do this via MIDI easily enough - but it’s protocol adds a layer of abstraction we’d like to avoid. We’re each going to look at various combinations of Live, found Max4Live devices (James), monome.org’s serialosc and the Arduinome firmware (Mike) and other OSC via Serial and Teensy 3.6 examples (Lewis), report back with findings and decide on best approach from there. We’ll likely develop a customised solution integrating various elements from this research and testing.

While we still have to test whether a touchscreen is actually that effective an input mechanism for Gemma - and Lewis still has to think more about what it could actually be used for and it’s various ‘modes’ - we agreed that using a Raspberry Pi 3 Model B or Zero would be the best solution for actually driving it. Mike confirmed the Pi could control the touchscreen directly, via its Linux OS or via a Processing sketch and associated GUI libraries.

Now that we’ve received the first tranche of money from Sound and Music Lewis will get on with compiling a bill of materials (BOM) to distribute for feedback. He’ll then order some of the components we’ve agreed are likely to be included in a testing and development version of The Nashesizer - the joystick, motorised sliders and rotary encoders.  We’ll then start working up test versions of these modules - extending and adapting Mike’s schematics from the prototype as well as addressing particular design and layout issues we’ve already identified and prioritised - optimising the spacing of the motorised sliders for Gemma’s use and designing and fabricating the mechanism for an alternative rotary encoder set up where the encoder is turned through 90 degrees.

Gemma still has to try out Mike’s ‘gestural control’ module demos - though we liked the idea of a pixel matrix as visual display for the Skywriter Hat as a possible ‘hands-free’ X-Y pad. We agreed the Adafruit VL53L0X Time of Flight Distance Sensor or Sparkfun ZX Distance and Gesture Sensor requires an ‘on/off’ switch - ideally a foot switch - to be anyway useful as an input mechanism - but again this is something Gemma has to test.

We discussed the idea of developing a feedback questionnaire for Gemma - to encourage her to spend more time testing prototypes and not dismiss them too quickly.

Unfortunately Gemma’s not been well - and so we’ve not been able to meet up and discuss our planning and scoping with her nearly as much as we’d like - though this definitely has to happen before we start to firm up a clear outline for the next ‘development and testing’ phase. This will also likely have an impact on the proposed timeline - though we’re aware Gemma has a Metal residency opportunity in mid-Feb we’re keen to respond to.

[planetarduino]

Making a mini 360° LiDAR for $40

LiDAR (or “light detection and ranging”) sensors are all the rage these days, from their potential uses in autonomous vehicles, to their implementation on the iPhone 12. As cool as they are, these (traditionally) spinning sensors tend to be quite expensive, well out of reach for most amateur experimenters. Daniel Hingston, however, has managed to build his own unit for under $40, using an Arduino Uno and a pair of VL53L0X time-of-flight (ToF) sensors.

The lighthouse employs a small gearmotor to rotate the two sensors on top of its cylindrical 3D-printed housing, passing signals to the Arduino via a slip ring. Data can then be visualized using a Processing sketch running on a nearby computer.

As seen at around the 10:00 mark in the video, the setup has been utilized to map out different test enclosures, and could be excellent for use in small robotic applications. More details can be found in Hingston’s tutorial here.

Making a mini 360° LiDAR for $40 was originally published on PlanetArduino

[planetarduino]

Lighting the Way for the Visually Impaired

The latest creation from Bengali roboticist [nabilphysics] might sound familiar. His laser-augmented glove gives users the ability to detect objects horizontally in front of them, much like a cane or pole is used by the visually impaired to navigate through a physical space.

As a stand in for the physical cane, he uses the VL53L0X time-of-flight (TOF) sensor which detects the time taken for a laser source to bounce back to the sensor. Theses are much more accurate than IR distance sensors and have a much finer focus than ultrasonic sensors for excellent directionality.

While the sensors can succumb to interferences from background light or other time-of-flight sensors, the main advantages are speed of calculation (it relies on a single shot to compute the distances within a scene) and an efficient distance algorithm that simplifies the measurement of distance data. In contrast to stereo vision, which requires complex correlation algorithms, the process for extracting information for a time-of-flight sensor is entirely direct, requiring a small amount of processing power.

The glove delivers haptic feedback to the user to determine if an object is in their way. The feedback is controlled through an Arduino Pro Mini, powered remotely by a LiPo battery. The code is uploaded to the Arduino from an FTDI adapter, and works by taking continuous readings from the time-of-flight sensor and determining if the object in front is within 450 millimeters of the glove, at which point it triggers the vibration motor to alert the user of the object’s presence.

Since the glove used for the project is a bicycle glove, the form factor is straightforward — the Arduino, motor, battery, and switch are all located inside a plastic box on the top of the glove, while the time-of-flight sensor sticks out to make continuous measurements when the glove is switched on.

In general, the setup is fairly simple, but the idea of using a time-of-flight sensor rather than an IR or sonar sensor is interesting. In the broader usage of sensors, LIDARs are already the de facto sensor used for autonomous vehicles and robotic components that rely on distance sensing. This three-dimensional data wouldn’t be much use here and this sensor works without mechanical moving parts since it doesn’t rely on the point-by-point scan from a laser beam that LIDAR systems use.

The HackadayPrize2019 is Sponsored by:

Lighting the Way for the Visually Impaired was originally published on PlanetArduino

[planetarduino]

Automate a rubber strip door with Arduino

In order to separate their office and shop areas, NYC CNC installed a rubber strip assembly that had to be pushed out of the way every time someone wanted to walk through. Although functional, it was also quite annoying, so they installed a system that uses a pneumatic cylinder to automatically move the rubber strips out of the way.

The device uses an Arduino Nano for control and VL53L0X  time-of-flight sensors for presence detection. In addition, it features a clever gear and belt assembly to mirror one side of the door with the other.

You can find more details of the build in the video below and check out the project’s components, Fusion 360 design files, and Arduino code here.

Automate a rubber strip door with Arduino was originally published on PlanetArduino

[thenashesizer-blog]

Lewis - Notes from discussions with Mike Cook & Craig Howlett - 28-11-17

As a follow up to the Retrospective Notes from The Nashesizer meeting on 6th November 2017 Lewis has since had Skype/mobile calls with Mike Cook and Craig Howlett - below brief summaries of key points.

Lewis worked up a rough block diagram for a next version Nashesizer based on previous deliberations as a discussion starter…

Mike Cook

Seeing Gemma use her current set up

We agreed that it would very useful to actually see Gemma using her current favoured hardware/software set up to work on projects at home and also perform. This would give the team valuable insight into how she currently works, what solutions she’s already implemented to make things easier for herself and what she still struggles with. Our design process should take this into account. So we’re going to suggest a session with Gemma where we film her in action - likely at one of her one-to-one sessions with Craig.

‘Gestural control’ module

We discussed the idea of a ‘gestural control’ module for Gemma - the distance/capacitive sensor module in the block diagram above - and while we’re not convinced it will actually be that usable by Gemma (its difficult even for the able-bodied to get reliable and repeatable control out of them) we thought it was worth working up some demos for Gemma to test - which Mike is going to action and then post details to the blog.

Mike suggested trying out the Skywriter Hat (£16 - Pimoroni) - which uses electrical near-field 3D sensing to generate positional data and detect common gestures like flicks and taps - and also the Adafruit VL53L0X Time of Flight Distance Sensor (£15.50 - Pimoroni) which uses a tiny invisible laser source and a matching sensor or Sparkfun ZX Distance and Gesture Sensor (£21.38 - Cool Components) which bounces infrared (IR) beams of light from the two LEDs on either side off of an object above the sensor. These sensors are far more precise than alternatives such as ultrasonic range finders.

A particular usability issue with these types of sensors is that they output data continuously - so we discussed the option of an additional ‘ON’ button - the module would only output data when this is pressed - and Mike suggested this might be easier for Gemma to control with a foot switch so we’re going to try this out.

Track ball module

Mike had previously sent a link to these APEM R Series removable bezel trackballs - which look ideal but are expensive (>£150). We mooted the possibility of sourcing a second hand Atari track ball or deconstructing Gemma’s old and retired track ball for parts.

We discussed various ideas for refining it’s use - a couple of additional buttons to disable movement in the x or y-axis; a button to switch between fine and coarse movement (Gemma’s current track ball while old and bulky has this functionality and she likes it) - through this could also be a more variable rotary encoder.

Mike suggested we could use an Arduino Micro Pro configured just for the trackball with it’s own separate usb socket.

Alternatively, we could just use an optical mouse turned upside down. It’s an intriguing possibility - it certainly works though how easy it would be for Gemma to actually use requires testing - and its definitely a much cheaper solution.

Motorised faders module

Mike confirmed that multiple faders and encoders would only need one micro-controller within a single module.

We agreed that we’d need to physically ‘mock up’ a fader bank to check that Gemma can use it effectively - perhaps by optimising the spacing required between faders.

We also agreed that an earlier idea of buying a second hand Behringer BCF2000 MIDI controller which has 8 motorised faders and hacking it probably wasn’t worthwhile in the short term.

Joystick module

Though quite compact (~40mm square) compared to the joystick in the prototype the APEM 100113 2-axis, 4-position joystick is reasonably priced at £13 and worth testing.

TFT + Touchscreen module

We agreed that an Adafruit 3.5" TFT 320x480 + Touchscreen would not only provide a larger on device display but also the potential for a flexible touch interface - although we’d need a Teensy 3.2 with it’s larger RAM to drive it. While this wouldn’t have the tactile quality of a bank of physical buttons we could easily test different ‘virtual button’ spacings and layouts - such as the Ableton Live transport buttons - and see which worked best for Gemma.

A Sparkfun 2x2 Button Pad with RGB LEDs set up as a radio group could sit next to Touchscreen and change the functionality of the screen.

Craig Howlett

While Craig is certainly interested in the development of the device overall his main role is to work regularly with Gemma on a one-to-one basis and support her developing a better understanding and skills in working with Ableton Live, integrating her existing hardware into her workflow and in testing and providing feedback on the various iterations of The Nashesizer.

We agreed that Craig should contact Gemma and arrange a series of regular, min 2-weekly sessions in her diary - at least until the end of February 2018. Craig will then confirm those dates with the rest of the team so that we could join them occasionally.

As discussed with Mike, an early session would document Gemma’s practice - to give us better sense of where she’s up to and the way she currently works when making a piece of work and/or performing live. We need to start with where Gemma is currently at - to understand what she’s comfortable and confident with; what she finds more difficult to realise; and what she’d like to do but currently can’t. The Nashesizer needs to respond to these issues and needs.

We appreciate that Gemma is currently far more familiar with Studio One than Ableton Live - but we want to encourage her to try Live more and to begin to appreciate it’s more sophisticated functionality and creative potential.

We discussed that Craig could start by comparing Studio One and Ableton Live like for like - so that Gemma can transfer the understanding she already has from one piece of software to the other.

Craig should also focus on the less familiar Live ‘session’ view - working up a demo to show how to build scenes and then move between these using Gemma’s Korg nano pad and Live’s MIDI mapping functionality to easily trigger an individual scene.

Later sessions should focus on getting ready for Gemma’s Metal residency in mid-February - actually working up creative projects that might be useful for the residency and in the process develop her knowledge and skills in using Live.

Craig suggested he could work up a flexible lesson/session plan on a week-by-week basis.

Generally we agreed that we need to encourage Gemma to use Ableton Live more - to nudge her out of her comfort zone; to try things out but not dismiss things too quickly; to gently challenge her understandable avoidance techniques; and to be a bit more critical in attempting to help move her forward.

Perhaps, as Craig suggests, we could work towards a deadline where Gemma agrees to delete Studio One off her computer.

Lewis will also contact Gemma and arrange a meet up soon to update her with developments and get her feedback, input and buy in of our plans.