CBUS notes:
-
The construct node/address feels a bit … weird?
probably node and event would be a little clearer description?
i will hook up my jmri instance later and check in FLiM to check
their nomenclature. Potentially swap node and event [ address today ]
I use Flim [ windows configuration tool ] to configure CBUS nodes.
However: until now i used JMRI’s CBUS Hub function to expose that to my
internal network. Until i get to build my canether.
or to be honest my current can-ether pcb+ components is damaged → need to order and build a new one
-
Exiting without a clear save button feels strange.
If you had to back out a change because you made an error?
that is particularly a risk if you have an extensive event list.
Ask me how i know…
Hint:
3 switches
6 blocks sensors
5 end of track sensors
3 switches x 3 events [ trown / mid / closed ]
and you are already looking at 40+ events over 3 or so boards..
I am probably being a bit playful but i have seen large Cbus installs
where these numbers would be on the low side … -
I am wondering: you have reed sensor and occupancy detector
Maybe section and spot detector is covering more?
section detection for a longer section; Spot for a single short spot( i use mergs’s dtc2 power measurement based for blocks/sections and a bunch of
InfraRed sensors for spot detection; ie end of track.
i might change them out for Time of flight or ToTI [ laser based ]
but that is still spot detection anyway as far as i am concerned )
Lets also celebrate the good stuff:
Sofar both my end of track as well as block detectors [ dtc ] work.
My GUI runs from windows, the backend runs sofar faultless from a separate computer. As far as i am concerned: this is a step forward from previous experiences… Thanks @reinder [ and others ] for making it happen!
@reinder Happy to share the current track and/or the export for my cbus env