Jump to content
OMRON Forums


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

seltmann's Achievements


Rookie (2/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter

Recent Badges



  1. Yes, I should have given more infos ;-) So M169 is defined as "M169->D:$90" and gives back values according to the compensation table. I thought the table would roll-over outside of the given range, so I don't understand your comment with "in the range". I can see the compensation table is recognized, but how can I see that it is switched of when I set I51=0? I want to compare the performance with and without compensation table and I don't see a big difference, so I wanted to make sure the switching is working.
  2. I'm wondering how to see the effect of the compensation table on the motor. I'm using I51 to switch between 0/1 and thought I find the effect in the difference between M161 and M162 or maybe in M169. However these don't seem to change. The compensation table is defined as: #1 DEF COMP 2438,#1D,#1,16384 ... Where can I find this?
  3. I finally came around to check the risetime, since the problem reappeared. I see a risetime of 3.9ms with linear voltage increase over several powercycles. Since the manual states "minimal 5msec" I think I'm fine in this regard?
  4. Ok, I checked the power supply and raised its voltage even a bit but no change yet. I'll try to measure the risetime somehow. Unfortunately the system is in use most of the time, so I can't just do changes/measurements there at any time. Another thing occurred to me when I tried to check for voltage changes. When I have just cold started, Device Manager shows "Delta Tau UMAC USB 2.0 Device No EEPROM" and PeWin says "no connection possible", I usually use EthUSBConfigure.exe by pressing "Store IP" and "Done". Then PMAC dissapears from Device Manager and I have to replug USB cable to find "Delta Tau PC104 USB Device". This time I just pressed the red cross for "Close" by Windows without pressing "Store IP" or "Done" and PMAC dissapeared from Device Manager again to reappear as "Delta Tau PC104 USB Device" after replugging of USB cable. How is this software working when even closing leads to a change?!? A simple replugging of USB cable without using the software isn't changing anything of course.
  5. I'm using a setup with: CPU (80 Mhz) ACC 1P ACC 2P (with USB and Ethernet) I'm having problems reestablishing an ethernet connection to the PMAC. After cold starting the PMAC I can't ping it at its usual When I connect my Win10 via USB the PMAC is identified as "Delta Tau UMAC USB 2.0 Device No EEPROM" in the Device Manager. I can use the EthUSBConfigure.exe (from PMAC Executive Pro2 Suite to set the IP, Protocol (TCP 1025) and the "H/W Type" (PC104) with a click on "Store IP". After replugging the USB cable the Motion controller is now identified (correctly): Delta Tau PC104 USB Device. At this point I can finally use PeWin32Pro again or even ping the PMAC, however after a cold start of the PMAC the set parameters will be lost and the Device Manager shows "Motion Controllers: Delta Tau UMAC USB 2.0 Device No EEPROM" again. Can you help me with the setup please?
  • Create New...