I mean physically, how well-seated are the relay expansion modules plugged into the pass-through socket on the expansion dock?

Short of a circuit design problem or defective parts (I am not yet convinced of either, just trying to chime in to help), another area you can turn your attention to, to try to solve the problem, is to see if the stuff is physically making contact for all the signals.

If you have an intermittent connection, something like what you are seeing is possible.

This is a common complaint. There are ways to use the docks and add a micro SD card for more storage, and a couple different techniques to extend storage onto the card. Look for the articles on this site.

Leonard I have had decent communication success doing either of the following:

1. Twitter
2. Open a ticket

I'd currently recommend #2, it's more official and they are responding using this system currently. I actually used both yesterday when I wasn't getting an answer and got answers on both.

I'm no fanboy, but at the same time, I do think they're trying to improve communication.

This is a common complaint. There are ways to use the docks and add a micro SD card for more storage, and a couple different techniques to extend storage onto the card. Look for the articles on this site.

They've just launched Omega 2 with a fairly tight kickstarter schedule. I'm not speaking for them, but I'm guessing they might re-stock a maximum of one more time before it is Omega 2 all the way.

Thanks much this has me a little more on track.

I looked over the header files, and almost every one appears to already have guards in place. BTW, this is proving a good lesson in the concept for me

For good measure, and after reading the articles, I also put #pragma once at the top of all header files just in case.

Unfortunately no luck. Looks like my errors are coming from the C files and not the headers. For example:

build/can-utils-master-edit/slcan_attach.o: In function main': slcan_attach.c:(.text.startup+0x1): multiple definition of main'
build/can-utils-master-edit/bcmserver.o:bcmserver.c:(.text.startup+0x1): first defined here

Is placing guards in C file ALSO advised?

Made a little more progress over the weekend.

I went into the zip file from GitHub and stripped it of any and all non- C and H files, and evaluated the content of any files I was taking away. They all appeared to be 'harmless' to remove, such as the existing makefile which would be ignored anyway, and some readmes with little content, or one auto-config script file that I can always manually execute or add back in.

I do kind of get stuck at the same point though. I upload everything to cloud compile, it attempts to compile, and I'm faced with a wall of errors that appear to be:

• Mostly references to "multiple definition of ___"
• "first defined here"

and then finally:

• collect2: error: ld returned 1 exit status
• make: *** [bin/cloud-compile-target] Error 1

Can someone bridge the gap for me and let me know how to approach solving my errors? Am I attempting to use Cloud Compile in the correct way?

Thank you @Luciano-S that was indeed it. Appreciate the oversight!

Thank you, no I didn't I'll look immediately! Will update post accordingly once I go over it.

Hi All,

I'm an experienced electrical engineer, but definitely light when it comes to coding. I can do some Python, but haven't delved into C++ in years (or similar, where actual compiling takes place).

I want to use Can-Utils on my Omega:

https://github.com/linux-can/can-utils

But it appears that I'll either need to Cloud Compile or setup a cross-compilation environment.

I tried cross-compilation, but I hit a brick wall on my other Linux box with errors that seem like quite a bit to dive into.

As an alternative, it seems like Cloud Compile is perfect for me. With that said, I'm starting at zero for exactly how to take what is in the link above for Can-Utils, and package it CORRECTLY for Cloud Compile to do it's job for me.

Anyone able to lend a suggestion or two my way. I am willing to read material on this, but am having a hard time determining what to search for.

Thanks!

--Jim--

I'm trying to follow the pivot-overlay tutorial to allow my rootfs to extend onto my 4GB uSD card (connected through USB adaptor.

I am getting some errors when I get up to the step when I'm copying "overlay" to the uSD card:

tar: can't create symlink from ./.fs_state to 2: Operation not permitted

That is at the start of the operation. In then successfully copies plenty of files

Later, I get about a dozen of these errors before the operation ends, all for different files in that directory:

tar: can't create node ./upper/etc/uci-defaults/11_migrate-sysctl: Operation not permitted

• I am using a freshly factory restored Omega

Any help?

--Jim--

No, he let the relay stick a few times and it worked itself out. Interesting!

Glad you're on your way. BTW, not sure your level of solder skills, but I like two of the suggestions above and would try either of them if you get more problems:

1. Replace the relay with a pin-compatible heavier-duty one (or)
2. Have the onboard relays drive the coil of heavier-duty relays

Okay gotcha.

• If you've already done the trouble-shooting of moving the expansions around and they still stick, I think that rules out the possibilities I suggested.
• I don't think this is the cause of any of your troubles, but for this installation you may want to consider printing out a 3D case for the Omega and dock, at least to keep some of the stuff from getting dust and dirt on them. I don't have the link handy, but I did get one of the cases I found online printed recently, and the fit was near-perfect first shot. I wound up not needing the top portion, but if I did it would've needed just a bit of tweaking to allow the relay expansion to sit nicely.