Veganic

MrPLC Member
  • Content count

    471
  • Joined

  • Last visited

Posts posted by Veganic


  1. Has anyone else tried to use the "Advanced" program example for the FX3 dedicated inverter library? The function block seems to work ok. The sample program doesn't. It compiles and downloads ok but gives a "Ladder Error" I have screen grabs of the offending code. ------------------------------------------------------------------------------ The general question is how can a program which compiles ok give ladder errors when downloaded? The specific question is what is wrong with this sample program/my use of it?

  2. I'm trying to program as much as possible so that I understand what is happening. The biggest problem is finding the information. This is just a "research" project so at least I don't have a deadline. I only have an FX1n to play with so can't use the beijers function blocks.

  3. That seems to have worked...I had calculated the PDOs based on the BFMs being words (2 bytes) but they are double words (4 bytes)...I think. My next challenge is to try and increase the number of PDOs to greater than 4.

  4. Hello, I have a simple Canopen network. Everything seems to be working ok, data is being transmitted etc, but.... I have a flashing error light on the FX2N-32CAN module. Bit 14 is set in BFM 29. This is listed as "Error passive state." What exactly is this indicating? How do I make it go out? (I've tried writing 0 to BFM29) Thanks!

  5. Whenever I try to use Global variables I get the following error.... "The variable is not a definition" I can use local variables. Is there some check box I'm missing? Anyone have a sample program with globals that work? Gx developer V 8.8 Also tried it in V8.12 so I'm assuming its me and not a bug. My reference source is GX Developer Operating Manual Art. no 160262. Edit : I found the problem. I need to set the AU parameter which then becomes an asterix Global Variables -> Label Then Check Au column.

  6. Have you tried to "go online"? Ususally asks you if you want to download. I've not used Beckhoff, only other CoDeSys versions. "Create boot project" just writes your program to the permanent memory, ie, it's retained after a power down. Writes don't get permanently written until you "Create boot project".

  7. I've uploaded a program with GX developer from a FX1 PLC. It has the following line: -|M8000|-------MOV D100 D100. The only thing I can think is maybe it has been compiled in IEC developer? This form is repeated in a few places in the program. Can anyone think of a reason for this line of code?

  8. CC-link anyone? The programs could be identical - just set the dial on the hardware. For: Relatively low cost. Bulletproof auto-detection of slaves. Simple to program. Against: Some cost. If you already have Ethernet/RS 485 its an added cost. Not as simple as the plug and socket.

  9. I can see how it would happen but it depends on the first line of code and how the preceding conditions go on and off.... The sequence would perhaps be something like this: Bit one goes on. The timer times out. The bits are reset. On the very next scan Bit two goes on. The timer stays on so doesn't time out and will never reset. And then it's just a matter of time to wait for the conditions to be right to set the other bits. Once set they cannot be reset without a power off. Whether those bits can actually be set depends on the rest of the program.

  10. At first glance I'd say move the reset and timer to before the setting rung. There is a possiblilty with your code that the timer never gets reset. 1. Set M0 2. Set M0 -> Timer 3. Timer done -> reset M0 4. some part of the program sets M0 and Timer never goes off. Alternatives would be Timer must not be done or enabled to allow the setting of M0 Edit : What I'm trying to say is that it is about the order of scan.

  11. I want to control a D700 inverter (x 3) from a GT1020. But... I want to start and stop with a momentary signal rather than a set/reset. An E-stop doesn't stop the drive, it just stops the output frequency. The problem I have is that with a SET bit to run the drive continues to run thru an e-stop (via SC+S1 &S2 terminals) and ramps up as soon as the e-stop is reset. I have a plan B : connect some pushbuttons! Before I resort to that I was wondering if anyone has any ideas. The problem seems to be that changing the function of the inputs doesn't change the function of WSx:x I have run out of time today so I have yet to try: Set to run. Monitor an input to fire a trigger to reset the run bit in the HMI. Edit : something else that might work is changing the Run output to "Safety Monitor" and using that to reset the bit with a trigger in the HMI. Will this work? Anyone had this problem before?