Hello Guest it is June 03, 2024, 08:49:41 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 - poppabear

791
PoKeys / Re: program causing pokeys to quit
« on: August 12, 2010, 10:28:34 AM »
Hey Bill,

      I think there is a conflict inside of Mach3 with the VB sleep functions.... I think Brian is looking into that, since it is inside of Mach.  There is no plugin controlled VB functions or actions in the plugin.  As far as the look up of the pokeys is concerned, I sent you my number give me a call, there is also an Unlock method in the pokeys manual....

Also, The time of the VB Sleep may also suspend the HID/USB connecxtion code, and that may make the PoKeys think it is disconnected.........  again, we (or you), could ask Brian to look into it. He moved my plugin into its very own thread in Mach3 a while back, So, he may have to look at if the PoKeys thread is/will continue to run serperate even if Mach3 is in a "Sleep" state thread.....  I dont know, the issue is a core mach3, I believe and only Brian can chase that one.

scott


792
PoKeys / Re: Bead support poKeys
« on: August 12, 2010, 10:20:55 AM »
As the saying goes:   RTFM

scott

793
you can get to the OLD serial Modbus via VB but you cant get to the new Serial Plugin or TCP modbus by VB.

But, you CAN do it in a two step process........

I.e. I highly recommend you use the Serial plugin Modbus

pull in the info to a brain, shuttle it to a DRO then pull the dro with your VB.

scott

794
what are you trying to do?  Are you trying to call a DLL from inside of a Mach plugin? or what?

scott

795
PoKeys / Re: program causing pokeys to quit
« on: August 10, 2010, 10:25:35 PM »
Hey Bill, are you running the latest PoKeys Plugin version 10.2, and the latest PK firmware?

Even if you upgrade, I would STILL be at a loss to understand why your program would make it disappear, what do you mean by disappear?

You still have my Biznesscard and phone call me at the house number tommorrow if you can, I might be able to help you through it.

scott

796
try clicking the Reverse run button in your program control, then turn the MPG backwards in shuttle mode.

BTW: nice job with your brain.

scott

797
GearoticMotion Preliminary testing / Re: Gearotica testing
« on: August 02, 2010, 08:55:40 AM »
Hey Art,

    So far it is working ok here, haven't fully tested every bell and whistle yet, but getting there.

my comp: Laptop, Vista 64 bit home premium SP2, intel core2 duo @ 2.12ghz, mem Ram 4GB.

PS........   So when you gonna add a way to do Worm Drives? With options on Straight and taper worms to remove back lash, and mabey with the driven gear with options on doing "Curved" teeth so it engages the worm more fully.........   hehehe, yea, yea, I know just could help it.

scott

798
Modbus / Re: Modbus and PLC S7-200
« on: August 01, 2010, 09:23:09 AM »
ahhh, in the Modbus Serial Plugin (any of the Modbus stuff actually), you HAVE to convert your Octal Addresses to DECIMAL address equivelants.

so for example Lets just say you have 30 registers comming in of each type.

In the plugin modbus config you would be using 4 configs

so outputs discrete would be
cfg 0, device = output coils, port/address (your com port # that your serial is hooked to), slave # (I am assuming "1"), refreash 25ms is a good start point, Address ModBus (Var) = 1 (since your discreats start at 1, number or registers 30 (max is 127), dirction Output-Coils.

your second one is

cfg1, Input-discrete, your com, slave 1, refreash 25, Address = 4097, #reg = 30, direction Input-discrete.

your third one is

cfg2, input registers, com, slave1, 25, address = 12289, 30, input-registers.

your 4th one is

cfg3, holding reg, com, slave1, 25, address = 116101, 30, input holding (you will need to divide your holeing registers in your PLC into continous blocks for holding input, and holding output, since if you have both input and output holding in the modbus is divided between input holding and output holding.

Make SURE you using 8-N-2 for the port protocol, I would recommend a timeout of between 20-50ms, make sure you tick the ModBus Run after you configure it all. MAKE SURE YOU HIT APPLY prior to going to your test modbus dialog. NOTE you test start address must ALSO be in decimal equivelants.

Now once you get the testing and you see your Inputs and outputs going to and fro to yoru PLC, the Brians is a little different monkey.  Understand your first "starting register" in that config of the Modbus is the equivelant of Brians Modbus LOCAL VAR "0" you will need to keep that in mind.

scott

799
Modbus / Re: Modbus and PLC S7-200
« on: July 31, 2010, 09:35:54 PM »
Did you use the Serial Plugin Modbus, if you want look in the "Members Docs" section and read the "Brains Users Guide".

Even though a Automation Direct PLC is used in the examples, the concept is the same.

scott

800
PoKeys / Re: Test LED
« on: July 31, 2010, 08:50:25 AM »
Frank,

   There is a Do-Able work around, if you download the PK Plugin, it comes with an example XML and Screen Set.
On the screen set (assuming you running the example PK xml), there is a PoKeys page that is set up to do testing of your pokeys.  (assumes you use Base ULED range 2000).  Their is a few rows of buttons that you can activate and deactivate the outpus you have set up as outputs, if that I/O point is an input then the Mach ULED that represents it will be On or Off depending on the Invert or not invert the inputs, you set from the pk software. For example, if you have a NO switch on a PK input, that when you close it, you want the Mach LED to light up on the PK diag page, then you will need to set that input as Inverted.

The same is true for OUTPUTS, if you want your Output to go HOT when a User LED is "On" in mach3, you will need to tick the box in the PK plugin config dialog that says "Invert outputs".

You have up to 2 serperate continous ranges you can do for inputs and outputs.

thier is ONE glitch, and that glitch is my fault on the screen sets.  PoKeys Pin 1 for instance, (in the PK internals Pin 1 is programming land is "0". So what that means is, when Pin 1 goes hot ULED 2000 will go hot, Pin2 of PK will do ULED 2001 ect....  If you set your base to 2001 they will then sink up to your PK pins but you wont be able to monitor PIN55 since the last ULED is 2054.

scott