On 17 Dec 2018, at 6:37 AM, Perry Squier via Groups.Io <wpsquier@...> wrote:

Thank you again for your help with this. I want to mention to you that I have been using the same cables connected to the NCE Power pro command station for years but with an older Mac and older version of DP. The only reason I wanted to upgrade is for Tsunami 2 decoders.
The JMRI settings are the same as #1 below and The connectors have never been removed or altered from the NCE station. I will check the AIU and review all again in the morning and get back to you.

On Dec 16, 2018, at 1:51 PM, Dave Heap <dgheap@...> wrote:

Perry,

Thanks for the log. This indicates JMRI has found the Prolific cable and is using the correct Baud Rate and command station settings.

There are two settings you need to check in the Power Pro under Setup Command Station:

- AIU broadcasts must be disabled.

- Baud Rate must be set to 9600.

I'd be suspecting problem (2) below. Please look up the web page I refer to below.

One other question before you do that. Do you have an extra connector cable between the Prolific and the Power Pro? If you do, the cable may be the wrong type (crossover or Null Modem) rather than the needed straight-through.

1) JMRI Settings.
============
The correct JMRI settings for a recent Power Pro are:
System Manufacturer: NCE
System Connection: Serial
Serial Port: <the name you determined above>
Connection Prefix: N (default and recommended)
Connection Name: NCE Power Pro (recommended name).
Additional Connection Settings: ticked
Baud Rate: 9600
Command Station EPROM: 2006 or later (unless you have an old system)

2) Connection to the Power Pro serial port.
===============================
The Power Pro front panel is quite a heavy gauge. Because the socket is behind the panel and the retaining binder posts are in front of the panel, a normal serial connector cannot seat correctly in the socket (the pins barely engage). The result is an unreliable connection.

This link explains the problem and fixes, with actual photographs.
<>


--
Dave in Australia

On 17 Dec 2018, at 1:45 AM, Perry Squier via Groups.Io <wpsquier@...> wrote:

<snip>

2018-12-16 09:38:16,570 apps.AppsBase ????????????????????????INFO ?- DecoderPro version 4.12+Rb6a9bb1 starts under Java 1.8.0_191 on Mac OS X x86_64 v10.14.2 at Sun Dec 16 09:38:16 EST 2018 [main]

2018-12-16 09:38:16,905 gui3.Apps3 ???????????????????????????INFO ?- Starting with profile My_JMRI_Railroad.3e0490cf [main]

2018-12-16 09:38:22,027 node.NodeIdentity ????????????????????INFO ?- Using jmri-lYrywdrrbhNiaaXgMnMayg-3e0490cf as the JMRI Node identity [AWT-EventQueue-0]

2018-12-16 09:38:22,230 xml.AbstractSerialConnectionConfigXml INFO ?- Starting to connect for "NCE" [main]

2018-12-16 09:38:24,369 serialdriver.SerialDriverAdapter ?????INFO ?- NCE cu.usbserial port opened at 9600 baud [main]

<snip>

