photovoltaic

How do you have the encoder axis setup in your Axis Settings?

Just a bit of a gotcha when doing this - Make your input assembly on the CJ side 4 bytes larger than what you ask for with the CL PLC. This is to accommodate the run-idle header. Example: CJ input assembly size in Network Configurator: 104 bytes Generic Ethernet Device assembly size in Studio: 100 bytes This is only for the CJ input, not the CJ output.

The typical way to establish an implicit connection between a CJ and a Compact Logix is to have the CL PLC control the communications. You can use the Generic Ethernet Device profile in Studio and assign instance numbers to the CJ network variables using network configurator.

The instruction "GetTime" shouldn't exist really. The system variable "_CurrentTime" gives you the exact same thing and is updated automatically.

Have you synchronized with the controller, made sure that you have "Monitor" turned on, and the program is assigned to a task?

I might have a 12 buried somewhere, I'll check in the new year. If so I can clone the internal CF and send you the contents.

Use an increment instruction instead of a counter.

Can you share the axis setup?

  Yes, checked on Windows. It is split into 2 partitions and Windows can't tell what filesystem they are. Perhaps one contains a bootloader, the other the OS.

Its an unrecognized file system on the internal CF. If you formatted yours I think that's the end of your screen

I believe the special requirement is you never touch the internal CF card. If I get a chance today I'll see what mine contains.

If correcting one side disrupts the other side I think you should be looking at a mechanical fix first. If you're simply looking to get real world units out of the camera the math is pretty straightforward and there is also the ability to setup real world units and the vision tools can inherit that scaling factor. I'm a little unsure what you are asking exactly.

In Windows I used a generic 1GB CF card. I used the Windows Disk Management utility. 1) Delete the volume 2) Create a new volume (size 64MB, FAT, Default Allocation, Quick Format) 3) Transfer Restore Files and recover the screen  

I suggest comparing the drive parameters with your backup. I've only ever seen this behavior when an axis isn't tuned.

Yes, each reference a timer/counter/variable. You will likely need to do some pre-formatting/scaling of the values in the PLC as the NB only accepts elementary data types.

Omron PLCs are not brokers, just clients. We can interface with multiple brokers though so I don't see why you couldn't do that.

You'll have to use 2 variables and place a ":" in between them.

It works well. I have use LAN and WAN brokers (mosquito primarily) and had no major issues. It's worth noting if you need secure comms the NX PLCs do this, NJs don't. You'll need an older version of the library for an NJ, the latest only works on NX. It's well documented and the example program is pretty easy to setup.

I have tested it lots, I don't believe it is compatible with Sparkplug B

The NA HMI will not communicate with a Siemens PLC. You will need to do PLC-to-PLC comms and then read the tags from the NJ.

The drive likely only supports 8 PDOs.

Looks like you'll be using socket communications and embedding the barcode contents in the strings you send over. There are a few ways to do it, lots of documentation on the Zebra site for it. You'll probably want to use something like Putty at first to get the formatting and commands all sorted out and then duplicate that with the socket functions in the PLC.

1.70 is the latest. Previous versions were 1.60 then 1.43

@kckku Have you tried connecting directly to the coupler with USB and transferring from it? Just go offline with the main PLC, right click on the coupler in your Configurations and Setup section, and choose USB -> Online. You can then right click on it again and select Transfer from Coupler