![]() It's just a lot less intuitive (JMRI) when you get to that level - and I say this for someone who has been writing computer programs since I was 11 years old, back in 1977 when the TRS-80 came out. Everything was the same, in fact, except the software - same Locoobuffer interface, same laptop computer I was trying to use JMRI on. And same hardware - no false block detections. Well, one weekend I went ove,r he had downloaded RR&Co and in a week had the trolley line automated like he wanted - me the computer guy couldn't get it working in JMRI but he, a lawyer, got it working in RR&Co. And still it never reall worked - spurious occupancy sensing was the biggest problem, and it's always bneen blamed on the Digitrax hardware. I could never get the script to work, and making a mistake in drawing the track plan meant I had to pretty much just start all over, erasing back to my mistake in block numbering and then finishing it caused all sorts of weird problems. I guess I lost some faith in JMRI when I tried to help a friend automate a trolley loop on his layout with it. ![]() It seems a lot easier to do this via RocRail than with JMRI. Possibly my other idea of a small Bluetooth add-on to any smartphone so you have the touch screen to turn functions on/off or select a loco, but an actual knob to run to control the train. The HTML interface is allowing me to experiment with my idea of a simple universal throttle using an Arduino. ![]() are intriquing to me because it's not written in Java, and writing scripts for it doesn't need Jython which if it isn't the world's worst scripting langues is in a close race for it. Their panel and also their simple HTML web interface for smartphones etc. I am giving it a shot, at least as far as using the virtual CTC panel portion - I don't think their decoder programming facilities are as good as JMRI (but I rarely use JMRO for that - I use all the same decoders so it's not hard to memorize the settings I use for all locos).
0 Comments
Leave a Reply. |