ION Device Template Reference Possible update

[Charles_Murison]

Hello all,

Looking to possibly revise the ION Device template reference for the newer ION meters (ION9000, PM8000, ION7400) only. This will not replace the older .chm file but rather be an extension in a new format. Given that this is something new we have the chance to make some changes. What I would love to know from you:

A) What information are you looking for in this file? What information inside the current document would you like to see in something new.

B) What format would you like this new file? .chm is old and likely not going to be used moving forward.

C) If possible what kind of navigation would you like to see?  (Does depend on the file type chosen)

Regards,

Charles

[Tom_Stevenson]

@JamesAZZO mentioned to me the need was for # of modules utilized and the capacity of each module type and Excel as the format.  Tagging James to keep me honest 🙂

Tom

[Grant_IPACS]

Hi @Charles_Murison ,

got any examples in mind?

personally any TXT file with ALL settings is enough for us, simple, lightweight, opens with generic s/ware.

It would be good to include those advanced setting in the file too.

[Charles_Murison]

Hello @Grant_IPACS ,

Nothing set in stone yet. As Tom mentioned there has been mostly requests for information regarding the number of modules in a framework and the maximum number of modules in a version of firmware. One of the easiest ways to represent this information is in a table, possibly excel file, possibly csv file, could even be a text file or even html file to list a few. Wanted to get some feedback from others as soon as possible before too many decisions were may that would prevent one option or another.

Regards,

Charles

[kyle_coveart]

I'm not sure about the feasibility of this request, but it would be nice to see a graphical representation of the framework. Yes, I know we have Designer, but that doesn't always give a clear picture as to how the framework is constructed.

Take the Energy framework from a PM8000 for example. 

In order to see how data flows through this framework, and what modules are linked to what, it requires lots of clicking back and forth on various modules. 

The current Device Template Reference does a good job of showing each individual modules inputs / outputs and setup registers and where they are linked, but it's not graphical. 

Something like this (taken from ION Reference) would make it very easy to see how frameworks are constructed. 

Again, probably not feasible, but would certainly be useful. 

[Tom_Stevenson]

@Arneil_Dalope 

[richard_schwass]

Hi Charles,

We use this document for a number of reasons, and are kind of happy with current format as its navigable.

1) Number of modules available versus used in a given firmware/template

2) Default framework linking and settings

3) Which modules are high-speed versus high-accuracy

4) Assessing meter capacity for custom frameworks

@Arneil_Dalope @eric_tjiptadjaj  anything to add?

Regards Richard

[Arneil_Dalope]

Hi Charles,

I would like to add to Richard's list numbers 5-7.

1) Number of modules available versus used in a given firmware/template

2) Default framework linking and settings

3) Which modules are high-speed versus high-accuracy

4) Assessing meter capacity for custom framework

5) Total Processing power used for every default firmware/template

6) Processing power used of a module

7) Module Handle

Thanks,

Arneil

[Charles_Murison]

Hello @Arneil_Dalope  and @richard_schwass ,

Would you be able to expand on what you would expect to see for point 2, possibly even an example? Note that at this time a graphical representation of a framework is unlikely, maybe something in the future but at this time outside my scope.

I am not sure I understand point 4.

5,6,7 while great suggestions may take a bit longer to get rolled into the new output.

Regards,

Charles

[richard_schwass]

Hi Charles,

Have a good play with the current chm... if you expand "Detailed Framework Info" then this is what I mean.

[Yut]

I found that the ION8800C model is not up to date in the reference data recorder module is 2 but the latest model we ordered has 4 data recorders.

[Charles_Murison]

Hello Yut

Thank you for brining this to my attention, however at this time I am focusing on the HEP products (ION9000, PM8000,ION7400) for the new tool. There is a possibility of increasing the scope to other products in the future.

Regards,

Charles

[Charles_Murison · Accepted solution]

Hello All, 

Below are some screenshots at my first prototype. Any data seen in these screenshots may not exist in actual device

Summary page

Module counts

Data recorder

@Grant_IPACS

@Arneil_Dalope
@richard_schwass
@kyle_coveart 

[Grant_IPACS]

looking good...keep up the good work @Charles_Murison 

[Arneil_Dalope]

Hi Charles,

Just want to bring this topic up again.

Not sure if you end up with the spreadsheet. If you already have, can you send a copy please?

Thanks. 

Regards,

Arneil

@Charles_Murison 

[Charles_Murison]

Hello @Arneil_Dalope,

Still working on this tool to create the spreadsheet(s). I had to replace my laptop and still having little gremlins getting the tool back up and running. Still working on this when I get the time.

Regards,

Charles

[JamesAZZO]

@Charles_Murison - is there a release of this or a new ION Device Template Reference chm file? We need something with the ION9000 / 9000T in it for our planning and designs. 

[Charles_Murison]

Hello @JamesAZZO ,

The .chm format no longer available. I will contact you about what information you are looking for.

Regards,

Charles