Rivka

In your case I would contact Unitronics technical support. They might want to get one of the faulty CPUs for investigation.

Do you mean that since you replaced CPU you don't have CPU errors anymore? Or do you mean that every time it occurs, you replace the CPU and reboot and then it works, but fails again a few weeks later with the replacement CPU? After CPU error occurs, rebooting again with same CPU works? If the issue happens always with same CPU, it can be because of a loose connection between CPU and panel. If it happens with different CPUs, please contact support so they'll guide you how to extract logs and send to us when it happens again. Hope this helps, Rivka

Please note that although you cannot force the user to use the function correctly, you can guide him to do so, using comments on parameter In and Out, and run-time checking, as follows:

Hi @Cara Bereck Levy, Your attention on that point please. Thanks! Rivka

Hello. If your project is corrupted, as it seems to be, I would go for the support solution right away. It is possible someone from R&D will fix it easily. Have a good day! Rivka

Hi, @NoamM, do you have suggestions about that issue?

Hello @Árni, It is kind of funny to come back to you after such a long time and I hope you already solved your issue. In such a case, I would contact technical support with a print screen of the CANOpen statistics struct and of the node's struct. Looking at the project only, it seems that you've done everything as you were supposed to. I already see that you tried to troubleshoot your issue via CAN sniffer. Did you see the PDO data arriving (other than 0)? Pay attention that you have a CAN sniffer filter available, based on COB-ID, to be able to see messages that you want only. (filter is configured at compile time, then can be modified at run-time through the "System -> CAN Sniffer Filter" struct Best regards Rivka

@Cara Bereck Levy, is it possible to react on that message, please? (I can help you by describing the exact behavior of those functions)

Hello @brugola The RED solid LED ndicates that there is no power provided to the module. This explains nothing works. @Cara Bereck Levy, can you please add this information to the help? Have a good day! Rivka

Dear @Dave, Your request had been added to the roadmap! (will probably appear in UniLogic 1.35) Thanks for the proposition! Rivka

Thank you @curtharrington1 for clarifying the feature. It is indeed a new feature that was introduced, along with the "for" and "while" loops. It is worth having a look at them! About the feature request on the dynamic combobox, that could be a nice feature. I'll open a feature request on it. Have a good day! Rivka

Hello @Jeff164, Basically, "Click/Tap" option is a combination of press and release: only if the panel detects both press and release event on the button will the action be triggered. In general, you can always set your bit upon "press" event and the ladder code that gets executed as a result of that bit rising would reset the bit after finishing the work. That can avoid the timing issue where a piece of code is supposed to execute if "MAN A FILL WT SAVE" tag is ON and the interval of time between the press and release events is too short compared to the ladder cycle time. Hope this helped, Best regards, Rivka

Hello @Hoops123, I can see there are a few holes in the help regarding the motion error codes. We are sorry for the inconvenience. -321 is a code that applies to EtherCAT axes only and means that the EtherCAT axis is in error state. The help will be updated with the missing error codes. Thanks for pointing this out to us. Best regards, Rivka

Hello @Skye, @curtharrington1 and @Dave, As you can read from Saragani's answer, this feature had been added and will appear on next UniLogic official version. We hope you'll enjoy! Best regards, Rivka

@Saragani, Your attention on that feature request Thanks, Rivka

ok, great, so that means that the new error code was useful even though it was not documented. I'll talk to the relevant person so it will be added to the help. Have a good day, Rivka

Hi, After consulting, code 5 actually points out to an IO that is electrically connected, but which software is malfunctionning. But in fact, this situation should have created a pop up listing all the connected IOs and you should have seen that the last one was missing. Was it the case for you, @Kojekude? Regards, Rivka

Translation:

Hi @Kojekude, Happy to hear that your issue was somehow resolved. This post will help us fill a blank in the help as status 5 was added later in order to help understanding exactly your kind of issue: status 5 means "one of the IOs is faulty". But obviously, if it does not appear in the help, it will not help anybody... @Shraga, could you please explain to @Cara Bereck Levy the addition of this error code and the way to have complementary informations on the nature of the faulty IO so she can add it to the help? Thanks, Rivka

@kratmel You probably meant that in that case we should choose "Pulse and direction" interface type in the counter configuration, then one of the inputs will be connected t the counting and the other, to the direction. Am I missing something?

Hello, Please have a look on the "Continuous update" parameter of most of the function blocks. It can help you to correct the position error. The MC_SetPosition cannot be used in your case because drive has to be stopped to use it. Hope that helped, Rivka

Hello, Sorry for the long delay, I hope your issue got solved in the meanwhile. If not, I would be interested in knowing what are the values of the TCP client struct members when the issue occurs:. Can you please post a print screen of the struct's values? Best regards, Rivka

Hello, Sorry for the long time without any answer. What you describe is actually strange (when PWM mode is 0, it is normal that the target reached does not work, but when PWM mode is 1, PWM current position should not stay 0).I would suggest you to send that issue to technical support. Best regards, Rivka

Happy to hear it was helpful!

Hello, The syntax is not correct. If you want to use the Var_Struct_Student variable, don't specify again the type. The compiler understands that you want to redefine the type Student. I don't know what you intend to do with the variable Var_Struct_Student, but this is an exampple of a correct way to use it: int i = 0; Var_Struct_Student[i].rollNumber = 5; (note: there is another issue here, that you use i before you assign a value to it.) I would suggest you to get a more solid C background, before using C functions, as debugging them could be more painful than ladder. C functions are of the type "you know what you are doing? So go for it!" Hope that helped Rivka