I tried jumping the gun and running without uncommenting the RX_INVERTED line in ln-config. Glad I came to my senses and watched your video thoroughly! Thanks Hans, the sky is the limit with the loconet interface!
That would be like talking French to an American ;-) The reason I decided to use the same logic on RxD and TxD is that the interface can be used on a hardware serial port as well, which is allowed by the LocoNet specification and less strenuous on the hardware. And it is more inline with good design practice anyway.
As an NCE user I have watched, with great interest, how you have used LocoNet in so many ways. I can certainly see why you feel that it is a versatile networking system. I’ve even thought of switching to Digitrax for my layout. In this video you have tweaked my interest in using LocoNet with NCE. I look forward to more on this in the future. I must say that I also appreciate these videos every two weeks. I enjoy watching them on Sunday morning. Thanks Hans!
Rob, I was using an NCE system and I have switch to a loconet compatible system. But I have see a few club layout using NCE for DCC train control and a loconet control loop for accessories and block detection, ctc panel and signal control. Iott do have a dcc interface you can use as a gateway with your current system. And still use a loconet control loop for different automation. You do have some options with your current command station.
@@pierrelambert446 Thanks for the reply. I do have the IoTT DCC interface awaiting installation. Like many others, I am also waiting for the Green Hat. I'm hoping to put them all together soon on my layout. The modular club I belong to uses Digitrax and I have thought about getting one of Han's LocoNet interfaces just to play with. I might try it on my layout too. BTW, that was your N-scale outfit in Han's video wasn't it? I'm also N-scale but nowhere near the scenery stage. So far just track although I have test run a few engines to make sure things are right. Just need that Green Hat to get my servo operated turnouts going.
@@robleathley6024 yes it is part of my layout. Only ⅓ of my layout have a good scenery. ⅔ is mostly like your. Just completed a house move and now I am looking to enlarge my layout. Until then, I am experimenting with Iott automation. I have activated block detection two months ago and I am experimenting with signals using the NeoPixel chain with s2811 chips to drive already build signals from custom signals system. I am now using tortoises motor for my switch and I won’t change those. But as soon as the new green hat is released I will order one. I already have a sg90 servo waiting. I am looking to test it out for a crossing barrier automation. My next layout will be designed with a lot off Iott devices.
@@pierrelambert446 I am about to start building my signal system. I'm using block detectors from MERG that will attach to a Yellow Hat. Like you, a string of 2811 activated 0603 RGB LEDs will be used for the actual signal. Hans showed how to use RGB LEDs with a small interface board in a video a while back. As I have a 3D printer, I'm going to try making my own signal masts. Found some designs on Thingiverse that look good. We'll have to see how it turns out.
It is almost an year now that I maintained a two week rhythm. Kind of a positive side effect of the pandemic, as I am less traveling for business. We will see how long I can go on with every two weeks once things are picking up again ;-)
Like rob I can’t wait the new video you put together every other week. I love the flexibility of your system and all the gateway build to the different model rail road standard and industry standard. Every new version of the Iott software bring many new functionality. As for your hardware it is working flawlessly since 4 months now. I am progressing too slowly to my taste on my layout project.But Iott will be an the core of my layout automation. One of the new futur features I am looking forward to use is the direct communication with JMRI without the need of a loco buffer. As my pc desk is located at the other end of my layout room.
Hello Hans ... I have one of your LocoNet Interface boards on the way, and am looking forward to working with my Digitrax system connected to our Arduinos. I have, however, had trouble finding the Arduino sketch you show in this video to control the NANOs LED via the button. I would also very much appreciate a copy of any other sketches you may be willing share for this interface. Thank you.
Check at 4;20 into the video. Once you have the LocoNet library installed in your Arduino IDE, there is a LocoNet entry in the example section. I am using the LocoNet Control Panel example in the video. It should work pretty much "out of the box".
Hans, thank you for the video. I have a DCC++ layout and want to integrate Loconet throttles into the layout. do you know what the setup on the IoTT stick and JMRI to have them talk to each other like they are on the same system?
First you need to make sure you are using a DCC++ version that supports LocoNet. Originally this was not the case with DCC++, but I found one article here www.clubncaldes.com/2017/04/cheapest-dcc-command-station-with.html where soembody added LocoNet, and the code is available on Github. I believe that a newer DCC++ implementation for the ESP32 also supports LocoNet, but I am not sure about the status of that project. Once your DCC++ command station supports LocoNet, you can use the Stick to connect to JMRI via lbServer, or you can use a LocoBuffer USB to do the same. Your system should then be a real LocoNet system, just with a 3rd party command station, but all typical LocoNet components should run on it.
No, the 12V supply is to make it Loconet Master. That is used for a stand alone Loconet without Central Unit. If you connect a throttle to an active Loconet, it is powered from wires 1 and 6, which is DC (Loconet T) or DCC (Loconet B) but with limited voltage and current.
As specified in ln_config.h the Mega requires pin 48 as Rx pin. The Tx pin can be set as you wish. Also note that both, Rx and Tx need to be in inverted mode. Check the notes in the ln_config.h file.
I tried jumping the gun and running without uncommenting the RX_INVERTED line in ln-config. Glad I came to my senses and watched your video thoroughly! Thanks Hans, the sky is the limit with the loconet interface!
That would be like talking French to an American ;-) The reason I decided to use the same logic on RxD and TxD is that the interface can be used on a hardware serial port as well, which is allowed by the LocoNet specification and less strenuous on the hardware. And it is more inline with good design practice anyway.
As an NCE user I have watched, with great interest, how you have used LocoNet in so many ways. I can certainly see why you feel that it is a versatile networking system. I’ve even thought of switching to Digitrax for my layout. In this video you have tweaked my interest in using LocoNet with NCE. I look forward to more on this in the future.
I must say that I also appreciate these videos every two weeks. I enjoy watching them on Sunday morning. Thanks Hans!
Rob, I was using an NCE system and I have switch to a loconet compatible system. But I have see a few club layout using NCE for DCC train control and a loconet control loop for accessories and block detection, ctc panel and signal control. Iott do have a dcc interface you can use as a gateway with your current system. And still use a loconet control loop for different automation. You do have some options with your current command station.
@@pierrelambert446 Thanks for the reply. I do have the IoTT DCC interface awaiting installation. Like many others, I am also waiting for the Green Hat. I'm hoping to put them all together soon on my layout. The modular club I belong to uses Digitrax and I have thought about getting one of Han's LocoNet interfaces just to play with. I might try it on my layout too. BTW, that was your N-scale outfit in Han's video wasn't it? I'm also N-scale but nowhere near the scenery stage. So far just track although I have test run a few engines to make sure things are right. Just need that Green Hat to get my servo operated turnouts going.
@@robleathley6024 yes it is part of my layout. Only ⅓ of my layout have a good scenery. ⅔ is mostly like your. Just completed a house move and now I am looking to enlarge my layout. Until then, I am experimenting with Iott automation. I have activated block detection two months ago and I am experimenting with signals using the NeoPixel chain with s2811 chips to drive already build signals from custom signals system. I am now using tortoises motor for my switch and I won’t change those. But as soon as the new green hat is released I will order one. I already have a sg90 servo waiting. I am looking to test it out for a crossing barrier automation. My next layout will be designed with a lot off Iott devices.
@@pierrelambert446 I am about to start building my signal system. I'm using block detectors from MERG that will attach to a Yellow Hat. Like you, a string of 2811 activated 0603 RGB LEDs will be used for the actual signal. Hans showed how to use RGB LEDs with a small interface board in a video a while back. As I have a 3D printer, I'm going to try making my own signal masts. Found some designs on Thingiverse that look good. We'll have to see how it turns out.
It is almost an year now that I maintained a two week rhythm. Kind of a positive side effect of the pandemic, as I am less traveling for business. We will see how long I can go on with every two weeks once things are picking up again ;-)
Like rob I can’t wait the new video you put together every other week. I love the flexibility of your system and all the gateway build to the different model rail road standard and industry standard. Every new version of the Iott software bring many new functionality. As for your hardware it is working flawlessly since 4 months now. I am progressing too slowly to my taste on my layout project.But Iott will be an the core of my layout automation. One of the new futur features I am looking forward to use is the direct communication with JMRI without the need of a loco buffer. As my pc desk is located at the other end of my layout room.
Thank you. LocoNet over TCP is now available in the developer version on the Github!
Hello Hans ... I have one of your LocoNet Interface boards on the way, and am looking forward to working with my Digitrax system connected to our Arduinos. I have, however, had trouble finding the Arduino sketch you show in this video to control the NANOs LED via the button. I would also very much appreciate a copy of any other sketches you may be willing share for this interface. Thank you.
Check at 4;20 into the video. Once you have the LocoNet library installed in your Arduino IDE, there is a LocoNet entry in the example section. I am using the LocoNet Control Panel example in the video. It should work pretty much "out of the box".
Hans, thank you for the video. I have a DCC++ layout and want to integrate Loconet throttles into the layout. do you know what the setup on the IoTT stick and JMRI to have them talk to each other like they are on the same system?
First you need to make sure you are using a DCC++ version that supports LocoNet. Originally this was not the case with DCC++, but I found one article here www.clubncaldes.com/2017/04/cheapest-dcc-command-station-with.html where soembody added LocoNet, and the code is available on Github. I believe that a newer DCC++ implementation for the ESP32 also supports LocoNet, but I am not sure about the status of that project.
Once your DCC++ command station supports LocoNet, you can use the Stick to connect to JMRI via lbServer, or you can use a LocoBuffer USB to do the same. Your system should then be a real LocoNet system, just with a 3rd party command station, but all typical LocoNet components should run on it.
For my clarification, if I plug in only a throttle to the interface, I need a 12V supply?
No, the 12V supply is to make it Loconet Master. That is used for a stand alone Loconet without Central Unit.
If you connect a throttle to an active Loconet, it is powered from wires 1 and 6, which is DC (Loconet T) or DCC (Loconet B) but with limited voltage and current.
Thanks Hans for this video. Will one follow on the DCC interface?
Thanks for watching. A DCC interface video is not scheduled yet, but there is a good chance I'll do one sometimes in the future.
Is there a commercial available Loconet interface that can be purchased? If so is it possible for you to provide a link - Thank You
Found it above - Thank You
You only mention using a Uno or Nano. Can you use a Mega with your sheild
Yes, that would work with the same library.
@@IoTT Thanks for the quick reply. If I am right all I need to do is change the pins from & 8 to 47 & 48
As specified in ln_config.h the Mega requires pin 48 as Rx pin. The Tx pin can be set as you wish. Also note that both, Rx and Tx need to be in inverted mode. Check the notes in the ln_config.h file.
@@IoTT I have tried to download the sketch but get an error every time. I have checked the config file and this is ok. It all works ok on a Uno
I'm sure the error message tells you what the problem is. Should be easy to fix.