General Topics - The Lounge
Subforums
-
- 82
- posts
-
- 92
- posts
-
- 4.2k
- posts
-
- 241
- posts
-
- 2k
- posts
-
- 2k
- posts
-
- Software download
- By pjt,
-
- 999
- posts
2,380 topics in this forum
-
- 165 replies
- 325.8k views
-
- 68 replies
- 112.8k views
-
- 2 replies
- 131 views
-
- 7 replies
- 833 views
-
- 1 reply
- 138 views
-
- 5 replies
- 409 views
-
- 2 replies
- 1.7k views
-
- 2 replies
- 340 views
-
- 12 replies
- 17.1k views
-
- 0 replies
- 207 views
-
- 3 replies
- 1.7k views
-
- 0 replies
- 623 views
-
- 8 replies
- 6.4k views
-
- 1 reply
- 599 views
-
- 1 reply
- 685 views
-
- 7 replies
- 2.6k views
-
- Guest
-
- 21 replies
- 12.9k views
-
- Guest
-
- 7 replies
- 1.7k views
-
- Guest
-
- 0 replies
- 1k views
-
- Guest
-
- 2 replies
- 1.3k views
-
- Guest
-
- 1 reply
- 1.3k views
-
- Guest
-
- 2 replies
- 3.2k views
-
- 5 replies
- 14.3k views
-
- 0 replies
- 817 views
-
- 0 replies
- 1.4k views
-
Posts
-
Hello, Is anyone familiar with how to load the program on a WECON HMI? The HMIs we have do not load to the same screen the instructions show. Thanks! -
The manual has connecting examples, how you need to wire the STO. -
By pcmccartney1 · Posted
L4x family always had issues with bricking. -
As I understand, the binary/digital I/O from the panelview to the PLC is working, so i would think the comms is fine. What isn't working is the block transfers, which transfer the integer data on RIO panelviews. If no integer data is being transferred the recipe pointer etc will all be 0 or the value of the last update within the plc. I have vague recollection of BTR/BTW stopping when the msg buffer fills, and i think there is some bit with the control block which you can monitor. I need to dig out a manual. -
None of the block transfers associated with the PanelView show .DN. Maybe the pictures didn't capture that during the very fast updates, but I suspect there's no communication. Again, wiring is the usual suspect, but it's possible a port failed in the controller or the PanelView. Check wiring continuity and terminating resistor values. It's rare, but I've seen resistors change value or open. I would change that T4:0.PRE to a few hundred to see the results of a slow poll. Do block transfers complete? (.DN on) I would probably try to leave it around 10 instead of 1 when this is resolved if there's no noticeable HMI lag from it. I wondered if someone accidentally pulled out the RIO connection from port 1, said oops, then plugged it into port 0, thinking that's where it was. I suspect you wouldn't be online if that was the case, but it's something to think about. I'm out of practice with RIO, but I remember different baud rate options and different terminating resistor values for different rates. If that's selectable in the HMI, make sure it matches the PLC settings. A slower baud rate might help mitigate noise problems. -
There are many benefits! In the Motion Control Setup, you input the encoder specifications. In addition, you can enter values for the scaling. There will be no need for a custom FB. The Motion Control Setup will calculate these values for you. Take a look at the NJ_NX-Series Motion Control Manual, section 2-1-2 Axis Variables. -
By VulpesLago · Posted
Is there any other benefit than get velocity and other values from axis? I was thinking about to make custom FB to calculate difference between actual value every 100ms. with that calculation i can get velocity aswell. -
The VFD control is separate. This was discussed in another thread you started. An encoder can be 'read' via the Motion Control Setup if it is either, EtherCat or a standard encoder wired to an encoder input module. (NX-EC0*).
-
By VulpesLago · Posted
I have not set it up with anything yet. I am still looking what i need to do the project. If i set up encoder as axis can i use MC_functions to control VFD via Ethercat? -
Interesting. Let me understand what you're talking about better with the recipe. You type the recipe number into a field (which works), then push a button which moves the value into another box, which lets you advance to the next step. But....hitting the button doesn't do anything. It sounds like you push the button and the PLC does something (validates the number to make sure it's a valid value, probably) and then updates the other field. Do you know where this is handled in the PLC? I'd be curious to see if any of the registers in the PLC are updating. If you can find the BTR/BTW that serve the HMI, you can then see the PLC addresses that are written by the HMI (well, technically read by the PLC from the HMI) and see if anything is changing when you enter the value and hit the button. Is there any chance you have access to the HMI program and software?
-