Posts made by dklinkman

Well there you go. I'm pretty familiar with Node-Red so I didn't bother to read the Onion docs on it. But the answer was right there plain as day. Installed, rebooted, and Manage Palette appears.

Thanks for the pointer.

-d

The device is about 10 feet from the AP. Curious that this occurs at precise 2 hour intervals. That doesn't seem like noise or weak signal. Maybe I'll look at the AP settings to see if there is an inactivity setting or something. Though I've never heard of that.

After the Omega2 Pro boots up, I keep a monitor on the serial console. The following was on the console the next day.

BusyBox v1.28.3 () built-in shell (ash)

/ __ ___ ()__ ___ / __ _ _ ___ ___ ____ _
/ // / _ / / _ / _ \ / // / ' / -) _ / _ /
_/////___//// _////_/_, /_,/
W H A T W I L L Y O U I N V E N T ? /__/

O-ware: 0.3.1 b214

root@Omega-B000:/# [ 7260.478448] Interface apcli0 link up! (WPA2PSK AES)
[14475.163003] Interface apcli0 link up! (WPA2PSK AES)
[21681.359565] Interface apcli0 link up! (WPA2PSK AES)
[28888.613048] Interface apcli0 link up! (WPA2PSK AES)
[36098.738045] Interface apcli0 link up! (WPA2PSK AES)
[43305.963114] Interface apcli0 link up! (WPA2PSK AES)
[50513.198418] Interface apcli0 link up! (WPA2PSK AES)
[57721.495145] Interface apcli0 link up! (WPA2PSK AES)
[64927.688575] Interface apcli0 link up! (WPA2PSK AES)

I assume this is normal. But why is this message repeating? From the timestamps it's repeating every 2 hours.

Thanks.

-d

I installed Node-Red using the console and it seems to start up and work just fine. But there is no Manage Palette in the menu, needed for installing additional nodes.

I assume this is because NPM is not installed. I tried installing NPM w/ opkg install npm. The install began and I believe there was a dependency on nodejs, which then conflicted with node. Possibly the node that Node-Red runs on. So the install failed.

Any ideas on how to get NPM installed w/ Node-Red?

Thanks -d

