Yeah, I'll dump the unipis from my project, this and (after updating the ide) "Your project has been created with (old version), please stick to that version forever to avoid errors" did it for me. Yes, S7 or Wago PFC are more expensive but concerning the hours I dumped into troubleshooting the are the better deal.

So,

I try to do some heater controlling and no matter what I do the DFactor stays zero. The only thing which brings some action is to use a negative D value which brings dampening but on the ramp-up and not when reaching the target value. Long story short: Can't for the live of me damp the overshoot the PI Part is producing and I need an "overdampend" setup because the customer is sort of intolerant concerning overshoot. Also the underlying Formula is sort of weird.

Has anybody any advise or has implemented a working PID with anti windup for Mervis?

Thanks, Andi

Thanks Martin!

Yeah, three one-wire temperature sensors. The upside is that we average the values, so we don't really care which one is which. But if I can't find a way to loop over the sensors without the bus mapping then this feature would become much more involved. Or some shell/sscp/??? magic to replace some one-wire address values after deploying...

Hi Martin,

thanks!

AUE PLC / Neuron. Mixed in the project abbreviation for the thing, sorry.

Sure, command line would actually be appreciated, better for automation.

Yeah, I guess what I'm doing is sort of unusual. It's augmentation for an industrial plant, plenty of little heaters/fans to squeeze a bit more efficiency out of an old workhorse. Since operation is not critical we opted to try the neuron/mervis combo since the price point is really attractive compared to lets say siemens or wago units.

Hi, thanks.

It's also possible to save some time by copying a AUE and live with the crude naming style. Would be nice to be able to change the prefix.

But as soon as you change for example settings on a modbus server you have to change it for every single PLC. Annoying for the six Neurons we're using atm, a dance I'm not looking forward to for the full installation (40ish PLCs).

... so, the trigger for this behavior was a division by zero on the first call to the function block (getdeltatime4...). Combined with the "stop on exception" setting the plc does just that, which is fine. Annoying though is that neither IDE nor HMI bat an eye on that, you have to go to "system status" and then to the very bottom to see that your plc just stopped all operations. Is there any way to catch such errors? I'd love to get an email when something like this happens...

so, I guess there is no documentation...

I sort of managed to be able to deploy one program to multiple plcs by not using autogen at all and doing io mapping in a way that it works if I copy&paste the plc in mervis and attach another physical plc to that copy. Far from ideal, I am not looking forward to doing this with 30ish plcs...

So,

I added a function block in mervis. When I deploy my solution, the plc starts up in some stopped state and I have to connect to it via debug and do right-click, resume normal tasks. WTF?

Also, the HMI is working just as normal, acception new values, no error messages whatsover.

How do I turn this off/is there some documentation for this feature somewhere out there?

Andi

Hi,

so I've a bunch of Neurons, all should run the same software (control for a couple of similar heater boxes). From my point of view these only differ in ip-address and some one-wire ids. Is there a manual somewhere on how to do such deployments with the least amount of hassle?

Thanks, Andi