Cumulus Support • MX 3043 Issues - Page 2

Page 2 of 4

Re: MX 3043 Issues

Posted: Sun 29 Jan 2017 5:40 pm

by rogerthn

vagos wrote: Done!!!, is there a way to identify if I have successfully managed to create a new screen? If I press Ctrl+A+D there is no notification. It just works.

screen will tell you if it fails to create a new screen

I do agree with Steve, /boot is NOT a good place for any application!
I do use /home/pi/CumulusMX and I start it at boot as below.
The script /home/pi/CumulusMX/start_CumulusMX.sh as below.

Code: Select all

#!/bin/bash
/bin/sleep 69
cd /home/pi/CumulusMX
sudo mono CumulusMX.exe

Do not forget

Code: Select all

chmod +x /home/pi/start_CumulusMX.sh

Then a crontab entry

Code: Select all

@reboot /usr/bin/screen -fa -d -m -S Cumulus $HOME/start_CumulusMX.sh

Re: MX 3043 Issues

Posted: Sun 29 Jan 2017 5:56 pm

by vagos

If I insert the sd card to win10 environment I can only "see" boot folder.

Nothing else. Is there a way of browsing the other folders inside sd card?

Re: MX 3043 Issues

Posted: Sun 29 Jan 2017 6:48 pm

by rogerthn

vagos wrote:If I insert the sd card to win10 environment I can only "see" boot folder.

Nothing else. Is there a way of browsing the other folders inside sd card?

Wintendo can only see the first partition on "removables"

Try ftp software with sftp support, FileZilla used to be my choice while other prefere WinSCP.
Once installed connect to the Raspberry IP using sftp

Edit:
OR
Move all CumulusMX-files from /boot to /home/pi/CumulusMX

Re: MX 3043 Issues

Posted: Wed 01 Feb 2017 6:57 am

by vagos

Thanks again, since during week working days my free time is very limited I have not reported back.

After 2 days of continuous operation I have managed to get this error from 16:00 yesterday.

error reading data from station it may need reseting

Cumulus is normaly reporting but it cannot get data from station.

Since I'm currently away, I have only rebooted Rpi and my girlfriend removed and installed back the usb cable.

With no luck unfortunately. Any way to overcome this issue? Anything I can do with Cumulus Dashboard?

Re: MX 3043 Issues

Posted: Wed 01 Feb 2017 7:14 am

by vagos

I have rebooted the station in total.

Works again.

I have also enabled

"Synchronise Fine Offset reads"

Work around for Fine Offset console USB lockup problem

Question: The clock on the station has anything to do with Cumulus logging time stamp?

I'll revert back with feedback

Re: MX 3043 Issues

Posted: Wed 01 Feb 2017 11:16 am

by mcrossley

vagos wrote:Question: The clock on the station has anything to do with Cumulus logging time stamp?

No.

Re: MX 3043 Issues

Posted: Sat 04 Feb 2017 12:43 pm

by vagos

rogerthn wrote:
vagos wrote: Done!!!, is there a way to identify if I have successfully managed to create a new screen? If I press Ctrl+A+D there is no notification. It just works.
screen will tell you if it fails to create a new screen

I do agree with Steve, /boot is NOT a good place for any application!
I do use /home/pi/CumulusMX and I start it at boot as below.
The script /home/pi/CumulusMX/start_CumulusMX.sh as below.
Code: Select all
#!/bin/bash
/bin/sleep 69
cd /home/pi/CumulusMX
sudo mono CumulusMX.exe
Do not forget
Code: Select all
chmod +x /home/pi/start_CumulusMX.sh
Then a crontab entry
Code: Select all
@reboot /usr/bin/screen -fa -d -m -S Cumulus $HOME/start_CumulusMX.sh

With some reading and your instructions I have managed to create a script file but the crontab entry doesnt seem to work correctly.

If I call the script it works. Could you please clarify what -fa -d -m means?

I assume -d -m -S creates a new screen in detached mode. What about -fa?

I have noticed that the service runs for a little but then stops. (No active connection to the dashboard)

Thanks again

Re: MX 3043 Issues

Posted: Sat 04 Feb 2017 4:34 pm

by rogerthn

From

Code: Select all

man screen

-f, -fn, and -fa turns flow-control on, off, or "automatic switching mode". i.e. -fa automatic switching mode
-d -m Start screen in "detached" mode.

Maybe you could try to reboot, within 1 minute logon and do

Code: Select all

screen -r Cumulus

Re: MX 3043 Issues

Posted: Sat 04 Feb 2017 6:34 pm

by vagos

