LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

I want to control a telesis pinstamp using labview has anyone done this?

The pinstamp is a Telesis TMP6100 that is being controlled by a Telesis TMC090 controller.  The computer communicates with the controller via USB.  I need to integrate the pinstamp into an existing in-house VB software package and would like to write a .dll in LabVIEW that would allow the existing VB code to call it with as few changes as possible to the VB.  I did get an activeX add on from Telesis but it came without any help files or variable definitions.  Telesis seems to want everyone to use their Merlin II software that is also included but I am trying to apply a little K.I.S.S. theory to my already overgrown project.  Any suggestions?
0 Kudos
Message 1 of 10
(7,788 Views)
Hi.  Thanks for contacting National Instruments.

As I understand it, you would like to communicate with a third-party USB controller through a *.dll in LabVIEW.  This type of communication is certainly possible, but USB commands are device-specific, so Telesis would have to provide the command set for that controller.  This KB details how to communicate with third-party devices and includes some helpful links.

If you can get your hands on the command set, the rest should fall into place.
Lorielle P.
Applications Engineer
National Instruments
0 Kudos
Message 2 of 10
(7,770 Views)
Hello G.A.G.,

Did you manage to get anywhere with your Telesis pinstamp? 

I have a TMC420 to integrate, and I was wondering if you were able to find any resources online.

Thanks.
---------------------
Patrick Allen: FunctionalityUnlimited.ca
0 Kudos
Message 3 of 10
(7,703 Views)

I managed to get a .dll written in LabVIEW that interfaces with the Telesis Merlin II software.  This is not what I wanted but when I started with the Telesis supplied SDK and emailed a question to Telesis with some sample code, I was told that I was somewhere where I wasn't supposed to be and that it was being referred up the ladder and that if I needed to contact them again, I would have to go through my co-worker (the engineer who was heading the project).  (I know, I had exactly the same look on my face as you do after reading that)  Since then, we have had two of the TMC-090 controllers in simple production roles and have had nothing but problems with them (I have not implemented my .dll for this reason).  I just heard the other day (after being called out to the floor for a problem) that according to the distributor we bought our Telesis products from, we are not the only users having trouble with the TMC-090.

Personally, I don't think that Telesis has anyone in their employment that knows enough(about their TMC-090 or programming or LabVIEW)...that guy left during our early stages of development.  I know this because I waited for him to return an answer to a question for about 3 weeks, then found out he didn't work there longer.  My advice to anyone thinking of using Telesis to keep thinking until you have a plan that doesn't include them...as much for you own sanity as for the dependability and consistency of your production line. 

0 Kudos
Message 4 of 10
(7,688 Views)
Thanks for the info. 

I am only the lowly integrator on this particular project.  All of the hardware has already been chosen and purchased by others.  I'm also pretty sure it was our customer that spec'd out the Telesis unit. 

After reading the documentation and getting a little better feel for what the equipment needs to do, I think in this case we'll be fine using the Telesis controller to setup the markers and then just use digital I/O to provide a method for LabVIEW to have control and feedback. 

Hopefully our customer is fully aware of the problems you mentioned and have technical staff on hand to deal with them.  This machine is being delivered a long, long way from home and warranty service calls are going to be very expensive.

Thanks again.
---------------------
Patrick Allen: FunctionalityUnlimited.ca
0 Kudos
Message 5 of 10
(7,682 Views)
There are two ways to comunicate with a TELESIS controller: Programable Protocol for simple one-way comunications and the Extended Protocol that includes error checking and transmission acknowledgment. Both are described at the last page in the Product Data Specification Sheet Download.

Now, there is an ActiveX available to use the Extended Protocol, the Extended Protocol ActiveX Control Download.

With this ActiveX is possible to send commands to the TELESIS controller, and get response when available.

I'm using a Telesis TMP1700 that's being controlled by a Telesis TMC420 controller, and i succesfully got the status, restarted and put online the controller.

It is possible using an ActiveX Container then Insert an ActiveX Object wich is the Telesis Extended Protocol Control. THe next picture will be seen in the Front Panel.


you can change the serial port configuration by clicking on it.

The next step is crating Invoke Nodes to use the methods.

The included file was made in LabVIEW 7.1, and it only request the status. It's necesary to change the command (Type) depending on what you want to do. Check the Product Data Specification Sheet to do this.

It's all i know by two days working on it.


Message Edited by G1L on 07-03-2008 08:08 PM
Message 6 of 10
(7,473 Views)

I am also trying to send data from VB to Telesis machineMNC420 but no luck.Kindly guide me and provide me some tutorial or sample code to send data.I am also unable to free download LabView7.1

                                      Kindly guide me

 

Thanks in advance

 

 

0 Kudos
Message 7 of 10
(6,117 Views)

Hi nikstheonlyone,

 

I could not find a MNC420 that Telesis’s makes. Perhaps you mean one of the TMMxxxx/420 or TMPxxxx/420?

 

Anyway, it looks like from G1L’s post that you can use activeX control in LabVIEW to interface with the Telesis machine; however, I could not find any examples of doing this besides what he posted. Maybe some of the other posters’ in this thread have something they wrote, but it is a four year old thread so they may not see your question.

 

In regard to your question about a “free” version of LabVIEW 7.1, we do not have one for LabVIEW 7.1 (as it is quite old) but we do have a 30-day trial of LabVIEW that you can download at http://www.ni.com/labview and then click on the Download LabVIEW link.

------------------------------
Bill E. | Applications Engineer | National Instruments
0 Kudos
Message 8 of 10
(6,100 Views)

As Ever Song pointed out, you need to downlad and install the ActiveX to be able to communicate with the TELESIS. Once you install the Extended protocol, you'll be able to read the help file that comes included in the install package. There is all the information about methods and properties to use the ActiveX.

 

There is a little code a used some weeks ago to update some serial numbers to be stamped, and start the stamp by the serial port.

 

Private Sub Form_DblClick()
Dim a As Integer
    Dim TLSSString As String
    FrmPrincipal.TELESISComm.DisplayErrors = False
    FrmPrincipal.TELESISComm.ResponseTimeout = 1000
    FrmPrincipal.TELESISComm.BaudRate = "19200"
    FrmPrincipal.TELESISComm.DataBits = 8
    FrmPrincipal.TELESISComm.StopBits = 0
    FrmPrincipal.TELESISComm.Parity = 0
    FrmPrincipal.TELESISComm.PortNumber = 10 'COM10
    a = FrmPrincipal.TELESISComm.SendWithResponse("1", "01" & PartNumber, TLSSString)
    Delay (0.2)
    a = FrmPrincipal.TELESISComm.SendWithResponse("1", "02" & "1T" & Right(PumpSN, 9), TLSSString)
    Delay (0.2)
    a = FrmPrincipal.TELESISComm.SendWithResponse("1", "03" & PartNumber & "1T" & Right(PumpSN, 9), TLSSString)
    Delay (0.2)
    a = FrmPrincipal.TELESISComm.SendWithResponse("G", "", TLSSString)
    Delay (0.2)
End Sub

 PartNumber and PumpSN are the data to be stamped

 TLSSString is a empty string or ""

 

Regards

0 Kudos
Message 9 of 10
(6,084 Views)

i need help  step by step video or photo to how connect to TMC420 control with pc please with program and drivers attached

0 Kudos
Message 10 of 10
(486 Views)