Recent content by HamsterKing

We recently replaced a SDCCG5A card and noticed this jumper JP23 was also set at 1/2. It was set at that on the old card that had been operating for years and we left it like that on the new card. The other two control processors were set at 2/3. As a side note when we changed the SDDC card...

This was something I found in my notes for creating a push button in Cimplicity. It looks like 16 hold the input for one second.

Eldorado; I don’t have my notes with me for a better explanation, but like WTF? said it’s the time cimplicity holds the point true to send to the MarkV. 16 is the standard and I believe32 is the max and is 1 second. So 16 holds the value for 0.5 seconds. I have seen one that was set at 1 and...

That makes, I missed that. Always learning that’s why I look on here. Thanks

I would think it should. But on the unit I’m looking at the Emergency over speed sensors only go to P core and are not referenced in the csp. The original poster says his is not tripping with two failed sensors.

Would be nice to know what control system this was operating on. Also I would think if you had two emergency OS probes fail it’s a big risk not to shutdown to replace them. I believe if it’s two out of three and you lost two then a third won’t make a difference. The documentation I have for...

Mauricio; Your probably waiting for CSA's response. But here is mine. If you already created an internal point in the logic for DTKLT for testing then that is why the it says the point is in there twice. If you followed your flowchart for creating an internal point you would have entered the...

Mauricio; On all of our units on all controllers the I/O config. Failed comes on the display for a second before it gets to A7. It has caused confusion before in the past here as usually you only pay much attention to it when your making a change and you think you did something wrong. I don’t...

All; I looked a little more and think the values in the MarkV are stored in the prom chip on possibly the SDCC card or other card. Attached is a pic of the PROM_REV file and it shows those curve blocks in the prom revisions and lists chip revision numbers. This possibly goes along with what...

CSA; I think my previous post was misleading. I can see the block in the dynamic display as well as the csp.prn. I was trying to communicate that I cannot see where the values for the array come from. casey.little seemed hopeful he would find the table values in the live logic when he got...

I can't be much help on this but have been following it. We have the same block in our MarkV's and I cannot find the 3D table either anywhere. I went online with unit and still cannot see it in the rung display. I looked in control spec and it has a brief description of how it works and a...

Hi, Not great at French but attached are a couple docs on gas valve calibration and voltages, if thats something your after.

I would say, from looking at logic examples and the description, the Integ_In is suppose to be the output to the valve to provide a bumpless transfer when switching from manual to auto. In the example I looked at the OUT does not go directly to the valve but to a compare block that would allow...

Cheedees question was how to get the numbers directly from the MarkV as they went with a different hmi and not Cimplicity. I provides an explaination that I currently use to get the numbers into our PI system, I just figured it out reading this forum form using the search feature and looking at...

If you want to check the number directly in the markv, look in the file TOTT_Q.src and count down to the timer you want. For example our total fired timer is L30FT_T, and it is the twelfth one down the list. Now go to demand display and look up ACCUM_12_MSW and ACCUM_12_LSW. Math equation...