Skip to Main Content Skip to Search
Login
File Exchange
MATLAB Newsgroup
Link Exchange
  Blogs  
 Contest 
MathWorks.com

Thread Subject: my own enabled subsystem?

Subject: my own enabled subsystem?

From: David

Date: 14 May, 2008 15:08:04

Message: 1 of 4

I have created a plug-in replacement for an enabled
subsystem block... don't ask why, its a long story. My
only problem is that in order for it to replace the
existing blocks automatically i need to get the enable
port on the top of the block (and also not have it count
as a regular input port). I can't see how to do that with
the mask editor or other block properties... any hints?

Using r14sp2 if that matters.

Subject: Re: my own enabled subsystem?

From: checker

Date: 14 May, 2008 18:40:22

Message: 2 of 4

On May 14, 8:08 am, "David " <d...@bigcompany.com> wrote:
> I have created a plug-in replacement for an enabled
> subsystem block... don't ask why, its a long story. My
> only problem is that in order for it to replace the
> existing blocks automatically i need to get the enable
> port on the top of the block (and also not have it count
> as a regular input port). I can't see how to do that with
> the mask editor or other block properties... any hints?
>
> Using r14sp2 if that matters.

By automatically replace, you mean programmatically?
What do you mean by 'get the enable port'?

-Chris

Subject: Re: my own enabled subsystem?

From: David

Date: 15 May, 2008 10:04:02

Message: 3 of 4

checker <checkeraz69@yahoo.com> wrote in message <42513570-
768d-4ed8-a8b8-
d4af68022c86@w34g2000prm.googlegroups.com>...
> On May 14, 8:08 am, "David " <d...@bigcompany.com> wrote:
> > I have created a plug-in replacement for an enabled
> > subsystem block... don't ask why, its a long story. My
> > only problem is that in order for it to replace the
> > existing blocks automatically i need to get the enable
> > port on the top of the block (and also not have it
count
> > as a regular input port). I can't see how to do that
with
> > the mask editor or other block properties... any hints?
> >
> > Using r14sp2 if that matters.
>
> By automatically replace, you mean programmatically?
> What do you mean by 'get the enable port'?
>
> -Chris


no, i mean that i now have my own library with this block
based on an enabled subsystem with one other input and
output, i have replaced the block with my own plain
subsystem block but it shows up with 2 inputs and 1
output. when i do this and refresh the model that uses it
my new 'enable' input looks like a normal input port and
will not connect to the old enable signal that came in the
top of the old enabled subsystem block. i need to put
my 'enable' input on the top of the new subsystem block so
it will connect in place of the simulink enable port.

Subject: Re: my own enabled subsystem?

From: checker

Date: 15 May, 2008 22:17:50

Message: 4 of 4

On May 15, 3:04 am, "David " <d...@bigcompany.com> wrote:
> checker <checkera...@yahoo.com> wrote in message <42513570-
>
> 768d-4ed8-a8b8-
> d4af68022...@w34g2000prm.googlegroups.com>...
>
>
>
> > On May 14, 8:08 am, "David " <d...@bigcompany.com> wrote:
> > > I have created a plug-in replacement for an enabled
> > > subsystem block... don't ask why, its a long story. My
> > > only problem is that in order for it to replace the
> > > existing blocks automatically i need to get the enable
> > > port on the top of the block (and also not have it
> count
> > > as a regular input port). I can't see how to do that
> with
> > > the mask editor or other block properties... any hints?
>
> > > Using r14sp2 if that matters.
>
> > By automatically replace, you mean programmatically?
> > What do you mean by 'get the enable port'?
>
> > -Chris
>
> no, i mean that i now have my own library with this block
> based on an enabled subsystem with one other input and
> output, i have replaced the block with my own plain
> subsystem block but it shows up with 2 inputs and 1
> output. when i do this and refresh the model that uses it
> my new 'enable' input looks like a normal input port and
> will not connect to the old enable signal that came in the
> top of the old enabled subsystem block. i need to put
> my 'enable' input on the top of the new subsystem block so
> it will connect in place of the simulink enable port.

If I understand, you're new subsystem uses a normal inport for the
enable port, but you'd like to have the port appear on the top of the
subsystem to get automatic reconnect on block replacement.

I don't know of anyway to get a normal port to appear on the top of a
block...I don't think it's possible.

The only options that come to mind involve programatically
reconnecting the inports to the appropriate place and at first glance,
it looks messy and buggy. Sorry.

-Chris

Tags for this Thread

Everyone's Tags:

Add a New Tag:

Separated by commas
Ex.: root locus, bode

What are tags?

A tag is like a keyword or category label associated with each thread. Tags make it easier for you to find threads of interest.

Anyone can tag a thread. Tags are public and visible to everyone.

Tag Activity for This Thread
Tag Applied By Date/Time
simulink David 14 May, 2008 13:06:02
port David 14 May, 2008 13:06:02
enable David 14 May, 2008 13:06:02
rssFeed for this Thread

envelope graphic E-mail this page to a colleague

Public Submission Policy
NOTICE: Any content you submit to MATLAB Central, including personal information, is not subject to the protections which may be afforded information collected under other sections of The MathWorks, Inc. Web site. You are entirely responsible for all content that you upload, post, e-mail, transmit or otherwise make available via MATLAB Central. The MathWorks does not control the content posted by visitors to MATLAB Central and, does not guarantee the accuracy, integrity, or quality of such content. Under no circumstances will The MathWorks be liable in any way for any content not authored by The MathWorks, or any loss or damage of any kind incurred as a result of the use of any content posted, e-mailed, transmitted or otherwise made available via MATLAB Central. Read the complete Disclaimer prior to use.
Related Topics