# Casting Signal to GroupSignal - PCSDK

**URL:** <https://tech-community.robotics.abb.com/t/casting-signal-to-groupsignal-pcsdk/651>\
**Category:** Developer Tools\
**Created:** [March 10, 2006, 11:19pm UTC](https://tech-community.robotics.abb.com/t/casting-signal-to-groupsignal-pcsdk/651 "2006-03-10T23:19:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bryan](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@Bryan](https://tech-community.robotics.abb.com/u/Bryan)\
**Post date:** [March 10, 2006, 11:19pm UTC](https://tech-community.robotics.abb.com/t/casting-signal-to-groupsignal-pcsdk/651/1 "2006-03-10T23:19:38Z")

</div>

Has anyone tried working with group signals from PC SDK for 5.07?

According to documentation, it is necessary to cast a signal to its particular type (DigitalSignal, AnalogSignal, GroupSignal) before reading or writing to the signal. When I attempt to cast to GroupSignal, it fails and says it is not possible. It only lets me cast to DigitalSignal.

> DigitalSignal giMyGroup = (DigitalSignal)ioSystem.GetSignal(“giMyGroup”);
> 
> MessageBox.Show( giMyGroup.Value.ToString() );
> 
> giMyGroup.Dispose();

If I cast my group signal to a DigitalSignal, it allows me to access the value, and the value is correct. But if I try to write to the value when it is cast to a DigitalSignal, I get huge numbers written to the group signal in the controller.

> DigitalSignal giMyGroup = (DigitalSignal)ioSystem.GetSignal(“giMyGroup”);
> 
> giMyGroup.Value = 1;
> 
> giMyGroup.Dispose();

Has anyone else seen these problems when working with group signals?

---

<div class="post-metadata">

**Author:** ![Bryan](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@Bryan](https://tech-community.robotics.abb.com/u/Bryan)\
**Post date:** [April 18, 2006, 6:54pm UTC](https://tech-community.robotics.abb.com/t/casting-signal-to-groupsignal-pcsdk/651/2 "2006-04-18T18:54:04Z")

</div>

This was a bug in the initial 5.07 release. The next release will correct this problem. I tested a beta version recently and everything worked correctly.