Community

Chris H

@Lazar-Demin
Thanks, I see the download buttons for the Omega2-LTE and DASH but the in the case of the Pro it's as I described earlier.

Downloading the repo works.

Chris H

@Lazar-Demin, just for interest - what's the correct way to download the DXF?

Can it be done using a browser? When I attempted this (right-click "save link as") a DXF file is saved but it's structure is XML and appears to be related to the HTML page on which the DXF file link is presented. Here's the top dozen lines of the 'DXF' for the Omega-Pro:

<!DOCTYPE html>
<html lang="en" >
  <head>
    <meta charset="utf-8">
  <link rel="dns-prefetch" href="https://github.githubassets.com">
  <link rel="dns-prefetch" href="https://avatars.githubusercontent.com">
  <link rel="dns-prefetch" href="https://github-cloud.s3.amazonaws.com">
  <link rel="dns-prefetch" href="https://user-images.githubusercontent.com/">



  <link crossorigin="anonymous" media="all" integrity="sha512-OZSLZxbfZRavuNMaKn9S2z6nOiqb+cSXqL/eTi4TqwhiRm1fDxQpuwjViN7NzGw/nhXT4O0BZIIg0Ym7szrbpg==" rel="stylesheet" href="https://github.githubassets.com/assets/frameworks-39948b6716df6516afb8d31a2a7f52db.css" />
  <link crossorigin="anonymous" media="all" integrity="sha512-jaRxAk/R7Eq6XXtxt2dWYc6UfgT/Jk9zYWYh4UpAt5LFRnYVaWqEM3sPhUFL3fOBmHhHoOcn4wfLkMS21Q1yaw==" rel="stylesheet" href="https://github.githubassets.com/assets/site-8da471024fd1ec4aba5d7b71b7675661.css" />
    <link crossorigin="anonymous" media="all" integrity="sha512-9nE+XgrWtARaS0zwxOiHy2GiHph7zd3w1/JhlkltB0BJKwNHjq0jmjMcOptBcoiHSmpEIeevcNvzeXoHqK77eA==" rel="stylesheet" href="https://github.githubassets.com/assets/behaviors-f6713e5e0ad6b4045a4b4cf0c4e887cb.css" />

etc.

Clicking on the DXF file link directly opens it's content in GitHub - I guess this can be copy-pasted to a local file but that's inconvenient.

I'm using MS Edge FWIW

Chris H

@schluchti

I imagine any hardware that is running an OS is going to take more time to power up that you need.

If the Omega had a sleep mode that'd be the way to do it but as yet, that's not an option.

What is the reason you need such quick power up? Is there some other way to tackle the requirement?

Cheers,
Chris.

Chris H

@dbell You need a USB A to Micro-USB (or in millennial language a "Android Charger") cable. When plugged into to PC it should appear as additional COM port in device manager. If not then your cable might truly be a charge-only cable with no data connections, or there's a fault with the dock.

The only physical UART (serial) connections are on the dock expansion connector. Additionally you'll need voltage level translator/interface circuitry before you can connect this tot he PC serial port (which will use RS232 levels).

Chris H

The 'Magic Smoke' is what makes it work! If you let that out, no workee end of story

Chris H

@Crazi-Tane
From memory: when you connect via USB the computer should register the onion as a serial port.

Just use the ssh as you would over a serial connection (? not familiar with the MAC way of doing this sorry).

HTH

Chris H

Thanks again!

Chris H

@György-Farkas , yes I've recently updated to b227 with the oupgrade -l -f command.

Next question, is there a list of release notes for the 0.3.2 branch & if so, is it accessible?

Chris H

Have you seen: https://onion.io/2bt-may7-2019/

Chris H

@György-Farkas

Thanks, I'd forgotten about the manual method. That worked fine.

Chris H

Sorry to resurrect an old topic but this also happens to me from time to time.

Right now I can see on http://repo.onioniot.com/omega2/images/ that the leatest version is omega2p-v0.3.2-b223.bin but when I run opgrade I get:

root@Omega-6E09:~# oupgrade -l -c

Device Firmware Version: 0.3.2 b222
Checking latest version online...
url: https://api.onioniot.com/firmware/omega2p/latest
Repo Firmware Version: 0.3.2 b222
Comparing version numbers
Device firmware is up to date!
root@Omega-6E09:~# oupgrade -f -c
Device Firmware Version: 0.3.2 b222
Checking latest version online...
url: https://api.onioniot.com/firmware/omega2p/stable
Repo Firmware Version: 0.2.2 b200
New firmware version available, need to upgrade device firmware

How to fix?

Chris H

@Neil-Manuel
Sorry, I just realised your comment was aimed @crispyoz not me.

Apologies.

Chris H

@Neil-Manuel
Tying up loose ends I used the standard calculation for LED resistors using your guesstimate of 1.8V drop on the LEDs together with @crispyoz value of 200R for the resistors:

(Vsupply - Vled)/R = (3.3 - 1.8)/200 = 7.5mA per LED x 2 = 15mA.

I agree @crispyoz could probably get away with higher value resistors (lower current per LED) and still get reasonable light levels. Alternatively, the GPIO might be able to safely handle 15mA, I just ran out of patience trying to find the spec .

Chris H

@crispyoz
It's tricky to find any data on the current sourcing capability of the GPIO pins. I only had a quick look in the Onion docs and the Mediatek datasheet without success.

You're drawing ~15mA from the port with the arrangement you describe assuming the 1.8V LED drop per @Neil-Manuel's reply. Once you find the maximum current source rating on the GPIO pin you can make a call.

It's also worth checking the sink current rating vs the source current as sometimes the sink current is the greater amount. In this case, you reverse the LED(s) direction, attach the resistor(s) to +Ve and switch the GPIO off to activate it.

HTH.

Chris H

It may be a problem because putting the LEDs in parallel means double the current compared to a single LED and the GPIO port might become overloaded.

To run them in parallel safely you need some kind of buffer/driver in between (eg a transistor/FET/Driver IC etc).

Traditionally, to run 2 LEDs at minimum current we would put them in series but then the voltage required to illuminate them will very likely exceed 3.3v and they won't light up - again a driver required.

What is the intended idea behind 2 LEDs from one port? There may be another solution...

Chris H

Regarding the relays, maybe think about SSR (solid state relays). They're a bit more expensive but controllable with logic signals and available up to very high current - beyond 100A at mains voltages.

The AC one also generally offer zero crossing switching i.e. switch at the 0V portion of the AC cycle.

HTH.

Chris H

@luz

Thanks for the suggestion, however ...

"Make clean" made little/no difference to the size, so I tried "make dirclean" but this nuked most everything including the toolchain (!). It did reduce the size to ~450Mb though

Oh well, I'll just have to live with it until I work out a better way...

Chris H

Outstanding!

Following your instructions worked first time. Is there was a way to mod you up or grant points?

Just a follow-up question...

In the home directory of my WSL the 'source' directory is now ~5G in size. Can I delete all but the 'staging_dir' directories and still have a working dev environment?

Since the WSL is on the drive it's cramped the available storage somewhat..

Many thanks,

Chris.

Chris H

FWIW, I tried b163 and also get constant reboot.

Attached is the serial output from the manual firmware upgrade process and subsequent restart as requested.

0_1489031869386_Omega2p_b163_maunal_install_COM3_20170309_145254.txt

Posts made by Chris H