Getting back to RIO AHRS install after a loooong time

Hi mjepson. When you say "(the latest version from git.drogon.net)", do you mean the very latest version of wiringpi, as in 2.25 or thereabouts, or a new copy of version 1.0? I'm just curious given the direction above from opal to only use 1.0 and not use the latest version.

Not that it's a problem for me, but sticking with 1.0 won't work for people with one of the new Pi 2's as Broadcom have changed the address in memory where IO is situated. For those people the latest wiringpi is definitely required.

Hi Rob,

I now have version 2.26 (at least, that's what it tells me when I run "gpio -v").

I just pulled it from "git clone git://git.drogon.net/wiringPi", which should always be the latest version, I think.

Interesting: and, using this version of wiringPi, you now have the 1 Hz flashing green LED (rather than 4 Hz) and non-zero values out of rioboard_test?

I have a 4Hz flashing light (which is good) and values are coming in with rioboard_test.

Ah, yes, sorry, 4 Hz is what I meant.

Quote: "you lucky, lucky, b*stard" :-).

opal: help! What else can I try?

Does "gpio -v" work for you, Rob? That was my queue to find a way to install LibWiringPi, since it gave me a 'command not found'.

Oh, no it doesn't, good call that man. Looks like the install didn't work after all. I'll do what you did...

Well, gpio -v shows that wiringPi is now installed (version 2.25, which is what gets packaged for my distribution) but I still get all zeros out of /rioboard/rioboard_test. It is no longer producing a log file with errors in it, though, so I'm flying a bit blind.

shows that rioboard_d is running?

Basically what I did (and what showed me that the command gpio was missing) was run the lines in /riofiles/startup_script/rioboard_d one by one by hand. Just to see whether they work. Maybe you can find something doing that?

How strange. I just restarted the device to double check that the daemon is running as you suggested and I am now getting a 4 Hz flash from it and yes, it is running. Hmmm. Maybe it needed a power-off rather than a reboot (which is what I did last night)? Anyway, all now working.

Thanks very much for your "community" support mjepson. :-)