Created Date: September 03,2017

Created by: kewakl

I will hazard a guess that these images speak for themselves and I should not need to actually say what needs to be fixed.

I'll add to this as I need to. { "alt ": "Click image for larger version Name:\tbad rendering.png Views:\t1 Size:\t21.4 KB ID:\t107899 ", "data-align ": "none ", "data-attachmentid ": "107899 ", "data-size ": "full "}

Compile or transfer fixes this. This has been around since at least 1.6.0.19

Created Date: September 03,2017

Created by: kewakl

{ "alt ": "Click image for larger version Name:\tBadRendering_2.png Views:\t1 Size:\t26.6 KB ID:\t107901 ", "data-align ": "none ", "data-attachmentid ": "107901 ", "data-size ": "full "}

Yeah, fun to interpret.

Compile fixes the bad render job.

Just in case anyone asks, restarting the software does not fix this. I guess that array indexes still flabbergast this software family.

Created Date: September 04,2017

Created by: Ridgeline Mach

I have some requests of my own.

1. If you use a CPD, and it has, for example, 6 data lines that are copying, and you delete, for example the first 2, when compiling, and re-opening the CPD, the first 2 empty lines should be removed.

2. Why can't a CMP input have a range option? True when "x " value is within this range, instead of having to write two CMPs in series?

Created Date: November 29,2019

Created by: kewakl

kewakl , you know how hard it is for me to refrain from pitching Do-More, right? but we 've had that discussion several times already.....

Pitch away!

I do see some very nice capabilities in the platform.

Memory and analog inputs are what I need.

So far, the PxK platform has that- even with its drawbacks and limitations, it does what I ?need?

Created Date: December 02,2019

Created by: MikeN

Pitch away!

I do see some very nice capabilities in the platform.

Memory and analog inputs are what I need.

So far, the PxK platform has that- even with its drawbacks and limitations, it does what I ?need?

A BRX these days can have up to 132 analog inputs when filling up every expansion slot with the highest density analog cards and using the 4 built-in inputs.

I have also made use of the MicroSD card slot for saving log data. I think I have a 16GB card in the two main communication hub BRX's in each of our warehouses. To keep write lifetime up, I usually log to RAM, then write to disk what I need. I think available RAM changes depending on IO config, but mine typically have something like 800-850KB available that I can use for logging, of which I only use around 50KB before I write to "disk ". If you want to keep writing a ton of log data to the microSD, you could always make them as consumable items you replace once a year. They are pretty cheap:

https://www.amazon.com/Sandisk-Ultra...dp/B073K14CVB/

Ask Bob0 what the max size SD card you can use is. Who knows, maybe you can stick that 512GB in there and use it for 10 years before it goes bad. lol

What kind of configuration do you actually need?