I'm confused, Marky. Where does? JMRI enter into this?

Wouter

On Sun, 23 Jun 2019 at 13:56, Marky <thrashbash31n@...> wrote:

Hi everyone,?

first of all , like to say i'm a newbie at this , so please bear with me.

I'm working on connecting 5 x?90 sg servos from one arduino , which in theory is possible? (via output pins 3,5,6,9,10,11), i'm currently running a sketch which operates one turnout successfully, but when i try to add additional servo's, the arduino isn't recognizing the signal from my PC (i'm getting the RX & TX leds on the arduino)

The thing i would like to know is, how to add additional turnouts to my sketch, as i've tried turnout2 and thats not working.


The sketch i'm running is here:

#include <CMRI.h>
#include <Auto485.h>
#include <Servo.h>

#define CMRI_ADDR 1

#define DE_PIN 2
int turnout1 = 0;

Auto485 bus(DE_PIN); // Arduino pin 2 -> MAX485 DE and RE pins
CMRI cmri(CMRI_ADDR, 24, 48, bus); // defaults to a SMINI with address 0. SMINI = 24 inputs, 48 outputs
Servo turnOut1;

void setup() {
  turnOut1.attach(9);
  turnOut1.write(2);
  bus.begin(9600);
}

void loop() {

   cmri.process();
   turnout1 = (cmri.get_bit(47));
   if (turnout1 == 1){
      turnOut1.write(10);
      turnOut1.write(9);
   }
   else{
      turnOut1.write(2);
   }
}

many thanks

On Jun 23, 2019, at 3:01 AM, bluetobits <steve.lomax@...> wrote:

Hi. Dave
Sorry about forgetting the custom icons. I'm running JMRI from google drive so I can work files on 2 machines. all the files are a bit over the place. Another thing to add to the list!
The area I was trying to address was indeed the lower rays of the turntable. .I tried deleting all the ray track and re-creating them to try to cure the issue and sometimes it works, most times it doesn't. In the version before this one I re-named many of the blocks from within the block table and created new blocks. The turntable is manual. The sensors are used as momentary switches which trigger my home grown turntable in much the same way as my turnouts. It's all handled in hardware from the JMRI dcc++
--
Steve 009 in UK

On Jun 22, 2019, at 5:48 PM, bluetobits <steve.lomax@...> wrote:

Sorry should have included: PanelPro 4.15+R5fb3e69, Java 1.8.0_161, Win 10, DCC++,

--
Steve 009 in UK

Hi Tim,

The status of the Light was sometimes being set quicker than the OpenLCB Light initialisation routine could cope with, causing it to go into an infinite loop condition if actioned pre-initialisation.

I'm definitely no OpenLCB expert so I'm unaware of what happens in that process, I just know that we can't allow calls to set the Light state before it's done!

Perhaps when creating manually, there will be less going on compared to the middle of an xml load so will initialise quicker?

Steve.

Hi Tim,

Many thanks for testing with a developer version and for uploading your xml, I found it in this folder??/g/jmriusers/files/ProblemsBeingWorkedOn/Updated%20Lights%20-%20Testing
All attachments in emails sent to the group are stripped from the message.

In OpenLCB CAN Simulation I was able to produce an issue with constant on-off messages in some of the OpenLCB lights using your xml file.
The status was being set before some OpenLcb specific code had finished initialising the Light.
( Red Herring alert for future dev. The higher address ranges seemed to take longer to initialise ?? )

I've added a further check to stop an OpenLCB Light status being set before being fully initialised via Github ref 7120??
With this in place I was able to load your panel with no issues, and have checked that Lights are being set at the right times.

I'll message here when an updated version with the fix is available,

Steve