Rockwell Activation Dongle
Lakia Limthong
FactoryTalk Activation supports Rockwell Automation's Universal Serial Bus (USB) dongles. Binding an activation to the dongle's serial number allows the dongle to activate software on any computer that the dongle is attached to.
Using a plug-and-play dongle with storage capacity allows FactoryTalk Activation Manager to automatically detect the dongle and provide the option of downloading activation files to it. The dongle can then be connected to any computer and used to activate software.
In some cases, a product's activation requires a specific dongle type. The error message Different dongle type needed indicates that the dongle in use does not support the activation of the product. The message indicates the type of dongle required, FlexNet or CmStick. Identify the correct dongle type and plug it into the computer.
If FactoryTalk Activation Manager Client computers are upgraded to Flexera version 4.04.00 or later, FactoryTalk Activation Manager Server computers must be upgraded to Flexera version 4.04.00 or later. For more information, see Knowledgebase Document ID: PN958 FactoryTalk Activation Unquoted Service Path Privilege Escalation and Knowledgebase Document ID: QA48617 Managing Remote FactoryTalk Activation Manager Servers.
The online help and release notes are available in English only. Some user interface text may still display in the selected operating system language if the operating system is set to one of these languages:
Activations that are not available, because they have either expired or not yet reached their start date, are displayed as disabled and show a red icon. Hovering over the icon displays a tooltip explaining why the row is disabled.
Activations that are no longer available because of a disconnected Ethernet card or disconnected dongle may still appear in the Available activations list. However, for unavailable concurrent activations, "n/a" displays in the Total column under Available activations. There is no indicator for unavailable node-locked activations.
This behavior is intentional, as the activations are still assigned to the device and are not available for use. If a node-locked activation is assigned to a device and the device is no longer going to be used, rehost the activation before final removal of the device. If a concurrent activation is assigned to a device, make sure that the application is closed and the logged on user is logged out so that the activation is returned to the activation pool before the device is removed.
This occasionally happens when there is a mismatch between the dongle hardware version and the dongle driver version. If you have recently updated your dongle hardware you may encounter this issue. First identified in FactoryTalk Activation Manager version 4.00.
If you have both node-locked and concurrent activations for a product, the total number of concurrent activations will aggregate the node-locked activation into its count and display an incorrect value. First identified in FactoryTalk Activation Manager version 3.62.
If you get multiple FlexNet Publisher (FNP) Concurrent and Node-Locked activations of the same feature name, the Total column in the Find Available Activations page might display incorrect values. First identified in FactoryTalk Activation Manager version 4.06.
When you rehost an activation for a computer that is not connected to the Internet, the message that appears during the Continue Rehosting step informs you to follow the steps in the Result column.
For CodeMeter activations, you cannot exceed the maximum borrowing time specified in License Transfer Configuration on the CodeMeter server administration utility. See CodeMeter 7.30 User Help for more information.
FactoryTalk Activation Manager versions 4.03 and earlier do not renew activations that have changed type from FlexNet to CodeMeter. Rockwell Automation recommends installing version 4.06, which supports renewing activations that have changed type from FlexNet to CodeMeter. If upgrading to version 4.06 is not possible, perform a rehost of the original activation and a get of the renewed activation for the activation type.
Expired FlexNet activations do not appear on FactoryTalk Activation Manager running on client machines. This behavior is by design, because expired activations cannot be acted upon from a client machine. On FactoryTalk Activation Manager running on a server, activations that are not available, because they have either expired or not yet reached their start date, are displayed as disabled and show a red icon. Hovering over the icon displays a tooltip that explains why the row is disabled.
To borrow CodeMeter activations correctly, the date and time settings of the client and server computers must match within one minute. If the date and time settings do not match, unexpected behavior occurs, such as the failure to activate valid licenses.
Borrowing or returning CodeMeter activations generates only a client diagnostic message. However, borrowing or returning FlexNet Publisher (FNP) activations generates both server and client diagnostic messages.
Rockwell Automation recommends using FactoryTalk Activation Manager exclusively to make updates to the server search list. If using CodeMeter Web Admin to update the server search list, the updates may not reflect accurately in the FactoryTalk Activation Manager search list.
When using a remote desktop connection to a client computer running a Windows Server operating system, borrowed CodeMeter activations are not displayed, borrowed activations cannot be returned manually (they are automatically returned when they expire), and products relying on the borrowed activation cannot be activated. To work around these limitations, log into the client computer directly. Rockwell Automation recommends not using a Windows Server operating system on a computer that uses borrowed activations or points to a FactoryTalk Activation server.
If the VeriSign Universal Root Certification Authority certificate does not exist on the local computer, the certificate is installed while installing Rockwell Automation software. Use Microsoft Management Console (MMC) to view the certificate in Console Root > Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates.
The following table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").
got an ipad pro 2018 and plenty of audio interfaces. I like them and obviously i use them to connect my hardware synths to the ipad for audio & midi.
I use them as well when producing in aum and ios soft synths only - principally because it gives me that sensation of "professionality". But is there ANY - i mean even the slightest - advantage in doing so ? Quality- or latency wise ?
personally i'm not able to hear any difference over using the apple usb-c to headphone adapter. thanks !
@richardyot said:
On newer iPads an audio interface will give you control over sample rates rather than locking you in to a specific rate of 48k which happens when using the Apple headphone dongle.
the practical reasons (midi/audio in) are clear to me, thnx. The question was related to "producing in the box" only. And if the audio out of the ipad (usb-c to minijack) is worse in quality than it would be with a usb audio interface, when for example connecting it to a mixer or external audio recorder.
an audio interface with good D/A will certainly sound better than the headphone dongle. I've A/B'd with a decent interface (Audient) and noticed a considerable difference, especially in terms of clarity of the low end and less brittleness in the upper mids. If you're doing long sessions, your ears will thank you. If you're simply dabbling here and there, then you're likely overthinking it.
My main ios interface is the ica4+ (due to it's midi capabilities and ios friendliness). it doesn't have the best DA conversion by any stretch, but it's still noticeably better than the headphone out to my ears.
You say you have "plenty of interfaces". you have all the tools.. Why not perform a test yourself? Quash this fomo with a simple listening test. Without knowing exactly what your setup is (what headphones, monitors, etc... you are using. are they set up correctly, in a room that is treated well enough so that they can perform accurately?) it is more or less impossible for anyone on a forum to tell you what will sound best for your needs.
@palms said:
an audio interface with good D/A will certainly sound better than the headphone dongle. I've A/B'd with a decent interface (Audient) and noticed a considerable difference, especially in terms of clarity of the low end and less brittleness in the upper mids. If you're doing long sessions, your ears will thank you. If you're simply dabbling here and there, then you're likely overthinking it.
thanks mate, yes i own a motu, iconnect and some older interfaces (focusrite, novation) For now i'm working with headphones only (AKG 701).
Well in this case it's my ears - i cannot hear any difference. maybe i should try for longer sessions and with some different synths.