@rmoore I started off figuring out the GPIO pins on the bare Raspberry Pi, and once you get your head around that, moving to the Unipi is the next logical step. I did'nt use this article, but it explains just about all that you need.

http://makezine.com/projects/tutorial-raspberry-pi-gpio-pins-and-python/

The Evok "platform" can be used as well, and I use it via the restful calls for setting some of the relays.

If you've not got a Pi already, get a Pi and try the small tutorial above. After that it's straight forward enough.

Merv.

Hi, I have a M20x that I want to replace with a new device, is the M203 a direct swap, just a newer model number? I use a custom Python program that reads and sets using requests. Some of my procedures:

def read_button(button):
    try:
        Status = urllib.request.urlopen("http://" + myself + "/rest/di/" + button).read()
        jsondata = json.loads(Status.decode("utf-8"))
        x = jsondata["value"]
    except Exception as e:
        # print('Read button fail, no button called',button)
        x = True
    return x


def set_relay(circuit, onoff):
    data = dict(value=onoff)
    url = "http://" + myself + "/rest/relay/" + circuit + "/"
    content = requests.post(url, data=data, allow_redirects=True)

Should I expect that all the relays, di, do, ai, ao access will be the same? I guess what I'm asking is, should I expect that my program will run the same on the M203 as it did on the M20x?

And separately, if I changed to the Patron devices, would the evok system be accessable in the same way as I've accessed it with my python code? Would it be an easy change over?

Thanks!
Merv

@tomas_hora Hi,
I did a fresh Rasbian install, got the neuron online, did a
git clone http.....
set the permissions (as per the GIT page)
started it up.
and....

PERFECT!

I have my python monitoring program starting automatically as a service, and I had to put a little sleep command in it on start as it was trying to run before EVOK started. Runs great.

Many thanks.
Merv.

That's brilliant.
I have some new micro SD cards on order, I'll do a clean new install and test once they arrive.

Merv.

This is causing me a problem too.....

I've tried setting the SysLogLevel parameter to a few different values, it's currently set to "emerg" which should report almost nothing.

The lines (as above) are now being written to daemon.log (as before) but now also into the syslog file.

Still puzzled...

The log entries look as follows:
Feb 13 08:19:23 VacuumPLC evok[425]: [I 170213 08:19:23 web:1971] 200 GET /rest/relay/2_01/ (::1) 1.81ms
Feb 13 08:19:24 VacuumPLC evok[425]: [I 170213 08:19:24 web:1971] 200 GET /rest/ai/1_01 (::1) 1.81ms
Feb 13 08:19:24 VacuumPLC evok[425]: [I 170213 08:19:24 web:1971] 200 GET /rest/relay/2_01/ (::1) 1.92ms
Feb 13 08:19:24 VacuumPLC evok[425]: [I 170213 08:19:24 web:1971] 200 GET /rest/relay/2_02/ (::1) 1.76ms
Feb 13 08:19:24 VacuumPLC evok[425]: [I 170213 08:19:24 web:1971] 200 GET /rest/relay/2_03/ (::1) 1.81ms
Feb 13 08:19:24 VacuumPLC evok[425]: [I 170213 08:19:24 web:1971] 200 GET /rest/relay/2_04/ (::1) 1.90ms
Feb 13 08:19:24 VacuumPLC evok[425]: [I 170213 08:19:24 web:1971] 200 GET /rest/relay/2_05/ (::1) 1.80ms
Feb 13 08:19:24 VacuumPLC evok[425]: [I 170213 08:19:24 web:1971] 200 GET /rest/relay/2_06/ (::1) 1.81ms
Feb 13 08:19:24 VacuumPLC evok[425]: [I 170213 08:19:24 web:1971] 200 GET /rest/relay/2_02/ (::1) 1.93ms
Feb 13 08:19:25 VacuumPLC evok[425]: [I 170213 08:19:25 web:1971] 200 GET /rest/ai/1_01 (::1) 1.79ms

The cause of them is my python program that is monitoring the status of a vacuum sensor, and checking what pumps are on and off, and switching pumps on and off. but, while I want to keep checking the status of the relays, I dont need to be creating so much debug activity. I'll take a look at the links you sent me.
Merv.

Hi,

I'm getting a lot of log entries in /var/log/debug and /var/log/daemon.log files. They are getting huge, and not rolling over to make it easy to delete the older files. Can I reduce the level of logging from evok?

Thanks.
Merv.

It was similar for me, mine ran fine for a few weeks before I got problems.

I meant to post here. I am running the latest version of Evok on the small Neuron and its doing fine. My python application is running for 4 days now with no hiccups.

I only use the Evok gui screen to verify what my application is doing (as well as looking at the LED's.

Merv.

It may be worth a try, cover the patch leads in tinfoil. Worked for me!