So I am ok with having Pi as an option, the straight to PC is super straightforward so easy to document. I advocated originally for it as base as the Pi is an unnecessary expense if you have a laptop but the Pi is the easiest self contained CS so, long answer, but I have no problem making it an option rather then base and providing instructions for both. Dennis your question is valid but again we have to pick something. I think makes the most sense to use pi4 as currentits the current version and the image that Sumner agreed to flash. Of course you could use a 3 or a 2 or not have one at all but the point was we have to pick something as discussed before. If we don't then it becomes complex and confusing. I personally run it on a pi3b. And certainly if others want to document all the different variations and possibilities then we can add to documentation but I think important we stick to latest and one setup as base. I fully agree on the stylistic and writing style comments. It could use editing by a good technical writer which I am not but I wanted to get us started.
I agree that JMRI on a PC should be the base but also think that it should be made very clear that if a person has a spare keyboard/mouse and monitor spending $35 on the Pi and $10 on a pre-loaded SD card will get them a plug and play system if they also get the Arduino with the pre-loaded Sketch. They don't have to be computer or electronics literate at all. Connect a power supply to the shield and connect the Arduino to the Pi with a simple cable and they are in business. I feel this would really appeal to a large number of people who would be very interested in DCC++ except for multiple steps loading software, dealing with com ports and cutting a trace is just too much for them. I feel spending $45 more for a true plug and play system wouldn't be much of a deterrent to them. Getting JMRI up and running probably would be fairly easy for a large number also so feel it could remain the very base system they could choose from. Most of you guys are really competent when it comes to anything to do with a computer. Sometimes it is hard to remember that for some just mention something like "find the com port you need" can be very intimidating when there can be a number of steps involved depending on their operating system and such. Keith I think what you have put up is a good basis to work from and things need to start somewhere and I feel it is a good start. Maybe a couple others could use it as a basis and submit their ideas. Also the cards will be $10 instead of the $15 you have listed. I'll have a link today or tomorrow to how to get the image card. I'm sending one out tomorrow in fact. On the Pi, I'd just say that any Pi from 3 onward will work as Dennis mentioned. Sumner
I understand that. My comment was to let new users know you do not have to purchase the latest RPi if they already have an older RPi.
I've started on the readme.md files in the repositories and also begun on the Wiki. I am going to use the ideas shared by @Keith Ledbetter . I hope others suggest ideas, outlines, bullet lists, paragraphs, etc. You can post here or actually edit the project. We have 3 places to provide marketing, help, and reference material; readme.md files, Wiki pages, and the DCC-EX website. Currently, the readme files are a going to be used as an overview of that repository and an outline of how to submit code. The Wiki will be a more detailed description of the project and the quick start for our two systems. The web page will be for the detailed DCC++ user manual and links to other documents and sections. We may find we need the manual to be in the Wiki instead or even in something like a PDF document (or all of the above?) Here is the start of the web page. All of these different document types are hosted on Github and all of it is manageable as a project with commits and pull requests just like the code. https://dcc-ex.github.io/
May I add my none technical two pennies worth [British slang for a small contribution - usually written twopenn'orth]? I am on here most days usually just reading what is being discussed as I am not a techie type. The key element is keeping the project simple. It's been said many times [first time about 2 weeks ago] and is in my view paramount to the success of take-up. To the newbie, it will be imperative that the system is as close to plug and play as you can make it possible. Even then there are some elements of the basic configuration that I am sure many [well, ok ME] might struggle with and without a support system, it does feel a little daunting. I have been following the thread of buying and building the UNO / Motor Shield / PSU / JMRI system in an attempt to convert that into a simple flow diagram with images for the new arrivals to the subject to follow. Although in an early stage - it looks like this - my hope is that it will eventually be helpful to many. R-
posted some feedback on your commits, there are a few minor issues (name misspelling being the biggest!)
Agreed on keeping is simple and you will be a good filter for that @Roger Beschizza. You can always look at updates and say, "I have no idea what that page was trying to say", etc. And we will work on it. And to keep with standards, there are things Github folks look for called "default community health files". Information should either be repeated there or at least placed there. There are different files like CODE_OF_CONDUCT, CONTRIBUTING, SUPPORT, etc. that people look for to see how to do one of those things. So I've place a CONTRIBUTING.md file in a new folder called "docs" off of master. Not only can you read the file, but when you do something like issue a pull request, a menu shows up because it sees that default file and gives a contributor a link like "Help on how to contribute".
For some reason GitHub didn't send email notices on the comments... we should move to using the PR instead going forward so we can capture comments more easily... Comments can be found on commit https://github.com/DCC-EX/dcc-ex.github.io/commit/78b74a4ee785025502639535ab6c982acb9f41d9
My idea, when I get everything up and running [Deo Volente] is to affix the two boards in their conjoined state to the side of the layout. This will enable easy attachment to the current DCC bus - but not the programming track - with the USB A-B cable and a power cable for the shield. The programming track will have a plug and socket arrangement. R-
Well I sent the first card out today and the shipping is $4.00 (has to go parcel) and add that to the cost of the card and there isn't much left over for donations to the train forum and to JMRI so I went from $10 to $12. That way I can donate about $2 to both the train forum and to JMRI for each card that is sent. Here is a link to the page with "Simple $35 Computer Running JMRI for the Train Room" information and how to put the Pi together and how to get the SD card with the image file on it.... http://1fatgmc.com/RailRoad/DCC/page-2.html If anyone sees errors please point them out. If you still wanted you could link to that page or someone could google 1fatgmc.com and find the info there, Sumner
I like it, could I add to your page and the paypal link a I like it. Could I just add the Uno Shield setup to your page and then have the paypal point to my address for the Uno/Shield combination. Any particular format make it easier for you? This is certainly Wiki worthy in my opinion rather then hosting on your site just for sake of not being singly dependent on you/your site.
in your document linked you are discussing the controller. You should reference JMRI there Also on p.2 you reference Identify and assemble the items required Arduino Uno Arduino Motor Shield USB A - B cable Power cable - This should say 15-18 V Power Supply to provide track power Locate and download the DCC++ Base station program [called a sketch] DCC++ Controller sketch - should be JMRI program DCC++ IDE [a program the techies use and is needed by the Arduino] - this should say Arduino IDE, DCC++ is the sketch mentioned in 2.1, the IDE compiles the sketch and loads the UNO through the USB A-B cable mentioned above in 1.3.
That would work and also I don't mind the page I did being in multiple places for the reasons you stated although I think right now I've got the Domain name and server fees paid out 2-4 years at this point. At 76 you never know exactly what the future holds for you though. I'll send you a PM in a bit about some details. ===================================================== On your post above.... "4. Power cable - This should say 15-18 V Power Supply to provide track power" I wonder if that should maybe be scale dependent. I'm N and started with 14-15 V and was having some problems (can't remember what) and starting seeing posts about using 12 V for N. I switched to that and have been using it, not that I think the higher voltage was the cause of my problem, but just did it based on what I had read a few times. I'd maybe go back up in power if some others would add feedback on this. Anyone?? Sumner
15V seems to work for most but I run a 16V on my n scale, have seen 12V run fine for some, In HO I would run 18V personally and in my G Scale I run 20V. The best thing honestly is probably for us to recommend is something like https://www.amazon.com/ALITOVE-Univ...ersal+power+adapter+20V&qid=1583260141&sr=8-7 so folks can adjust but I think starting with 15V for N and HO is the right starting point and folks can tweak from there.
Thanks guys I think I'll put the 14 volt power supply back on. I've had problems programming a couple decoders but seems like that goes away if the pickups are cleaned. I'd think the little higher voltage might help with that??? Sumner