I have the same setup but my MCU_RESET works properly (button is face up on the PCB, about .25" from the ATmega). No Omega2+ reset.

I finally got the arduino dock 2 working under O2+ 0.1.9 b149 and I built up a commented example for using the I2C interface between the Omega and the dock. For the example ideally you would have an external LED w/ resistor attached between ground and digital pin 12 of the arduino headers. But if you don't have that you can simply change the code right at the beginning to use digital pin 13 which is effectively the blue led on the dock:

#include <Wire.h> // for i2c communications

int EXTLED = 12; // use any arduino digital pin between 2 and 12, or 13 if no external led
int REGISTER[8]; // can range in size from 1 to 255
int INDEX = 0; // current index into the register
int STATE = 0; // current state

void setup() {
  pinMode(LED_BUILTIN, OUTPUT); digitalWrite(LED_BUILTIN, LOW); // blue led on the arduino dock 2
  pinMode(EXTLED, OUTPUT); digitalWrite(EXTLED, LOW); // my selected external led
  Wire.begin(0x08); // 0x08 is the arduino dock 2 i2c port
  Wire.onReceive(i2c_on_receive_handler);
  Wire.onRequest(i2c_on_request_handler);
  Serial.begin(9600); // serial output to /dev/ttyS1 on the omega2
}

void loop() {
  // the first byte of the register controls blinking for the external led
  // to start the blinking: i2cset -y 0 0x08 0x02 0x00 0x01 i # the third byte sets index 0
  // to stop the blinking: i2cset -y 0 0x08 0x02 0x00 0x00 i # the last byte is the value
  if (REGISTER[0] != 0) {
    digitalWrite(EXTLED, HIGH);
    delay(1000);
    digitalWrite(EXTLED, LOW);
    delay(1000);
  }
}

// called when a transmission is received via the i2c port
void i2c_on_receive_handler(int bytes_received) {
  int cmd = Wire.read();
  int v = 0;
  Serial.print("received command/data, value: "); Serial.print(cmd, HEX); Serial.print("\n");
  switch (cmd) {
    case 0: // toggle the blue led once - ex: i2cset -y 0 0x08 0x00
      digitalWrite(LED_BUILTIN, !digitalRead(LED_BUILTIN));
      Serial.print("toggled led\n");
      STATE = 0;
      break;
    case 1: // turn the blue led on or off - ex: i2cset -y 0 0x08 0x01 0x01 i # for on, last byte 0x00 for off
      v = Wire.read();
      digitalWrite(LED_BUILTIN, v ? HIGH : LOW);
      Serial.print("led value set to: "); Serial.print(v); Serial.print("\n");
      STATE = 0;
      break;
    case 2: // write value to the register at index - ex: i2cset -y 0 0x08 0x02 0x00 0x01 i # 3rd byte is the index, 4th byte is the value
      INDEX = Wire.read(); v = Wire.read(); // note: should check valid range for INDEX, in our case 0-7
      REGISTER[INDEX] = v;
      STATE = 0;
      Serial.print("wrote value: "); Serial.print(v, HEX); Serial.print(" to register at index: "); Serial.print(INDEX, HEX); Serial.print("\n");
      break;
    case 3: // prepare to read a value from the register at index - ex: i2cset -y 0 0x08 0x03 0x00 i # 3rd byte is the index
      INDEX = Wire.read();
      STATE = 3; // register value at index can now be read - ex: i2cget -y 0 0x08
      Serial.print("set register index to: "); Serial.print(INDEX); Serial.print(", and state to 3\n");
      break;
    default:
      Serial.print("error, unexpected command value!\n");
  }
}

// called when data is requested via the i2c port
void i2c_on_request_handler() {
  byte v = 0;
  switch (STATE) {
    case 0: // default - reads and returns the current state of the blue led - ex: i2cget -y 0 0x08
      v = digitalRead(LED_BUILTIN);
      break;
    case 3: // read and return register value at index - must be set up for read using command 0x03 from above
      v = REGISTER[INDEX];
      STATE = 0;
      break;
    default:
      ;
  }
  // note: any attempt to print causes the Wire.write() to fail - don't know why
  // Serial.print("received request, returned: "); Serial.print(v, HEX); Serial.print("\n");
  Wire.write(v);
}

Basically you use i2cset and i2cget to send commands and data to the arduino and possibly retrieve data back. For example to simply toggle the blue LED:
i2cset -y 0 0x08 0x00

This sends a command byte of 0x00 to the arduino via I2C port 0x08. The blue LED will toggle on or off. These use command byte 0x01 with some data to explicitly turn the blue LED on or off (vs toggling):
i2cset -y 0 0x08 0x01 0x01 i # turns blue led on
i2cset -y 0 0x08 0x01 0x00 i # turns blue led off

Notice the addition of the 'i' at the end of the command line because now we are sending an array of bytes vs a single byte. The example also has a data register that can be used to store values or to control something. In the example I am using the first byte of the register to control whether the external LED is blinking or not. Command byte 0x02 is used to write to the register at a specified index:
i2cset -y 0 0x08 0x02 0x00 0x01 i # writes value 0x01 at index 0x00 of the register - external LED blinks
i2cset -y 0 0x08 0x02 0x00 0x00 i # writes 0x00 to the register stopping the external LED blinking

It's possible to request data from the arduino also. This reads the current state of the blue LED:
i2cget -y 0 0x08 # that's it - no other bytes - will return 0x00 or 0x01

To request data from the register you first have to tell the arduino where to read from. First we'll write some data to the register at index 0x07:
i2cset -y 0 0x08 0x02 0x07 0x99 i # write 0x99 to register at index 0x07

And now request the data back but first you have to say from where using command byte 0x03:
i2cset -y 0 0x08 0x03 0x07 i # pre-set index to 0x07 for subsequent request
i2cget -y 0 0x08 # should return 0x99

These sequences can be packaged into scripts also to make life simple. For example, to continuously blink the blue LED, this script could be called i2c-blink:
while true
do
i2cset -y 0 0x08 0x00
sleep 1
done

You can define an alias when you start getting tired of typing (or forgetting) the -y 0 all the time:
alias i2cset='i2cset -y 0'
Then use a simpler:
i2cset 0x08 0x00 # toggles the blue led

So anyway, that's my slightly non-trivial I2C example for the arduino dock 2. Hopefully there are no typos in my sample commands above. Enjoy!

I tried this just now and it seems to work great. It's the same AP but now with multiple SSIDs. Just added an extra 'option ssid' to /etc/config/wireless

Still having pretty good luck with Omega and Omega2+. Wireless needs to be tweaked a bit but it works great. I got Ethernet to work with just a few fiddles. I even put the Omega2+ and the GPS dongle into a window and eventually got solid GPS data from 13 satellites. GPIO seems broken with the current build. At least when following the examples. Granted being a computer and Linux and network guy helps with all of this. But it does work.

I'v actually been having really good luck with the Omega2. AP mode works well, STA mode works great. Accessing the Internet via wireless works well. Serial console works well. Setup went smoothly. Web UI is functional. Cloud access doesn't work yet. I'm not very knowledgeable of WRT so there are things I am used to in a typical Linux that are missing. But so far so good. I am supplying the device with ample power

Ok now I understand the minimalist OS for Omega due to limited storage. I don't have a cross -compile environment but I do have other Linux instances where I can prepare a storage device if I want. More than anything I was just curious why fdisk would display partitions but not modify or create them. Now I know.

Thanks for your response!!!

So there's no way to partition or format USB storage? I can only mount and dismount the storage?

Brand new Omega user here. But not new to Linux.

I plugged a 32GB USB drive into the expansion dock and it shows up as /dev/sda. So far so good.

Tried to partition it using fdisk /dev/sda but that only displays information. Typically that would return a partitioning menu.

Also mkfs.ext4 /dev/sda1 doesn't work. Command not found.

OpenWRT Wiki suggest these commands should work. https://wiki.openwrt.org/doc/howto/storage

But obviously there is something I don't know or understand in Omega land.

I am able to mount and access the default FAT partition on the USB just fine.