Raspberry Pi 3 in the House... and Running JMRI!

[C855B]

Aaaaaaaaaaaaand... you're already over my head. My Linux knowledge these days is limited to "apt-get" installs from pre-linked binaries in public repositories. (Not that bad, really, but one of the first things I did when retiring is purge my brain of Linux detritus. Or at least it seemed that way.)

Speaking of Linux expertise, when is one of our resident Linux nerds going to step up here and give us a step-by-step on how to start JMRI on boot default user login?

[John]

Speaking of Linux expertise, when is one of our resident Linux nerds going to step up here and give us a step-by-step on how to start JMRI on boot default user login?

That shouldn't be too hard ..

http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui

[C855B]

Thanks, John. Had never used the '@' operator in that context, so there you go.

[Iain]

So, I admit, I've sort of been staying out of things because I tend to do stuff on the command line, and don't even know how to use many of the gui tools y'all are looking for (or even that they exist, for that matter)

[eric220]

After a wipe and clean install, followed by these directions: http://4dc5.com/2012/06/12/setting-up-vnc-on-raspberry-pi-for-mac-access/



Success! That is a shot of it running headless under the layout.  Now I'm just working on getting JMRI to load on boot.  That should just about do it!

[C855B]

 

[eric220]

Two and a half hours later... No launch on boot. Time for a stiff drink.

I don't understand what's going on. I made a script that launches Panel Pro, put it in init.d, and ran update-rc.d. If I run the script manually, it launches Panel Pro. On boot, bupkis.

I must say this whole experience has led me to develop some very strong opinions about Linux.

[C855B]

Yeah, Linux can really suck, and searching online for hints or even a little bit of assistance is nothing less than infuriating. The problem I think you're having is you are trying to launch a JAVA app which lives in the user space, not the root. init.d is trying to run it as a privileged root application, when you launch it manually you are running it as a "mere" user.

John gave the clue above:

That shouldn't be too hard ..

http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui

Scroll down to "Setting An Application / Your Application To Automatically Run In The GUI". You need to put your startup in .profile, which is the user init file. (.profile normally doesn't show on the standard file system GUI.) Since running the GUI automatically logs into the "pi" user - unless you changed that - it should start it up after boot is complete.

At least in theory... I haven't tried auto-running yet. But I think John's hint should work.

[eric220]

And someone who knows what they're doing to the rescue. Winning.

JMRI is officially launching on start! The Pi is headed back to the layout, and Linux can go... Well, I guess the next two pages of what I have to say might hurt someone's feelings, so I'll leave it alone.

[C855B]

Oh, trust me, ten years of sysadmin on a couple of dozen Linux servers taught me everything I needed to know about mouse aerodynamics and monitor impact testing.

[eric220]

Oh, trust me, ten years of sysadmin on a couple of dozen Linux servers taught me everything I needed to know about mouse aerodynamics and monitor impact testing.

FTFW

[mighalpern]

Part of my weekend was getting the Pi installed in the case and then putting a command line to invert the screen, seems that the case has slots to mount on the wall but that flips the monitor 180 and so everything is upside down.  Anyway checked for updates and upgrades and entered the command line and everything fires right up.  Touch screen is right on the money.


thanks to Eric 220, JMRI withrottle and panel pro boot up to the screen and are ready to go.
Now unfortunately,  I can run JMRI and hook up the PR3 and get my phone to talk to JMRI, but I can not run a train.  If I press a function key I see it on JMRI, the PR3 "stat" light blinks, but no go on the layout, I can see it on my phone throttle that, that function key is being pressed.  My digitrax throttle all work.  so, any ideas what I can check for.  Running JMRI version 4.4 R1

[eric220]

Given my recent experiences, I'd suggest liberal application of a large blunt object.

One thought, is there a conflict between the port running the new monitor and the one driving the PR3? Check the port in JMRI preferences.

As another troubleshooting step, if you bring up the loconet monitor, do you see messages from the Digitrax throttles, say when you change speed?

[mighalpern]

hey Eric,  i am actually having issues with the port selection.
One thing I did do is use the test exe file and brought up a throttle and it worked fine thru JMRI.  so I saved that as a default throttle, but it is not working.
The "stat' light is blinking every time i command something in either JMRI or the phone, but nothing is getting to the loco's.  Been thinking that i should reload the noobs and raspbian and start over.  otherwise I can figure this out