@György-Farkas the out of the box state is continuous illumination. that is the manufactured normal state. any other state needs to be arrived at by user software control. that is a user defined state. look, you can beat this to death if you want, but i'm looking for help which you seemingly do not want to offer or can not offer. so why the trolling? please, just leave it effing alone.
@György-Farkas thing is i realize it is possible to blink the LED if one wants to do that. however the normal state of that blue LED is to be continuously illuminated and on my dock that is no longer the case. hence this request to anyone that might have an idea about how to restore the continuous illumination. it seems it is a hardware component failure or near failure that is happening and so if anyone has any insight into what component it might be i'd appreciate knowing. thanks.
watch this video if you need to see the normal LED state,
https://youtu.be/fo_KEEIQO9M?t=285
@György-Farkas hi, that is not my understanding of the dock LED. this particular blue LED did stay illuminated during operation. although the following clip is short you can see that the blue LED is continuously illuminated. the blinking LED of the arduino is done via an external LED.
https://www.youtube.com/watch?v=u5o5xAGO6ck
https://docs.onion.io/omega2-arduino-dock-starter-kit/arduino-kit-blinking-led.html
the power LED on my ardunio dock 2 has, after 2 months of being powered continuously, ceased to stay on. however it does flicker at times and at other times remains very dimly illuminated. the dock itself appears to be working ok. i was able to install the arduino dock 2 software via opkg again and i can still do wireless transfer of sketches and they run ok. but still i'm left wondering if this is a problem. the LED itself still functions as it will at times burn normal brightness for short periods. i'm just puzzled about what the issue could be and if there is a possible fix either hardware or software. if anyone has an idea about this i'd appreciate some feedback. thanks.
@ice-long you might want to think about doing the procedure described in the documentation.
https://docs.onion.io/omega2-docs/boot-from-external-storage.html
@Christopher-Bunnell the dash is probably pretty similar to the onion hologram since they were pretty much developed at the same time. if you can find the pinout sheet for the dash and also the pinout and maybe tech reference for the onion you might be able to cross reference the pins that onion uses with the onion cellular and just match those same pins from the dash and using wires plug those dash pins into a onion expansion, anyone of the expansions should do.
@Maximilian-Gerhardt you sorta out did even yourself with this post :)
thank you. it will be very helpful.
@Simon-Cain hello, just wanted to add that the mac address on my omega2+ also changed.
the link just re-directs to this page. you have any more cool tricks?
worth mentioning that the 5 "accessible" ethernet are on the omega2s which is quite a bit more expensive.
i've tried the oupgrade twice and neither one worked. it goes through the download and certainly looks like it is working but then omega2+ just blinks for 40 min each time, btw running very hot, and then i just reboot and when it comes back up it shows a new b160 installed. i guess i'm gonna try a sysupgrade later.
edit: i tried a different omega2+ and the oupgrade routine worked well as did the overall installation.
@Miguel-Miranda maybe it needs the GNU patch application installed on the build machine?
http://savannah.gnu.org/projects/patch/
@Debjyoti-Acharjee did you install the driver that is linked from this page?
https://docs.onion.io/omega2-docs/connecting-to-the-omega-terminal.html#connecting-via-serial-mac
@Tommaso-Vescovo not sure if you are aware of the un-comment of repos to gain additional files but i did a opkg list search on "blue" and got this back. thought i would post it in case you had not seen these files.
root@Omega-325F:~# opkg list | grep blue
bluelog - 1.1.2-2 - Bluelog is a simple Bluetooth scanner designed to tell you how many discoverable devices there are in an area as quickly as possible. It is intended to be used as
a site survey tool, identifying the number of possible Bluetooth targets there are in the surrounding environment.
bluelog-live - 1.1.2-2 - Bluelog is a simple Bluetooth scanner designed to tell you how many discoverable devices there are in an area as quickly as possible. It is intended to be use
d as a site survey tool, identifying the number of possible Bluetooth targets there are in the surrounding environment. This package contains the files for "Bluelog Live", an optional
mode of Bluelog which creates a real-time webpage of discovered Bluetooth devices.
bluez-daemon - 5.47-1 - Bluetooth daemon
bluez-examples - 5.47-1 - contains many examples apps for bluetooth, requiring python
bluez-libs - 5.47-1 - Bluetooth library
bluez-libs - 5.30-1 - Onion-Customized Bluetooth library
bluez-utils - 5.47-1 - Bluetooth utilities
bluez-utils - 5.30-1 - Onion-Customized Bluetooth utilities
gnunet-transport-bluetooth - 0.10.2-git-20180205-b673e9c3ed4a211b974bc602b893a427533566d7-1 - GNUnet bluetooth transport
ibt-firmware - 2017-09-06-a61ac5cf-1 - Intel bluetooth firmware
jamvm - 2.0.0-1 - JamVM is a new Java Virtual Machine which conforms to the JVM specification version (blue book). In comparison to most other VM's (free and commercial) it is extreme
ly small.However, unlike other small VMs (e.g. KVM) it is designed to support the full specification, and includes support for object finalisation, Soft/Weak/Phantom References, the J
ava Native Interface (JNI) and the
@Ryan-Walmsley yes, it is. SPI has been an issue for onion users. the protocol as implemented on the omega2[+]'s is somewhat broken. there have been many posts of the problems here on the forum so a search of spi will explain what is known.
@Gamaliel-Valencia well, if the thing is still within any type of warranty framework then i would put in a ticket for return, mention the thread so if they have any ideas over what has already been discussed they can join in. but it seems to me you have tried all that you could. other boards have just not responded as well so some of them just may be broken. wish i could offer something else but out of ideas.
@Gamaliel-Valencia hi, it's been awhile since this was discussed so not 100% but i think you may have flashed wrong software. there was one
software for original arduino dock and another for arduino dock2. they are not interchangeable. but it might be something else entirely. search on flash correct firmware for arduino dock 2 on google or here.
@MB hello, i suggest you do some searches on wifi router because last year there were many posts about the abilities of the omega2[+] to connect or not connect to some wireless router models. it seems the omega2 devices have problems with some models of wireless routers.
@cas the only write up i have seen is the readme.md on this page,
https://github.com/OnionIoT/omega2-bootloader and
yeah, that is a good point. there are no links between many of the various examples or tutorials. the original documentation did a good job in referencing and linking the documentation to additional information or another part of the documentation. are these documents able to be edited by the community?