Episode 16, Part 1 of JMRI via Bluetooth serial.

[@markh4531]

Excellent video. Looks like a fun challenge. Can’t wait to see the next update.

[@FunWithHOScaleStuff]

Hi Mark and thank you for watching. I'm anxious to present a working conclusion to this effort but as you probably know, things don't always turn out as we plan. Anyway, my next video will be about how I pair the bluetooth module with the PC. I'm keeping my fingers crossed that it works out. ;-)

[@Christiane069]

Ooh! I am learning so much from your channel. Where have you been till now. I can't wait for the next video.

[@FunWithHOScaleStuff]

You're very kind to write that. I hope you enjoy the upcoming videos documenting my effort to connect JMRI to the NCE Power Cab via Bluetooth. I'm hoping that it works ;-)

[@Christiane069]

Just one quik question. You are using Arduino control for your set up if I understand correctly. So, why are you using NCE, and not the Arduino system. Not possible, or too complex? How about a good challenge!@@FunWithHOScaleStuff

[@FunWithHOScaleStuff]

I apologize for the late response. KZbin is supposed to notify me and never did. That is an excellent question. I am sorry for any confusion. The Arduino work for the Throttle/Controller was a project I started about two years ago. I wanted to share what I found so far but it the development time is so long that it wasn't prudent to depend on that project reaching a point where I could use it to actually run my locomotives and accessories. I bought the NCE Power Cab starter set in order to stress test my other project of the DCC Monitor. That code requires some magical interrupt and data stack management. :-) Both of these projects are on currently on hold. I'm very willing to share what I've found so far working on them if you are interested. I could write a book with all of that. :-) Thank you for your interest and for the comment.

[@mike9repeating]

That sounds like a really interesting project your going to start. Good luck!

[@FunWithHOScaleStuff]

Thanks Mike. I'm excited about using the Bluetooth. It is entirely new to me. I'll try to include some of the gritty details for the more techy folks but keep the discussion as straight forward as possible so any young folks watching this can gain an understanding of how I tried to do this one.

[@Christiane069]

Well. Thanks for the response. I can't wait for the book. I will buy the first 10 copies if it can help you going. Yes, I am very interested about any info on this project of yours. I am not new to coding. I stated long time ago (I mean some time ago) with COBOL and then BASIC , but of course it's been a will.

[@FunWithHOScaleStuff]

Almost ready to post part two of the JMRI via Bluetooth Serial series. It has become rather longwinded and I propose that this will substitute for any book in length. Thanks for watching. I hope you continue to enjoy the content I post. 👍

[@Christiane069]

OK. It is very nice talking to you. You are a very nice man. Looking of any of you videos.@@FunWithHOScaleStuff

[@mobahartenholm9289]

Hello, I did subscribe your channel month ago, but I lost it. I can't remember the name of your channel but I find it today, great surprise and I'm very lucky about that. Thats a very interesting projekt, can't wait to see your progress. Regards from germany - Rainer

[@FunWithHOScaleStuff]

Thank you for the kind response and welcome back. I'm pleased that you share my interest in this hobby. I plan to make a bluetooth connection to the Arduino Uno in the very next episode and I will share as much detail about the bluetooth module and its connection as possible.

[@nedmerrill5705]

Do you need the protocol for what you want to do? Isn't it all under JMRI, or within the NCE domain? Isn't Powercab the NCE starter DCC system with only two jacks, the left one for the Powercab and the right one for the slave? Mine only has two, not 4. You have an interesting project on hand and are speaking my language...

[@FunWithHOScaleStuff]

Thanks for that kind comment. About the protocol, the JMRI does everything correctly for NCE to understand and execute the user commands. But that information is wrapped in a local NCE protocol (handshaking) that determines when the JMRI information is permitted onto the RS485 network. That network consists of up to three additional cab controllers and each one must have a different address. Each controller must buffer it's NCE command data until it is addressed by the NCE master controller. From what I've seen at this time is that the addresses are issued one at a time on the RS485 lines and each one is followed by a period of tri-state (released from transmit) and evidently waiting to see if there is a response. So the Arduino I'm using will need to be that addressable device and must buffer JMRI information until it is addressed. Once the Arduino sees its address I plan to dump the JMRI information that is buffered (if any) onto the RS485 bus. At least this is the expectation/plan for now. Whether this project is successful... well we'll see, eh? Stay tuned. ;-)