Internet PLC Forum

That would be the best in my dream, but as far as we are selling the machine, nothing is really preventing to the customer a physical access and let competitors doing reverse ing.

The fact of using Load_eep to use a non Modbus accessible memory is already a step, Encrypting this memory before transmitting into the DM variable is also a way.

Unless dismounting the switch or hard wiring the switch. or diving the plc in resine....

Hello everybody,

That's a good news... But can you give me more details about that way of using the LOAD_EEP variables.

1) If the FRAM-256 RTC is present, the pseudo eeprom is not used anymore and replace by the FRAM memory that can handle unlimited read/write. Is it right?

2)If the fact of Using the LOAD_EEP command is as faster as using the DM[xx] acces or will it slow the complete ladder speed process?

Regards
 

The other solution is to use a DM32 variable that can easily handle the 6 digits of the full time from 000000 to 235959
 

Hello Everyone,

I'm getting some '2 years old FMD88-10   FirmWare 78A'  where  it's written Rev 1 on the motherboard
and a 'new FMD88-10 Firmware 81' where it's written Rev 3 on the motherboard

When uploading my software and displaying the ladder logics scan counter per  seconds,

I'm on 700 ladder scan per seconds and on the new harware more than 1350 ladder scan per seconds.

Is this difference  due to hardware or firmware? Is there a way to speed up the olds FMD88-10?

Regards.

Philippe

Thanks for your reply Gary

I've noticed that on my original message there was a mistake in the description
-
"when, under ITrilogi V6.47 I quickly hit the Stop_button_Rel (R71), it's going back in the timer waiting loop...
if I longer hit the Stop_button_REL, then it's correcly clearing the alarm and working as expected"

The problem here is that I cannot automaticaly clear the alarm after a time out only.

I used the stop button for this example, but mainly this logic will be used for a vibration switch that start an emergency stop of the machine and I don't want to have the operator just cleaning the alarm without an visual inspection to see what caused this alarm. Just resetting automaticaly after a time out is not enough. I would like to avoid him just cleaning the alarm and let the marchine restarting. The delay 'behing' is to force them to go to a visual inspection anyway and not being 'obliged' by performance manager/financial people to bypass the procedure. Because i'm pretty sure in that domain, productivity can overpass procedures and warranty.

Good day everyone,

I'm creating some rung to handle emergency hammer buttons. The idea is when the N.C. hammer button is hit, a relay keep the status (latch) and when the hammer button is resetted, a timer start to clear the error status and also a reset error request... the idea is to avoid removing the alarm directly.

The current logic is working fine up to the point when the timer reach 0 (elapsed reset time), the system is waiting a realise relay hit to clean the emergency.

when, under ITrilogi V6.47 I quickly hit the Stop_button_Rel (R71), it's going back in the timer waiting loop...
if I longer hit the Stop_button, then it's correcly clearing the alarm and working as expected.

I cannot explain why a short hit is not clearing the alarm and where it's happening in the ladder. Is it a ladder logic mistake? Where is the fault?

Description of the differents inputs/relay/timers

I1    : INPUT : Emergency_Butt ( N.C. circuit)
R72 : RELAY : Stop_Button_Ok ( Use to be N.C / N.O independant from the INPUT logic)
R70 : RELAY : Stop_Button (Latch that keep that an emergency event happend)
R71 : RELAY : Stop_Button_Rel (Request for cleaning the alarm (If the Stop_button_Ok is not ok, the R71 is opened)
R73 : RELAY : Stop_Button_Tim (Closed when the T2 timer is running)
T32 : TIMER : StopButtonDelay (Set to a amount of waiting time and activated when the physical alarm is cleared)

I've received 2 'old' FMD88-10 that have firmware 78A and 78B

I'm currently developping on a third one that have firmware R81

I've read in the forum that it's not an easy task to upgrade it.

By seaching in the manuals, most of the functions i'm using are available and program upload seem to fork fine.
But I wonder if there are some bug fix, behaviours modifications and so between the differents firmware?

Is it possible to know (even in PM) what are the differences between theses firmware to avoid a deep testing again of the software on the others PLC

Regards