Search results for:

Hm well in that case I'll have to move the parts in "0" position manually before connecting the MeArm because one problem which is being caused by this is that for example the servo at the base, which holds the whole unit, starts oscillating back and forth because of the quick movement and the inertia of the arm.

I have just connected a bunch of sensors (e.g. MPU6050, DHT22, BMP085, RFID, CC3000 Wifi) and wanted to see how much information I can display at once in 'realtime'.
I'm also sending the sensordata via MQTT to collect it.
I don't have a specific project in mind, I'm just looking for viable IoT solutions.

One idea would be a smart heatbed module for 3D printers which will automatically pre-heat and regulate the heat based on the MES information and the order management.

Hi,

I've got the MeArm recently and I'm trying to control the servos.

It comes with those cheap blue servo motors (sg90), which are depicted in the servo tutorial:
http://www.espruino.com/Servo+Motors

I've tried this simple example just to move a part between two positions in 3 seconds each time it moves.

var s = require("servo").connect(C7);

//s.move(0); // move to position 0 over 1 second
//s.move(1); // move to position 1 over 1 second
//s.move(0.5, 3000); // move to position 0.5 over 3 seconds

// move to position 0 over 1 second, then move to position 1
s.move(0, 3000, function() {
  s.move(1, 3000);
});

My question now:
Is it normal, that as soon as I execute the first move for a specific servo object (even multiple other ones) it will move instantly/quickly instead over the specified time?
After that first move all moves will be executed accordingly.

BR
Daniel

It won't budge on the Espruino. I'll get more modules in a few days, then I'll check if it's only this one or the heltec modules in general.

I think the heltec module is just a bit wonky.
I've now tried it with a Spark Core and it works there just like with the Arduino out of the box.
Someone on the Spark forums only got theirs only to work by adding the pull-up resistors.

Ok I think I figured out the problem.
Most likely the Cruis module, as well as the Adafruit module have pull-up resistors built in (the Adafruit has them).
And the "cheap" heltec module doesn't. So adding 4,7k Ohm resistors to the i2c pins will fire up the display.

The strange thing is that the heltec module (the one OP uses) works on my Arduino UNO on 5V and 3,3V. I also thought it was dead but then I tried it on the Arduino. So the voltage from the Bat pin on the Espruino should be more than enough.

The Crius C0-16, which is also being used on the tutorial/module site here works with the Espruino as inteded.

It's really strange.

Nope, no errors in the console and no picture.

I got the actual (probably higher quality) module from the tutorial today (Crius C0-16) and that one works.

I just tried this and ran into the same problem (exact same module).

It works on my Arduino Uno with 3,3V and 5V (the address is 0x3c)

Did you supply the 5V directly or via the Espruino Bat?
Because when I supply 5V via the Espruino it still won't work...

Thanks Gordon, moving the wlan connection to onInit seems to be the solution, it works now ;-)

Yes, it's running 1v71.
Sadly this didn't work, it just doesn't continue after ">echo(0);" as soon as the Clock module is added for import. I'm now trying to get it running in standalone by importing the modules from the SD card.

I've also tried to remove the ADXL335 accelerometer code and it also worked.

I'll try another accelerometer sensor, looks like the Clock module and the ADXL335 don't like each other for now.

BR
Daniel

The web IDE will just stop after ">echo(0);" with no error message.

If I leave out just the Clock module import it will execute the code up to the point where it tries to initialize the clk variable and throw an error message, so I guess the Clock module import seems to be the problem somehow.

Hi everyone

I have used this code to retrieve sensor data:

var foo = require("ADXL335").connect(C3,A0,A1);
var wlan = require("CC3000").connect();

wlan.connect( "xx", "xxx", function (s) { 
  if (s=="dhcp") {
    console.log("My IP is "+wlan.getIP().ip);
    require("http").createServer(function (req, res) {
      var d= foo.readG();
      var data=  {"x":d[0], "y":d[1], "z":d[2]};
      res.writeHead(200, {'Content-Type': 'text/plain'});
       res.write(JSON.stringify(data));
       console.log("x " + d[0] + " y " + d[1] + " z " + d[2]);
     // res.write("x " + d[0] + " y " + d[1] + " z " + d[2]);
      res.end();
    }).listen(80);
  }
});

This works just fine. Since I also want to have current timestamps for the sensordata logging, I tried to set the clock as described in the reference, which results in this:

var foo = require("ADXL335").connect(C3,A0,A1);
var wlan = require("CC3000").connect();
var Clock = require("clock").Clock;

wlan.connect( "xx", "xxx", function (s) { 
  if (s=="dhcp") {
    console.log("My IP is "+wlan.getIP().ip);
    var clk=new Clock("Jan 07, 2015 12:38:00");    
    console.log(clk.getDate().toString());
    require("http").createServer(function (req, res) {
      var d= foo.readG();
      var data=  {"x":d[0], "y":d[1], "z":d[2]};
      res.writeHead(200, {'Content-Type': 'text/plain'});
       res.write(JSON.stringify(data));
       console.log("x " + d[0] + " y " + d[1] + " z " + d[2]);
     // res.write("x " + d[0] + " y " + d[1] + " z " + d[2]);
      res.end();
    }).listen(80);
  }
});

But this code won't execute. The clock code parts will work on their own, but as soon as I try to initialize the Clock module with the previous sensor/wifi code, it won't work anymore.

Any ideas?

BR
Daniel