innoaloe

Hello Michael, yes, the Data Trace is indeed inside Sysmac. You can look on the left window somewhere near to Axis Settings. We can choose what to be recorded, then start recording the data. Once we stop it, the plot will be shown (yes, the plot cannot be updated in real-time). Being a newbie is always a start... give me something other than Omron and maybe I'll lose my mind :D. In fact by looking into your project I've got a new idea for our exhibition, making sine wave trajectory control. It's not something common in automation, but in terms of exhibition is always to show-off, so something out of the ordinary is always better :D Whenever possible I'll gladly assist

The COMM indicator on the PLC should actually OFF before we're attempting any connection, eventhough the cable is plugged-in. The DIP Switch itself should be turned on, but in this case I think there is improper wire connection or pull-ups somewhere that caused the COMM Line to went High before it's time. I had similar issues when using Symbol's Barcode Reader before and still haven't found any solution to it aside from changing the Barcode Brand...

Hi everyone, recently we got a complain about UM password protection in the CP1L. So our user intended to apply password to a CP1L PLC which doesn't have battery installed. They were testing to turning off the PLC for about a week. In the 8th day, they turned it on again and tried to upload the program from the PLC. But after they input the password, and error shows up which indicates whether the password is wrong, or already inputted wrong 5 times in a row. Further checking shows that A99.12 memory was turned on which indicates that wrong password has been inputted 5 times. This was not the actual case since we make sure no one was using the PLC in those 7 days. A99.12 by its nature is not a non-retain memory. Is it possible that during Power On, the memory is unstable that it turned On by itself? I know it can be the case on some areas like DM / WR and also the RTC memory. And since A99.12 is a Read-Only memory, we cannot use P_First_Cycle to ensure it's turned Off as what we used to do with A500.12 (Inhibit Output). Currently I'm testing it by myself, for 3 days had left the PLC Powered Off. If anyone had inputs about this please advice. Thank you

Hello Michael, glad to see you've been testing it. I had seen flaws on the code that I sent to you last night... you know, brain cannot functions really well during when we're about to sleep This kind of project piques my interest better compared to machine automations actually. Of course many new things come out to the automation world, but this kind of proving theories is more fun to me. Well, maybe I can say that for now since I just finished my degree 3 years ago. I dunno whether I can say that in the next 5 years. Hahahah... Anyways, I had create another revision for the code. I don't have hardwares with me to actually test it, but the simulation result seems to be good enough as you can see on the following Data Trace result. Here I just put 3 Sine components to be seen, but actually there are already 10 components that makes the resulting Axis Position. I didn't show them all just to keep the tracing result look readable. You can look more into it in the program. I am using Amplitude and Period as the parameters. No phase shifts added so far, you can add it later on.   And just for further references on why the previous sample didn't worked : The MC_SyncMoveAbsolute only accept _mc_Aborting Buffer Mode. My previous one was using _mc_BlendingNext that's why it returns an error. A quack with Sysmac Studio is that it doesn't really limit what input are you giving to the FB as long as the data type matched, so unexpected misses like that can be expected if we're not really reading the manuals thoroughly. The FOR Loop was made from counter from 0 TO 10 to which the actual array index was 1 to 10. I forgot to set the FOR Loop limit from 1. Already fixed that in the current program The previous example was using a fixed 1 ms Timer to control time value. This was actually a mistake since I forgot that for different Periods, a Sine Wave will end on the time that is the same to its Period. The other that I forgot is also we're talking about Discrete Signal here, so the time parameter should be an increment of a certain Sampling Time. This was actually mentioned in your algorithm before. The calculation for Sine in the previous program is using DegToRad function. It was actually not necessary since 2*pi*t/T is already resulting into a radian and not degree. It was also what makes the CSine value looks weird before. I had removed it in the new program. In the new program we define first the Sampling Time, then increment the SineWave Time for each SineWave components. We need to have separate counters for that because we need to reset the time to 0 for each SineWave is reaching its Period, which should be different for each. I was using Omron newest servo, the 1S-series as my Axis in mind, that's why the encoder count is much more higher (about 8 Million). Fixed that in the new program to G5 encoder count (1048576) You still need to edit the Axis setting since mine is Virtual Axis in degree units. Also the Homing function is not yet there. It might also require another tweaks here and there. Since you're seems to quite OK with the Ladder, I changed my program to be based on Ladder also. Frankly speaking, to me the readability to human is much more easier compared to ST. Hope it helps SineControl_Rev2.csm2

Apparently there is already a new Auto-Update for Sysmac Studio, to 1.17.21   http://www.fa.omron.co.jp/product/tool/454/sysmac-studio/e1_doc.html

