After performing several tests, I found that the problem in the short communication distance was due to the wifi antenna.
I tried with the antenna that comes with the evaluation board of the Omega2s+ and I stopped losing information.
Does anyone know what the part number of this antenna is?
@timj My devices on test are for testing some customised network functionality, as @luz mentioned there are some issues with GPIO and I'm experiencing some strange PWM issues. Once I have time to work through and resolve some of these then I'll be happy to share any changes.
If you're keen to progress this, perhaps start a new thread and everyone can chip in their experiences.
@huntc Glad to see you're up and running. I'm not sure that containers are supported but routing etc is supported and this is the extent of my experience with netns.
I took a look at your product, congratulations looks like a winner.
I found a workaround for my serial connection, just put the microcontroller in deep sleep before trying to awake Omega, this is enough to let it boot correctly. Will not be opening a new thread with that.
@sam-walton The easiest way to set the state of a GPIO at boot is to add the relevant command to the /etc/rc.local file. Depending on your requirements you would use something like gpioctl dirout-low 18
Pls try the sshfs extension, to see if that works for you.
MS always makes it "awesome"..
# onion os version (just FYI)
=== Version Info ===
Omega firmware: v0.3.2 b242
onion-os - 1.0.6-1
1: Set a passwd for the omega user to connect from your workstation over ssh, passwd is the easiest way.
Install SSH FS extension for VSCode in the VS
$ ext install Kelvin.vscode-sshfs
or DL the vsix & add to VSCode
SSH-FS shall create its own icon in the left panel, under "Soucre-Control","Extensions" etc. Click on it to setup the new ssh connection/credentials (IP, username, remote folder etc), pointing to omega.
Click on the "Folder+:" icon under the new connection entry.
This will effectively add the remote folder to the current workspace. You will be
prompted for the passwd, if that was left blank in #2.
The connection also gives a shell prompt.
Any file that is created under the newly added "remote" folder shall be created physically under the remote folder. "Save" to apply code changes.
The plugins (C/++, Python etc) that you have installed in your WS works as usual,
while you code.
My workstation is Linux, so there was no need to install any ssh client. If you
are on Windows, putty might work. I have not tried it.. but I guess it would work,
since I see "putty" mentioned in the configuration page of #2.
sorry for this
but in python spidev its not working as it should be i have to change sending bytes .but in raspberry pi its working without any change. and according to documents of lora chip its half-duplex.