Jump to content
OMRON Forums

Sanjay

Members
  • Posts

    12
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Sanjay's Achievements

Apprentice

Apprentice (3/14)

  • First Post
  • Collaborator Rare
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. I ran into similar issue with Yaskawa drives. I fixed it by opening up the Yaskawa ESI file matching the drive and then changing the data-type on the torque entry from UINT to INT and then re-importing the updated ESI back into PowerPMAC IDE. After that, the data was mapped correctly into the PowerPMAC as a signed integer..
  2. Hello Jeff, My suggestion would be to write a little parser program that can read each line from the "new" format of the config file and then only write it out to the destination file if it would be valid for the "old" firmware...
  3. I think it was the KB4601887 update (Cumulative Update for .NET Framework) that broke things as acknowledged in the Microsoft notes for it.. It mentions that crashes can happen "when disposing an HwndSource whose RootVisual is null, a situation that arises in Visual Studio when docking or splitting windows, and could arise in other apps." Workaround This issue was resolved in KB4601558 for .NET Framework 4.7.2, and KB4601555 for .NET Framework 4.8. I'm seeing KB4602298 (Cumulative Update Preview for .NET Framework) listed as an update on my Windows 10 PC which seems to incorporate these two fixes. Installing it resolved my issues with the PowerPMAC IDE crashes. More details here: https://www.bleepingcomputer.com/news/microsoft/recent-windows-10-updates-cause-visual-studio-wpf-app-crashes/
  4. There's an app note that DT had sent me that helped me tune EtherCat DC loop using the Hystresis method. It seems to be more stable on my Ethercat loops using the Hystresis instead of the PID loop. Can't find a link in the file depot to it but here's a Google Drive link that you can try: https://drive.google.com/open?id=1VyeOB1VnxRnFvEtjV4i6UEw8oe0r01PL
  5. I've found that the IDE sometimes seems to throw this error but if I just immediately redo a second 'Build & Download' or just 'Download' it will often work the second time around.
  6. FYI - This problem still exists in Version 4.4.1.7 (latest one). Extremely annoying to have to restart whole IDE each time.
  7. Is EoE capability on the roadmap for the IDE (or is it somehow possible to do already)? It would be extremely helpful when doing remote diagnostics and startups. I'm looking to be able to use it with CK3E/CK3M and Yaskawa Sigma7 Ethercat drives or Copley Ethercat drives. Since Acontis already supports EoE, I would think it should be relatively straight forward to add like the IDE added FoE a couple releases back...
  8. You need to update the various pages on the website. For example, the Contact Support webpage still shows @deltatau.com: http://www.deltatau.com/DT_TechnicalSupport/ContactSupport.aspx and also the offices list: http://www.deltatau.com/DT_About/aboutCorporateOffices.aspx
  9. Is there any single document somewhere that lists all the products that have been CE certified and have declarations of CE conformity?
  10. Perhaps there's a newer version of the PcommServer manual out that I'm not aware of as there's no section like that in my manual. Can you let us know what is revision date of latest PcommServer manual? I don't see any revision # on my version but there's 108 total pages.
  11. Are there any API calls in the PCommServer library that can do the equivalent of the Backup PMAC functions in the PeWin32Pro software so that we can integrate that into our application?
×
×
  • Create New...