Omega not creating wifi
I just got my Omega2 and Extension dock, but the light never flashes, it just goes solid amber, and never creates a wifi network to connect to. What should I do? Do I have a defective unit?
Thanks in Advance, Samuel
@Samuel-Martin I'm not sure what to tell you but you should be able to hold the reset button for 10 seconds to perform a factory reset. I'm not the right person to ask though.
You need to look at the output on the serial-port in order to find out what the problem is.
@Samuel-Martin Use the first Serial Port to help debug.
@Tyler-Mattioli ![alt text](image url)I tried holding the button but it doesn't do anything. I will look into the serial port on the omega now.
I'm not quite familiar with the LED sequence but if it's not providing a WiFi network then I would take it as DOA and notify Onion accordingly.
They might ask you to carry out a few tests before you return it them.
this is what I get when I try the verbose thing on the serial port.
@Samuel-Martin That's an OSX-error. I don't use OSX, so I can't help with that.
Indeed... it would appear that the factory install of the OSX
cuprogram is a bit broken, I get the same issue if I try that on my work macbook.
The issue is probably not access to the serial device (that works fine using my custom serial client) but rather lack of permission to create the lock file.
A post on apple.stackexchange suggests that running
sudocould work; normally I'd argue against that, though in the case of a tool that ships with the operating system it's a bit less risky (compared for example to when Linux people suggest doing that to an unknown-origin build of the Arduino IDE or the Android adb tool, rather than add their Linux user to the dialout group or set up proper udev rules). Still using
sudounnecessarily feels wrong - it's just not a good habit to get into.
It may be simplest to use a different serial terminal program on OSX, that does not attempt to create a lock file in a disallowed system directory.
@Samuel-Martin The device name that you used may be a device name for FreeBSD... I found this article that demonstrates how to find out the device name of a serial USB device here:
@fossette The issue of the posted error message exists even when a valid serial device (ie, one that works with other terminal programs) is specified, even by its full path name. It really appears that the factory install of
cuis not usable by ordinary users, and that the issue is with an application-specific lock file not the serial device.
(Hence, it is quite different than the typical Linux issue of the user not being in the dialout group or whatever owns the serial devices, and unless
cuhas an undocumented "don't bother with lock files" option, it's not clear how one could cleanly fix it)
That said, you may have a point about the name of the device node - the name Samuel-Martin is using for the device file is unfamiliar to me, so it could be an additional problem that would show up after the posted error message was overcome. I would normally expect something related to the name of the USB-serial chip, or a "/dev/cu.usbmodem..." or something like that, but I don't know what serial connection is actually being used here.
I tried using sudo, and the I never worked, and I tried to Los the try device, but says no such file or directory.