ok thnx,

why if I call the script it runs but when I run it via crontab entry it doesn't?

Is there anything else to do?

Just to note: that I have enabled auto login via raspi-config. Does it do any harm to the crontab?

Another note is that I have a clear installation of jessie lite, the CumulusMx is now on Pi folder, with static ip, auto user login, script enabled and given su access.

Re: MX 3043 Issues

Posted: Sat 04 Feb 2017 7:32 pm

by rogerthn

Did you try screen -r Cumulus within a minute?
You could try to modify start_CumulusMX.sh as below to check how long it is running

Code: Select all

#!/bin/bash
echo staring $(date) > /home/pi/start_CumulusMX.log
/bin/sleep 69
echo Slept $(date) >> /home/pi/start_CumulusMX.log
cd /home/pi/CumulusMX
echo cd done $(date) >> /home/pi/start_CumulusMX.log
sudo mono CumulusMX.exe

btw, you can also try screen -r Cumulus after more than one minute
The screen should be there

Re: MX 3043 Issues

Posted: Sun 05 Feb 2017 10:32 am

by vagos

Recaping

1)My installed directory is home/pi and then CumulusMX without any folder (made all the proper corrections from your suggested code

2)I have created a cumu.sh file as script file

inside i have pasted

Code: Select all

#!/bin/bash
echo staring $(date) > /home/pi/start_CumulusMX.log
/bin/sleep 20
echo Slept $(date) >> /home/pi/start_CumulusMX.log
cd /home/pi/
echo cd done $(date) >> /home/pi/start_CumulusMX.log
sudo mono CumulusMX.exe

the file start_CumulusMX.log ok, what it logs?

3) By running the script only

Code: Select all

sudo ./cumu.sh

its working but without logging

4) Getting the entry inside crontab

Code: Select all

sudo nano /etc/rc.local

and then pasting your code before return (0)

Code: Select all

@reboot /usr/bin/screen -fa -d -m -S Cumulus $HOME/cumu.sh

Results.

After reboot the script doesnt run. Neither

Code: Select all

screen -r Cumulus

returns a screen.

Thats my progress up to now

Re: MX 3043 Issues

Posted: Sun 05 Feb 2017 12:27 pm

by rogerthn

vagos wrote:Recaping
.
.
.
Code: Select all
sudo nano /etc/rc.local
and then pasting your code before return (0)
Code: Select all
@reboot /usr/bin/screen -fa -d -m -S Cumulus $HOME/cumu.sh
Results.

After reboot the script doesnt run. Neither
Code: Select all
screen -r Cumulus
returns a screen.

Thats my progress up to now

aha
Remove

Code: Select all

@reboot /usr/bin/screen -fa -d -m -S Cumulus $HOME/cumu.sh

from /etc/rc.local
Then as user pi

Code: Select all

crontab -e

and paste

Code: Select all

@reboot /usr/bin/screen -fa -d -m -S Cumulus $HOME/cumu.sh

/etc/rc.local

Re: MX 3043 Issues

Posted: Sun 05 Feb 2017 1:49 pm

by vagos

Deleted the entry from

Code: Select all

sudo nano /etc/rc.local

geting the entry

Code: Select all

@reboot /usr/bin/screen -fa -d -m -S Cumulus $HOME/cumu.sh

to

Code: Select all

sudo nano /etc/crontab -e

same thing. Nothing happens

, again no screen to recover

Code: Select all

screen -r Cumulus

Re: MX 3043 Issues

Posted: Sun 05 Feb 2017 4:44 pm

by jlmr731

vagos wrote:Deleted the entry from
Code: Select all
sudo nano /etc/rc.local
geting the entry
Code: Select all
@reboot /usr/bin/screen -fa -d -m -S Cumulus $HOME/cumu.sh
to
Code: Select all
sudo nano /etc/crontab -e
same thing. Nothing happens , again no screen to recover
Code: Select all
screen -r Cumulus

crontab is a application.
when you did

Code: Select all

sudo nano /etc/crontab -e

you made a file named "crontab" in the /etc directory or edited it if it was already there

Try as your normal user log in run

Code: Select all

crontab -e

then it will bring you into the crontab editor and then enter your commands you need to run

Re: MX 3043 Issues

Posted: Mon 06 Feb 2017 8:17 pm

by vagos

Thank you Jeff.

Well

Code: Select all

sudo crontab -e

inside there i got the attached image
Ctrl+O
Ctrl+X

rebooting and nothing again.

PS: Small correction the path is $HOME/pi/cumu.sh

corrected on the crotab -e but still doesnt work