Hello Guest it is April 17, 2021, 11:38:19 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - TeaMan

Pages: 1 2 3 4 »
1
Update.  I was able to get the correction factor to work.  I added a No Op block before the formula block and everything seemed to work fine.  Not sure why it was needed since I have formulas before this rung without No Op blocks, but that was the solution.

Still trying to get my head around the address to read RPM from Mach4 yet.  Will update if I get that one figured out too.

TeaMan

2
Modbus / Using decimals in and setting modbus address using brains
« on: May 11, 2014, 11:02:57 AM »
Good morning everyone.  I'm posting this under modbus because my brain is basically used for modbus.  I have two questions at this time.

1.  I installed an optical sensor on both my Mill and Lathe.  They are Omron EE-Sy671 and EE-SY672.  There is a slight difference in the Actual RPM and the RPM that the drive is reporting.  I need to put a correction factor into my Brain to be able to match the RPM sent with the S command from Mach 3 and actual RPM.  One of my correction factors is .93.  When I use the Brain rung putting a formula in to the run of E*.93 or E*0.93 the result when I view the brain is a number over 9000, and it runs the drive to max output.  Is it possible to use decimals in a brain to create a correction factor?  If so, any ideas?

2.  Now that Mach4 is reading the actual RPM, I'd like to also read it into my Magelis touch screen.  I need to get this value into a modbus address, so I can read it into the Magelis screen.  I have the sensors wired into a Gecko 540 board and its coming into the index parameter in Mach3.  Any ideas on how I can get this value into a modbus address so it can be read into my touch screen?

I attached my brain for reference.  The last rung in the brain is where I'm putting my formula.  I'm changing the No Op instruction to a formula.

Thanks
TeaMan

3
Modbus / Re: Problems with Modbus TCP
« on: May 09, 2014, 01:51:06 PM »
Thanks for the instructions Poppabear.  I'll give that a try too.

Brooks, where did you get your prox sensors?  I only could find one of them in the online electronic houses.

Thanks
Ed

4
Modbus / Re: Problems with Modbus TCP
« on: May 05, 2014, 09:58:12 PM »
Neat little devices.  Do you find them accurate enough to use for home switches?  How repeatable do you find them to be?

Ed

5
Modbus / Re: Problems with Modbus TCP
« on: May 05, 2014, 10:26:21 AM »
Brooks, Id be interested in the make and model of your prox switches if you dont mind.

6
Modbus / Re: Problems with Modbus TCP
« on: May 02, 2014, 03:05:32 PM »
you will probably have to do some diting, but you will have a place to start.  The speed uses the G code, S command word.  Example is S800 M3, Which sets the speed to 800 rpm and starts the spindle clockwise.  My drive had two siputs for speed per se.  The one I used was for RPM, the other is for frequency.  Hope this helps.

7
Modbus / Re: Problems with Modbus TCP
« on: May 02, 2014, 12:48:15 PM »
Take a look at the Brain I posted.  I am starting and stopping the spindle and changing directions.  I do however have to stop the spindle between CW and CCW commands, but thats OK for now.  I also have to send one command to stop the drive and another to reset it so I can start it again, it puts it into ready state.

My brain essentially does three things.  It starts and stops in either CCW or CW directions.  It resets the drive to Ready and it sends the commanded speed to the drive.  It should almost work as is for you by entering the codes into the formulas in the brain to send the proper codes to your drive.

TeaMan.

8
Modbus / Re: Problems with Modbus TCP
« on: April 22, 2014, 09:20:57 PM »
Sorry the brain didn't attach.  here is one more try.  I went with the brain mainly for speed.

9
Modbus / Re: Problems with Modbus TCP
« on: April 18, 2014, 09:44:28 PM »
On the Mach3 side, you basically have to do two things.  First, you have to go into Function Configs and go into the setup Modbus tcp.  What I did was set one config for each address.  If you have more than one address that are next to each other, you can combine them, but I didn't, it made it easier to remember what I was using in my brain.  I then set up a brain to do just what you are trying to do.  It was to start and stop the motors, change direction, and set the speed. Here is the code in my brain.  Hope this helps.

10
Modbus / Re: Problems with Modbus TCP
« on: April 15, 2014, 07:25:41 PM »
Yes I did.  I got help from various members, mostly Scott, Poppabear.  He was great to work with and really knows brains and Modbus.  I had various issues from addresses to converters to brains but got it all worked out.  Let me know where you are in your project and what issues you are having and I'll see if anything I learned will help you.  Others may be able to help also.

Ed

Pages: 1 2 3 4 »