2018-12-16 09:38:34,494 jmrix.AbstractMRTrafficController ????WARN ?- Timeout on reply to message: AA consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:34,601 nce.NceConnectionStatus ??????????????WARN ?- Incorrect or no response from NCE command station [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:34,606 jmrix.AbstractMRTrafficController ????WARN ?- timeout flushes receive buffer: ?[nce.NceTrafficController Receive thread]

2018-12-16 09:38:44,605 jmrix.AbstractMRTrafficController ????WARN ?- Timeout on reply to message: AA consecutive timeouts = 1 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:44,712 nce.NceConnectionStatus ??????????????WARN ?- No response from NCE command station [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:54,714 jmrix.AbstractMRTrafficController ????WARN ?- Timeout on reply to message: AA consecutive timeouts = 2 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:54,818 nce.NceConnectionStatus ??????????????WARN ?- No response from NCE command station [nce.NceTrafficController Transmit thread]

2018-12-16 09:39:04,822 jmrix.AbstractMRTrafficController ????WARN ?- Timeout on reply to message: AA consecutive timeouts = 3 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2018-12-16 09:39:04,927 nce.NceConnectionStatus ??????????????WARN ?- No response from NCE command station [nce.NceTrafficController Transmit thread]

2018-12-16 09:39:04,936 jmrix.AbstractMRTrafficController ????WARN ?- timeout flushes receive buffer: F4 [nce.NceTrafficController Receive thread]

On 17 Dec 2018, at 1:45 AM, Perry Squier via Groups.Io <wpsquier@...> wrote:

<snip>

2018-12-16 09:38:16,570 apps.AppsBase ????????????????????????INFO ?- DecoderPro version 4.12+Rb6a9bb1 starts under Java 1.8.0_191 on Mac OS X x86_64 v10.14.2 at Sun Dec 16 09:38:16 EST 2018 [main]

2018-12-16 09:38:16,905 gui3.Apps3 ???????????????????????????INFO ?- Starting with profile My_JMRI_Railroad.3e0490cf [main]

2018-12-16 09:38:22,027 node.NodeIdentity ????????????????????INFO ?- Using jmri-lYrywdrrbhNiaaXgMnMayg-3e0490cf as the JMRI Node identity [AWT-EventQueue-0]

2018-12-16 09:38:22,230 xml.AbstractSerialConnectionConfigXml INFO ?- Starting to connect for "NCE" [main]

2018-12-16 09:38:24,369 serialdriver.SerialDriverAdapter ?????INFO ?- NCE cu.usbserial port opened at 9600 baud [main]

<snip>

2018-12-16 09:38:34,494 jmrix.AbstractMRTrafficController ????WARN ?- Timeout on reply to message: AA consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:34,601 nce.NceConnectionStatus ??????????????WARN ?- Incorrect or no response from NCE command station [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:34,606 jmrix.AbstractMRTrafficController ????WARN ?- timeout flushes receive buffer: ?[nce.NceTrafficController Receive thread]

2018-12-16 09:38:44,605 jmrix.AbstractMRTrafficController ????WARN ?- Timeout on reply to message: AA consecutive timeouts = 1 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:44,712 nce.NceConnectionStatus ??????????????WARN ?- No response from NCE command station [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:54,714 jmrix.AbstractMRTrafficController ????WARN ?- Timeout on reply to message: AA consecutive timeouts = 2 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2018-12-16 09:38:54,818 nce.NceConnectionStatus ??????????????WARN ?- No response from NCE command station [nce.NceTrafficController Transmit thread]

2018-12-16 09:39:04,822 jmrix.AbstractMRTrafficController ????WARN ?- Timeout on reply to message: AA consecutive timeouts = 3 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2018-12-16 09:39:04,927 nce.NceConnectionStatus ??????????????WARN ?- No response from NCE command station [nce.NceTrafficController Transmit thread]

2018-12-16 09:39:04,936 jmrix.AbstractMRTrafficController ????WARN ?- timeout flushes receive buffer: F4 [nce.NceTrafficController Receive thread]

On Dec 16, 2018, at 10:23, Nathan Tableman <nathan@...> wrote:

My WIP code

See comments for my thinking on how to iterate into features, but the idea for me is that I am going to make a second q that allows these things to “self config”

Then maybe on that q I also send into these things from node red a polling request, then I can control when and how (maybe even combine the setup and poll message to make these sensors VERY flexible)

But for now I have hardcoded some variable.

My q pattern is /trains/sensors/MAC.pin

Payload is JSON that mimics the JMRI one with an exception, I change the number to a word, and I am fixing that in mode red.

Again my idea here is to make this as plug and play as I can. I don’t want to write code specific to each of my ESPs I just want to load them up and be done.

Of course the ip of the server is a pain, but I have yet to see a zero conf enabled MQTT….

If you want to make this work directly with JMRI and you assume the MQTT is running on the same IP, you could scan for a zero config that comes from JMRI, use that IP and change this code to conform directly to the JMRI format.

Since node red is awesome I always use it as something in the middle to transform and I use it to blink LEDs and other things in my system.

/*

? ?Nathan end of 2018

? ?Idea is to make code that can be pushed to any esp 2886

? ?that auto forms a sensor net for model rail

? ?the first part is not done:

? ?have a zero conf mqtt config q that the devices get their infor from to have them act normal

? ?instead I am just hard coding it all

? ?other todos

? ?some kind of debouncing - not realy debouncing, but I have not yet though about how I want the fliping of state to handled

? ?as of right now these messages are managed by node-red and then go into JMRI since JMRI doenst have a uniform interface

? ?ead the device type and make a list of input pins (the idea is to make this thing super automatic) right now I am just hard coding them

? ?Adafruit Feather HUZZAH ESP8266 pins: #0, #2, #4, #5, #12, #13, #14, #15, #16

? ?{"type":"sensor","data":{"name":"IS2","state":4}}

? ?{"type":"sensor","data":{"name":"IS2","state":4}}

? ?this is designed to run every loopDelay ms and report all the sensors on pins in usablePins[]

? ?I have thought that I should only report changes, but it seems to be more reliable to report all and often, I need to think about this

? ?which is why debouncePins is there - starting to think through how I only report changes.

? ?and a third idea is an API to request a read using the q this thing is susbribed to they way I can control the polling from node red

*/

#include "EspMQTTClient.h"

#include <SoftwareSerial.h>

String payload = "I'm here! " + WiFi.macAddress();

int lastreading = 0;

String topicPrefix = "trains/sensors/";

void onConnectionEstablished();

String sensorPrefixJSON = "{\"type\":\"sensor\",\"data\":{\"name\":\"";

String sensorInFixJSON = "\",\"state\":";

String sensorSuffixJSON = "}}";

int usablePins[] = {4,5,12,14};

int debouncePins[] = {};

int loopDelay = 250;

EspMQTTClient client(

? “Flopper", ? ? ?// ssid

? “Flipper", ? ? ? ? ? ?// password

? "192.168.20.78", ? ? ? ? // MQTT ip

? 1883, ? ? ? ? ? ? ? ? ? ?// MQTT broker port

? "", ? ? ? ? ? ? ? ? ? ? ?// MQTT username

? "", ? ? ? ? ? ? ? ? ? ? ?// MQTT password

? WiFi.macAddress(), ? ? ? // Client name

? onConnectionEstablished, // Connection established callback

? true, ? ? ? ? ? ? ? ? ? ?// Enable web updater

? true ? ? ? ? ? ? ? ? ? ? // Enable debug messages

);

void setup()

{

? Serial.begin(115200);

}

void onConnectionEstablished()

{

? /*

? ? ?in here I want to call a special queue/config somehow so this thing auto configs

??

? String subTopic = topicPrefix + "#";

? client.subscribe(subTopic, [] (const String & payload)

? {

? ? //Serial.println(payload);

? }); */

}

void loop()

{

? client.loop();

? int arraySize = sizeof(usablePins) / sizeof(usablePins[0]);

? for (int x = 0; x < arraySize; x++) {

? ? int pinToUse = usablePins[x];

? ? int reading = digitalRead(pinToUse);

? ? String topic = topicPrefix + WiFi.macAddress() + "/" + pinToUse;

? ? if (reading == 1) {

? ? ? String publishJSON = sensorPrefixJSON + WiFi.macAddress() + "." + pinToUse + sensorInFixJSON + "OFF" + sensorSuffixJSON;

? ? ? client.publish(topic, publishJSON);

? ? } else if (reading == 0) {

? ? ? String publishJSON = sensorPrefixJSON + WiFi.macAddress() + "." + pinToUse + sensorInFixJSON + "ON" + sensorSuffixJSON;

? ? ? client.publish(topic, publishJSON);

? ? }

? }

? delay(loopDelay);

}

On Dec 15, 2018, at 12:56, Chris Rood <crood58@...> wrote:

Manu,

I agree and was going to respond back with the same when I had the chance. Most ESP8266 and ESP32 have SPIFFS like you said and you could store the config in a JSON file. JSON can be parsed by the ESP very easy.?

On Dec 15, 2018, at 12:56, Chris Rood <crood58@...> wrote:

Manu,

I agree and was going to respond back with the same when I had the chance. Most ESP8266 and ESP32 have SPIFFS like you said and you could store the config in a JSON file. JSON can be parsed by the ESP very easy.?

On Dec 16, 2018, at 9:35 AM, Perry Squier via Groups.Io <wpsquier@...> wrote:

Dave,

here is the USB cable report:

USB-Serial Controller:

? Product ID: 0x2303

? Vendor ID: 0x067b? (Prolific Technology, Inc.)

? Version: 3.00

? Speed: Up to 12 Mb/sec

? Manufacturer: Prolific Technology Inc.

? Location ID: 0x14200000 / 27

? Current Available (mA): 500

? Current Required (mA): 100

? Extra Operating Current (mA): 0

There is no Serial Number field.

Perry

On Dec 14, 2018, at 7:42 PM, Dave Heap <dgheap@...> wrote:

Perry,

I helps enormously. The vital line is:

2018-12-14 13:55:40,514 serialdriver.SerialDriverAdapter ?????ERROR - Serial port cu.usbserial not found [main]

This indicates that JMRI is trying to open the serial port called "cu.usbserial" and it does not currently exist. So obviously nothing can work. ?There are several possibilities:

The the most likely is that the port has changed name because you have plugged the USB-Serial cable into a different port and macOS has changed the port name. This can occur if you have an office-supplies type cable that doesn't have a unique serial number.

You need to:

- Upgrade to JMRI V4.14 as soon as it comes out. It will catch such problems and stop you from trying to use DecoderPro until you fix the problem.

- Start again with my previous instructions, with the following additions.

When you look at the System Information USB report for the cable, note the Manufacturer name and whether there is a Serial Number field. Report back on this (select, copy and paste works).

Once you have seen the port appearing/disappearing, leave it plugged in, don't reboot your computer, start JMRI and select the correct port, restart JMRI only and check that all defaults preferences are set to NCE. Restart JMRI if needed.

Get us another log and we'll see if we have a connection.

Dave in Australia

On Dec 14, 2018, at 7:42 PM, Dave Heap <dgheap@...> wrote:

Perry,

I helps enormously. The vital line is:

2018-12-14 13:55:40,514 serialdriver.SerialDriverAdapter ?????ERROR - Serial port cu.usbserial not found [main]

This indicates that JMRI is trying to open the serial port called "cu.usbserial" and it does not currently exist. So obviously nothing can work. ?There are several possibilities:

The the most likely is that the port has changed name because you have plugged the USB-Serial cable into a different port and macOS has changed the port name. This can occur if you have an office-supplies type cable that doesn't have a unique serial number.

You need to:

- Upgrade to JMRI V4.14 as soon as it comes out. It will catch such problems and stop you from trying to use DecoderPro until you fix the problem.

- Start again with my previous instructions, with the following additions.

When you look at the System Information USB report for the cable, note the Manufacturer name and whether there is a Serial Number field. Report back on this (select, copy and paste works).

Once you have seen the port appearing/disappearing, leave it plugged in, don't reboot your computer, start JMRI and select the correct port, restart JMRI only and check that all defaults preferences are set to NCE. Restart JMRI if needed.

Get us another log and we'll see if we have a connection.

Dave in Australia

On 16 Dec 2018, at 2:06 PM, Marc <forfoum@...> wrote:

Dave,

Yes I noticed :-) and deleted the post...

On 16 Dec 2018, at 1:41 PM, Marc <forfoum@...> wrote:

If you are using Locobuffer-USB and say DCS100 on COM3. PREFERENCES Connections should be such :




And the Defaults should be as such :



Marc