lamboom

MrPLC Member
  • Content count

    157
  • Joined

  • Last visited

Community Reputation

2 Neutral

About lamboom

  • Rank
    Sparky

Profile Information

  • Country United States
  1. NJ controller firmware upgrade.

    Perhaps I can help ..  I said earlier .."And, I'm going to Omron to get away from Siemens."   This implied no comparison between Omron NJ and Siemens S7-1200 .. they are quite different after all...  However, where they are NOT different, Is the complex and expensive manor that firmware upgrades are performed ...  I think Crossbow thought I was comparing the CPU's 
  2. Thanks for the reply Joe PROBLEM SOLVED... The reason was not expected .. and worth sharing.    There were many good articles out there on how to manage the Windows Firewall .. but that wasn't the problem. There were two identical computers, each was to be able to communicate with the HMI (not at the same time)  One could do it, the other could not. The HMI's IP address is set by configuration software created by the PC, and downloaded to the HMI.   That IP address was 192.168.0.20    Neither of these two PC's had made the original download.   I looked at the LAN static IP address for both PC's, and it was 192.168.0.105 Then I checked (using NetSetMan) the IP address of the PC's WiFi ... One was 192.168.0.19 (the PC that worked) ... and the other was 192.168.0.20 (the one that didn't work) Could there be a conflict?  Two different networks: one trying to communicate with to an IP address over LAN, which is the same as the PC's WiFi  DHCP IP Address?    REALLY? So I turned off the WiFi (little switch on the side of the PC),  Powered Cycled the PC ...  And The communication worked. Well, I liked having the WiFi active .. almost never turn it off   So, I re-sent the HMI configuration software with a new IP address for the HMI: 192.168.0.25  And now both PC's communicate just fine with the HMI.. with the WiFi on and working too... PS.. I do have to turn the WiFi off when running a full Virus Scan with System Mechanic .. otherwise SM will crash .. but that's another story.  
  3. This is a problem that shouldn't happen .. It may be due to a defective Network port in the PC. Basically, it's easy to connect to Red Lion G3 HMI's.. using USB, or Ethernet.   Unfortunately there is a flaw with the G315 processor.. and you cannot connect with newer PC's via USB .. and there is no FIX.   However, connecting via Ethernet should be quite easy .. and, I'm able to do it with several old and newer PCs' .. EXCEPT one:   A Dell Latitude E6410.   I don't need help with the Red Lion programming to enable Ethernet communication via TCP/IP ... That's kinda straight forward. (sorta) What I need help with is... what's wrong with my PC ..?  sniff!      I have two similar Dell's  .. one is an ATG model... I've set the fixed LAN IP address the same in both (192.168.0.105).. and I've set the HMI's Ethernet port (789) to an address in the same subset: 192.168.0.20  ...   The E6410 ATG communicates no problem.. the other E6410 ..communication fails.  Everything seems identical in both PC's (well... not totally .. the LAN cards might be different) Anyone ever had this connectivity problem where only one of two identical PC's can connect via Ethernet? Thanks Much... PS: perhaps a suggestion on troubleshooting a LAN Network card? OR..Firewall blocking the HMI connecting...  ?  
  4. INNO  .. You are awesome...     I just tried writing that program yesterday.  Tyler Corbett (Omron Engineer, Canada) told me about "SetVariable" yesterday.  I can't believe I missed that when I looked over the list of "Actions" in "Events and Actions" ... (I have that same problem when I'm looking for a specific item on a menu ... sigh!)     My first attempt WORKED!    .. I didn't try to make the NJ side variable to go FALSE when the page does away .. you just showed how to do that ..  my first job this morning, with coffee ..       Life truly has meaning Tyler also presented some good info on going the other way.. where the NJ is controlling the pages on the NA HMI ... Nice!
  5. OK.... One last way of saying it: Special_NJ_global Variable := TRUE  when Special NA globalVariable is TRUE  IF "PageName" is _HMI_CurrentPage   ... How hard can it be?  Yes, I know the above expression is bogus.. but, it makes the point......  
  6. On Page 8 of NA Practices Guide ..Omron manual V422-E1-01 .. Last question:  "Is it possible to switch the screen from the PLC? Is it also possible to report the current screen from NA to PLC?"     Someone asks  a two question, question, and this is the only answer: "On the NJ, specify a String-type variable and assign it to “_HMI_CurrentPage”, a system variable that specifies the current screen. You can change the screen by entering the name of the destination screen in the variable assigned to the system variable. If the address values are directly linked with the page numbers as in NS series, you must write Visual Basic". This answer probably means something to someone who already knows how to do it ... but, it's not much help for me.  I get that you create a String-type variable: select STRING[256] under the Type column.. But, what does it mean to "assign it to this system variable: "_HMI_CurrentPage"  .. the answer seems only to answer the first question, and ignores the second question.. which is the one I'm interested in....  Do you know the answer to the second question?  PS: I think it's in the NA's Variable Maping .... working on it... EDIT.... Nope.. nothing there.. that's just for calling pages from the NJ software...   I want to work with input variable data, and display of resulting variable data on that same page; because, the input data creates the output data.  an' I don't want to push some "Equals" button that activates an ST rung.. I want the ST rung to be auto activated by the "existence" of the current page ... "_HMI_CurrentPage"  or something like that....???   Thanks, Micheal
  7. More Example: I’m going to make a Regular Wave, I input 85mm for a height, and 0.68 seconds for the wave period.  instantly, if something is already in the SCALE data input (200), the Full Scale Height in Feet (55.8), and the Full Scale period (9.62) would be quickly displayed in the data display windows… yet the axes hasn’t run yet  (Start Regular Waves) …    How can I get these Full Scale data displays to work before the axis is run?      PS:  You can see that they work fine, after the axis is run …. .. thanks to memory of variable data….  
  8. You sayin' I would have to use Visual Basic to create a script to make a special variable TRUE  ... hmmmm...  what's the indicator in software, that a particular "page" is "ON, or TRUE ? (remember I'm a bit of a newbie here.. sorry     FYI.. I did finally figure out the last 2 wave sequences, with some Tsunami help from "Dirt" on PLCs.net https://www.youtube.com/embed/B0UGm9JTw3U?rel=0  
  9. Thanks Crossbow .. I remember reading something like that .. You have to map page numbers 0.1.2...  to the page names ..  It wasn't real clear how that would help do what I wanted.    But, that idea of a "script" that turns on and off looks good...  I'll research Scripts in those manuals... I'm looking for a way to set values or binary states to variables, depending on what "Page" was displayed on the HMI ... As an example, when I input values on a page like "wave height", and it might be in feet,  There would be another data display object (on the same page) that indicates the height in millimeters; however, that display in mm, would be based on a "Scale" factor.... like 1/200  or 200.   "Scale" would also be a data input on this, or other HMI page.    I would like the data displays to be "live" .. so that when a scale and a wave height is input as data, the wave height in mm, is displayed.    No axis program is running yet.  The HMI page is live for inputting and displaying variable data; but the CPU isn't doing any servo controlling ... I need a way to display variables that are calculated from inputted variables.  I need a small program to go live when a page is displayed, and always be calculating, and displaying different variables on the same page.         Basically, you input something, and other data displays on the same page, change in response.   Because, they mathematically depend upon the values of the variables you inputted. I would like to see them, before running the axis.    
  10. Hi.. an easy question.. which I can't find an answer too .. in the 2 manuals:  V421 and V422 ...: "Can you make a variable that goes TRUE when a particular page is selected, and "live" on the HMI screen?" Yes, it's easy to map NJ variables to the objects on the HMI pages...  Yet, It's not clear how to create a variable for a "specific page".. so it is TRUE when that page is on screen. I'll keep looking .. and post what I find, in case no one posts the answer ... thanks   Regards, Michael
  11. The fix is two fold:  1) the equation for only 1/2 cosine wave, is not practical, in that in one cpu cycle the position can go from + PeakMax to zero... The position equation must have a few extra points past peak + position ... so, this part of the equation:  SIN(Pi * Sine_Time ....  should be SIN(2 * Pi * Sine_Time ....  or at least 1.1  ...Just to let the IF-THEN statement catch the peak, before it drops to zero. 2) Best to use the ST version of incrementing the StateTracker variable rather then ladder in the adding of different cosine waves in series...  The ST: Inc(StateTracker) will get you out of an ST series, and into another ST series if needed.   But then, you already knew that if you took the Omron classes ...      Thanks for looking .... Regards, Michael
  12. STATUS:    Changed to using State Trackers  .. That worked well .. No clunks, and the sequence runs fine; but, only up to a point.  There is a point at short periods (0.3 sec) to the positive peak of the cosine ramp up, when the control fails and the linear motor runs away negatively into the hard stop. (have nice shock pads for that..     This may be due to the position equation itself.  By creating only 180 degrees of motion mathematically ( SIN(2 * Pi * Time increments/Period) + 270 degree Offset)  The 2 is not in this equation)  The equation is only for a half cycle...  perhaps it should be in the equation... or something a little larger than 1 .   Because, the "end" timing is too critical.  In only one CPU cycle, (0.001sec) the curve will go from + peak(max) to zero!.     Probably, better to make the cycle go slightly past + Peak(max), but try to catch the + Peak(max) with the IF-THEN statement.   UPDATE:   RESOLVED... both Tsunami and the Rogue wave series: Found a way to use Inc in ST ..  makes for easy jumping to various states.. or stages..     Thanks all!
  13. UPDATE ... This works... Sort of: The ST and the MC_SyncMoveAbsolute fb start at the same time, when the peak + is reached, StateTracker is incremented to #1), Stop_Tsunami goes TRUE, (rung 32), TCosine_Start goes FALSE (rung 29), and T-Hold goes TRUE (rung 30).  FB_SyncMove is disabled: After 6 seconds of Hold, increment State Tracker to#2, which  enables Tsunami_ReturnRamp Fb, returning position back to zero: Tsunami sequence ends, MC_Stop is activated, and StateTracker is reset back to #0   This works nicely .. but it isn't with a flaw .. somewhere..   For TsunamiPer longer than 0.3 seconds, everything works as it should.  Shorter than 0.3 seconds, (higher velocites, and decelleration ...  The linear motor's slider, when first stopped at the peak + position ... doesn't HOLD, it moves quickly negative to the hard stop...and there's a FAULT .. Could this be due to the way MC_SyncMoveAbsolute is "Switched Off" ?      Here's a trace from the LinMot drive: Not too bad.. 0.4 sec. rise time to peak of 60mm... But look at what happens at an attempt at 80mm in 0.4 sec: It does it... but control fails at the transition to "Hold" ... so much for holding,  .... YET, the NJ has no problem keeping control of a 154mm sine wave at 0.4 sec. period ..... To be continued     
  14. Tried some other options .. also didn't work well .. one thing for sure,  the equation for FSine_Tsunami is correct ..it provides a new position every 1.0ms to the LinMot Drive.. That part is working well.. just things go badly after the position equals (2*Amplitude) .. the peak to peak value of the 1/2 cosine plot. Using an IF-THEN to jump out of the position calculation.. Turn off the ST (which is not a good idea.. but, what else)  The T-Hold starts a timer for 4 seconds, below: Turning off Tsunami_Run also kills Delay_Timer.Q .. which powers off the MC_SyncMoveAbsolute with brute force .. probably should use MC_STOP,  but that brings problems too. This causes the linear motor to jump a little in the negative direction, but 4 seconds later the MC_MoveAbsolute fb kicks in and the position ramps to zero or Offset, if an offset is selected.   After the return to zero, MC_STOP is activated by TON: MC_Stop is reset by TON:   This still doesn't work... because there isn't a way, known be me.. that will permit this sequence of moves to be done in 3 stages.  Omron doesn't have stages.. but, it does have tasks... perhaps, i should look into that more closely... to be continued..          
  15. Hi..  Still Trying to make this Position curve: Pay no attention to the glitch (arrow)  it's a different system (Think of it as inches not volts) .. this pic just shows what I would like to do with the NJ and a linear motor .. It's like 3 parts. first is a cosine move from zero to peak-to-peak (2 * Amplitude) of a position data stream from a MC_SyncMoveAbsolute fb.  The position holds for a few seconds .. then an MC_MoveAbsolute ramps the position slowly back to zero. How hard could it be ... Here's where I am so far: set variables and select for an OFFSET if required:   Equation (6) generates the cosine position move .. the trick is to stop the equation when the max positive peak is reached.  IF-THEN tries to do that (TLim is a small value 0.001mm)  to make sure it's possible for FSine_Tsunami to be larger than 2*TsunamiAMP .. T_Hold starts the TON, and TsunamiRun (the command that started the sequence) goes FALSE.   Line 10 does stop the equation at the right time ...  it's what happens next where all hell breaks loose.  The next trick is to HOLD that last position for 4 to 6 seconds.  This just won't happen because there is no way to stop line (6) of the ST.  No way to freeze a position while still using the MC_MoveAbsolute, stop using it, and transfer control to a MC_MoveAbsolute.    This is my Question ... Delay_Timer.Q goes FALSE because Tsunami_Run is now FALSE (Rung 21)  This messes up the axis control by the MC_SyncMoveAbsolute fb. and the linear motor jumps negative a little; However, 4 seconds later, the MC_Move Absolute kicks in (RUNG 31) and returns the linear motor to zero (or Offset, if selected): Everything gets Reset by rung 33 & 34 Sooo.. this program doesn't work, and is certainly not the best way to make the position curve..   The one thing I could really use help with, is how to jump out of an ST equation for a Global Variable that's being generated by the MC_SyncMoveAbsolute .. hold the selected last position.. and transfer control to a MC_MoveAbsolute, to ramp back to zero or Offset. Regards, Michael Update:  this same post on PLCs.net has over 2200 views .. and, I did get some good help there (equation (6) for example .. unfortunately methinks there are no Omron engineers visiting PLCs.net very often.    Most Omron Engineers are very busy, and I can see why.  You do have to do some serious training at Omron schools, and years of internship .. there must be very few Omron Engineers out there.  I didn't know this, when i started the Omron project... sorry)