Well... if we're using NS of NB HMI, basically we still can use two monitors because we'll still using two softwares :D For NA HMI is a bit tricky. I usually open two instance of Sysmac Studio, save a same project into two different files, then open both on each instance. The first one is to edit the NJ, the second one is to edit the NA. For changes that I had made to the NJ project, I save it and doing an Offline Comparison on the NA project, to which the NJ inside the NA project will be updated with the changes. Certainly it's not that flexible, but still a doable workaround

Hi Justin,   1. NS10 Displaying F160 input image You'll need to program the NS10, adding a Video Display object on a screen to be able to see the F-160 image. The image is transferred from F160 to the NS10 through the NS-CA002. This connection doesn't do anything aside from displaying the camera image. You cannot get any functional data from the camera such as inspection results.   2. NS10 Controlling or Monitoring the PLC Aside from displaying the F160 image, you can use the NS10 as a control panel for the PLC. You can make buttons, lamps, number inputs, etc onto the NS10 screens to control the value of PLC memory. To send the commands, NS10 need to connect to the PLC using it's PortA or PortB. In your case it is connected to PLC's SCU21 slot Port1 through the PortA. 3. PLC Control to NS10 The Serial RS232 connection between F160 and the PLC CPU's Serial Port can be used to trigger the vision system and receiving inspection result. Triggering is done by PLC, sending commands to the F160, to which afterwards the F160 will return a response including inspection result, though the F160 must be setup first in order to do so.   Hope that helps  

We call that "Marketing Strategy". What does a PLC do again, really, if not being a controller to automate machines? :D

So, did you managed to do the Homing?

Thanks for confirming Jay, gonna go on with it now :D

Hello, I want to ask if anyone have experience on this. So I want to mount C200H-LK401 combined with CS1 PLC. But the PC Link communication is meant to be done with another C200H PLC using C200H-LK401 also. Now the thing is, in CS1 PLC, LR Address Area is converted to CIO 1000 and so on. Will the PC Link still works to C200H? Like CIO 1000 from CS1 will be mapped to LR0 in the other C200H. Thanks in advance

Hi @BobB. Yes, actually I intended to replace it to ControllerLink instead of keeping the old PC Link. But the customer is against it at the moment.

@Jay Anthony just mentioning you here in case you know something about it, since I saw you posted similar things in PLCTalk before. Sorry to disturb :D

Omron FB Library provide this _CPU012_SendCommand FB which can be used to send FINS-to-Modbus Command into the Serial Port, if it is configured as a Serial Gateway. But you still need to manually create the Modbus data to be sent, and process the receiving

There are lots of FINS samples available in the download section... like the one from me :D http://forums.mrplc.com/index.php?/files/file/1034-omron-simple-hmi_finsudp/

Ah sorry about that... I never personally checked it, since I always had CX-Programmer first prior to having Sysmac Studio :D So is that project going well?

NA does have some pre-made parts like arrows, warning signs, country flags, etc., which is not an image libraries but a Control. They're not come with button / lamp libraries if you only installing Sysmac Studio pack and not CX-One. The path you mentioned is exclusive if you install CX-Designer, which is part of CX-One software package. The reason why is probably due to Buttons and Lamps in NA already have a quite "cool" customization tool :D, which eliminates the need of adding extra image library. However I agree that time-by-time we want to give some difference to our project.

From what I know E_SYS_999 is a code for "Illegal Processing" during Runtime, and the manual only said to Restart the NA for the cure.   My guess is that the Event Lamps(178) is already called before NA enters the Main Screen, so any Language Package data is now yet available to be accessed. I might be wrong though...  

@uun sudah dikasi contoh di atas sama pak Anthony :D. Dicoba dulu ya... Ga tiap hari buka forum Already example above is the same Mr. Anthony . Try dulu ya ... GA daily open forums  

Well... now that you said that, I'm not sure anymore Let's just wait 'til he replied

For now I can only think about it as a debugging tool... to prevent us entering wrong data when we're Forcing the values. Logically speaking, we can say that a good program will prevent such Undervalues / Overvalues to happen (with combination by LIMIT Functions and so on) But when debugging and forcing the values, we can accidentally did that.

Ah... overlooked that in the screenshot. Really, these kind of minor mishaps always create confusions

Hello! Anyone here know about Fuji Electric power monitoring unit F-MPC04? Does anyone have the Communication Manual for this unit? I need to find the F-MPC Protocol which it used with RS-485. I know it is accessible via MODBUS RTU, but there is already a system exist using this F-MPC protocol. It seems Fuji doesn't publish this protocol for public, but there should be a document somewhere :D   If anyone knows please kindly reply here. Thank you

@Solheim95can you confirm that this'll work for instructions like MOVE or Mathematics? Because I had tried in simulations that it doesn't limit the value if we're using such instructions.

Unfortunately there is no easy way to do indirect addressing for bits, like the one for DM area