Wednesday, October 24, 2012

Oct.24 15+Interviews Summarized

Here is a quick summary of all 17 Interviews ( 30-40 minutes)  on what is needed to teach IEC 61499 standard odistributed control and automation. Next: summarize by question/topic.


.


Wednesday, August 1, 2012

Aug.1 PLC Training

If PLC programmers and technicians will use the  IEC 61499  tutorials to extend their applications to include distributed control, then looking at PLC programming classes might be useful. This can help to know..

  • ...what they know to go from their known to their related unknown
    • ... what terms do they use, what standards methods do they follow, etc
Some PLC courses listed online:
These were found via ads, google, http://www.plctalk.net

  • http://www.ronbeaufort.com/main_frame_page.htm
  • http://www.ehow.com/how_6824747_learn-plc-programming.html
  • http://www.plctechnician.com/index.php
  • http://www.thelearningpit.com/lp/doc/index.htmlhttp://www.thelearningpit.com/lp/doc/index.html
  • http://www.koldwater.com
  • http://www2.tesc.edu/syllabus/current/CTR-212/syllabus_CTR-212.html
  • http://www.galilmc.com/learning/tutorials.php?type=plc
  • alternative PAC: http://www.opto22.com/site/learn.aspx

Wednesday, July 25, 2012

July 25 LMS USB distributed too

Mainly been working on a full set of FBs for the KIPR KISS CBC v2... 
So iRobotCreate FB tests are what comes next.


But now the new LMS USB communication is working and allows distributed applications.


FBDK with 2 Simulated LEDs. and checkbox. 
If the Box is checked the FBDK LED, and  LED 1 on 2 different LMSs turns on. 
Not yet working is LMS publishing results to other devices.


Here is a first try at an LMS distributed application::
Application on the resources FBDK, LMS1, LMS2 and a Routing Resouce 


Routing Resource Application


Wednesday, June 27, 2012

July 27 CBC forte implementation

Designing the interfaces for all CBC functions except for create functions (coming) produced interfaces amazingly similar to LMS FBs for similar sensors. Motors are quite different, but not the interface. So are general FB interfaces needed, where only the insides changes or are that can be used as templates?


Forte Specific questions:
Nothing major, but need to note 

  • WSTRING and STRING data inputs and String functions like strcmp. What type conversions are needed to get it to work.  [ask in fordiac forums]
  • RSP exported like a normal input event, but it isn't [forte issue - start outside of forums]
  • CBC shut_down_in(float delay)  Delay is a time, but is type float. 1499 uses "REAL" for float, (I thought), but get type problem. Plus really should use TIME for type even if have to translate it to float. [Assume seconds, but will test and work on translation]

Wednesday, May 30, 2012

May 29 4DIAC on CBC BotBall

Thanks to KIPR for providing the equipment to perform the following test IEC 61499 application mapped to 3 devices over WLAN while visiting.
Finally a truly distributed application for demonstrating a distributed standard.
CBC being Linux based made this simplier.


Test Case:
PC has START/STOP push buttons via  IN_EVENTs. When START is pressed, a touch sensor on CBC 1 is allowed to work. When touch sensor is pressed a motor  CBC1 runs and the action is mirrored on CBC2 by a motor also running. Release and both motor on CBC1 and CBC2 stop. If STOP on the PC is pressed then the touch sensor on CBC1 has no affect. Additionally a Servo motor moved on CBC 1.
Additional test: No PC: Download application and turn off PC. Touch turns on a motor on both CBC 1 and CBC2.



Saturday, May 5, 2012

May 5 Robotic Arm app

The real task is to:

  • Arm Down
  • Claw Close (pick-up cup or other object)
  • Arm Up
  • Turn 
  • Claw Open (drop object)
  • Turn back (reset)

Currently this application is divided into 3 parts corresponding the 3 motor functions:

  1. UP/ DOWN robotic arm until Touch pressed 
  2. OPEN / CLOSE claw
  3. Turn RT/LT 
Extra E_DELAYs are used to simulate when another motor would be active.

1. 
UP/ DOWN robotic arm until Touch pressed :

2. OPEN / CLOSE claw = 3. Turn RT/LT   except for motor and led port #s

Claw Close, Stop, wait until needed again, Open, Stop
Turn  Right, Stop, wait until needed again,  Left,  Stop

Currently looking into if this is best as Composite FB or Sub-system.
The generalized version has the problem that both motor plus and motor minus end with motor stop, from the last event output its not clear if its from forward or backward.

May 5 64-bit= technical difficulties

May labs will be done with a press simulation. Posts about planned lab apps were to be posted  after the lab, but no reason to wait now.


Lab computers are 64-bit Win7. We have a driver that works, basically the standard usbserial driver labeled as ecos. However for the usb ethserial communication we have not found the right combination. Lots of others have had problems, but none found match ours close enough to help. Even the students labtops are now 64-bit.


If anyone reading this knows how to get the RXTX dlls and jar file working under Win7  64-bita please post a comment here or answer my StackOverflow question.  It appears to be the right combination of path and 32-bit or 64 bit driver, java, RXTX files, which we have not yet found.


Additionally a USB ethserial version of PUBLISH / SUBSCRIBE FBs has been started using the new layered communication in FORTE.