photovoltaic

If you map a BOOL[160] as you input variable in the NX1P2 you will automatically convert the 20 bytes into bits  

I could probably find out for you - but why would you need this out of curiosity?

I don't see any sort of communication interface on those drives - I think your best bet is a pen and paper..

I can't locate the firmware for 3.20 - I checked many versions of NTST

My understanding is that your project is 3.23 but your PT is 3.20. If this is correct then you can update the system version on your PT to match the project.

It sounds like what you need is 3.23 so you can upgrade your NT to 3.23 (attached). NT-AQH0F.63C

Can you share the mmi file?  

NS screens can be converted to NA5 screens (a rough conversion). If it's a large HMI project that might be a quicker and cheaper route to go. If you need to stick with the NB most integrators should be able to do this conversion for you. You can also use a piece of software called NS Runtime and run the NS application on a PC.

FHV7 Camera EDS File View File The official EDS file for the FHV7 Smart Cameras. Submitter photovoltaic Submitted 04/01/24 Category Utilities

Download it here: https://forums.mrplc.com/index.php?/files/file/1208-nt-support-tool-487e/

It was done yes, but unless you're an experienced web designer I don't recommend it.

Yes, it's possible. Many manufacturers will have an embedded license key in a function block that must match a key entered on an HMI for example. You can do things like pull the MAC address from your Ethernet port and incorporate that into the key. This will allow for a single program instead of a custom version for each machine (with a custom key hard-coded to compare to). Obviously you'll want to secure the FB and CPU if you do this. Any advice beyond this will depend on your application specifics.

Do you still need the NS12 image for the internal CF card?

You can also use the loopback address (127.0.0.1) and this will make it so that changing your PLC's IP address won't break your code.

Yes, with VB script. There are a few ways but I would personally run a Global subroutine every second, in that subroutine you establish a time (in seconds) at which you force a screen change. In this example if the popup is the current page the script will force a screen change to "Main" after 270 seconds: Sub popTimer If _HMI_CurrentPage = "Popup" Then accum = accum+1 If accum >270 Then _HMI_CurrentPage = "Main" End If Else accum = 0 End If End Sub    

There's no native way to do this on the NA however there is a system variable you can use to check the time since the last activity. You can retrieve it with VB script: Omron.Hmi.ProjectManagement.ProjectManager.LastActivity You can then either force a screen change by VB script or if you map that variable to the PLC you can have the PLC change the screen to your screensaver page.

If you go to your IO Map and drill down to the CIF card variables there is a lot of troubleshooting info visible that might help. Also - if you can detect a comms loss you can use NX_SerialBufClear to clear both buffers. As a last resort you can also restart an NX card with RestartNXUnit. Have you tried playing with Flow Control and buffering?

So Keyence used the same module identity on 2 of their ESI files, then claimed Omron was an EtherCAT pirate ?

They will show up in your IO map where you can assign a tag of the same datatype

1: I imagine the EtherCAT Technology Group would beg to differ. Omron has 4 registered Vendor IDs with the group, and over 100 mentions in the group's media coverage, and plasters the trademarked logo on all their documentation and marketing material. I imagine there would be a few lawsuits if Omron wasn't compliant with EtherCAT and a registered user.   2. PDO is a process data object - you don't edit it. You can read or write to/from it, and being greyed out simply means the Keyence device doesn't let you customize what PDOs you access.

You will need to use the EtherCAT SDO instructions to do this. The IOL_XXXXX instructions are for Omron Masters on EtherCAT or the NX Bus. Use the SDO Read instruction first to read the current values and confirm the size, then write the correct size back with your changes.

Coordinated motion, which your PLC supports, is designed for this sort of application. It ensures "coordination" between 2 or more axis. If the slave falls out of sync if will stop both motors. Your position is as accurate as your motor tuning is setup to be. There is always positional inaccuracy in a servo system - even precision CNC machine motors are rarely "exactly" where they need to be(when you have 20+ bit encoders this becomes practically impossible to be 100% on target). The inaccuracy is called following error and you can lower this with tuning - but never eliminate it. You can also define allowable following errors on your drives. As for your question regarding acceleration and deceleration - coordinated motion is your best option to ensure the motion profiles of both motors are better aligned. Any servo though has a larger following error during acceleration and deceleration. Sysmac has some pretty easy tuning tools built in if you are using Omron drives.

What version of NB Designer are you using? Can you share the .pkg?

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