CrestronMobile ParseDataElement Error

[edch1041]

hello,

i'm using the latest crestronmobile sample programm from this site to test the communication between crestron and cf via crestron mobile.
i'm using a mc2e (v4.3.15) as control unit and iviever4 (v4.0.196 build 196) for the visu.
the communication works fine, i also get all joins to the ipad. but in my control unit the error log get filled up with following message:
"Error: ParseDataElement Error - Not Data Value"

does anyone know about this error message?

greets
christoph

[GregSoli]

Hi Christoph,

There is an issue with the Heartbeat message in that module - it has
tags in the string and it shouldn't. Try replacing it with
this:CrestronMobile.sendData("");

Also, if you send me your e-mail I can send you the beta module I'm working
on as it has a lot of things fixed in it as well as support for Gestures,
etc.

Let me know if this doesn't work for you.

On Fri, Feb 24, 2012 at 5:04 AM, edch1041 <
reply@reply.github.com

wrote:

hello,

i'm using the latest crestronmobile sample programm from this site to test
the communication between crestron and cf via crestron mobile.
i'm using a mc2e (v4.3.15) as control unit and iviever4 (v4.0.196 build
196) for the visu.
the communication works fine, i also get all joins to the ipad. but in my
control unit the error log get filled up with following message:
"Error: ParseDataElement Error - Not Data Value"

does anyone know about this error message?

greets
christoph

---

Reply to this email directly or view it on GitHub:
#2

Greg Soli
Audio Advice, Inc.
704-614-2574

[edch1041]

hi greg,

the ParseDataElement error is gone, but i got some other errors and one special after closing and opening the app in a certain scenario.

to error 6 till 9:
this error only appears when i close the app (app is in the multitasking bar), lock the ipad(communication from cf to crestron goes down), unlock the ipad and open the iviewer again.
when i close the hole app, also from the multitasking bar and then open it again no error is logged. also when the iviewer is open and i lock the ipad, then wait till the connection is down and unlock the ipad again no error is logged.

error log from the mc2e:

1. Notice: Restarting Program
   TimeStamp: 07:35:38 2-27-12 UpTime: 3 days 00:16:25.45 Task: ProgramR
2. Error: Error -7 sending packet to Slot-05.IP-ID-03. (0032:000D:0032)
   TimeStamp: 07:36:31 2-27-12 UpTime: 3 days 00:17:18.12 Task: UpdateRe
3. Error: Error -7 sending packet to Slot-05.IP-ID-03. (0032:000D:0032)
   TimeStamp: 07:36:31 2-27-12 UpTime: 3 days 00:17:18.32 Task: UpdateRe
4. Error: Could not send clock update to device Slot-05.IP-ID-03, status=-1 (00BB:0000:00BB)
   TimeStamp: 07:36:31 2-27-12 UpTime: 3 days 00:17:18.32 Task: UpdateRe
5. Error: Error -7 sending packet to Slot-05.IP-ID-03. (0032:000D:0032)
   TimeStamp: 07:36:31 2-27-12 UpTime: 3 days 00:17:18.45 Task: UpdateRe
6. Error: Invalid state for Rx HeartbeatRequest
   TimeStamp: 07:37:57 2-27-12 UpTime: 3 days 00:18:44.78 Task: TCP_Read
7. Error: Invalid state for Rx HeartbeatRequest
   TimeStamp: 07:42:14 2-27-12 UpTime: 3 days 00:23:00.88 Task: TCP_Read
8. Error: Invalid state for Rx HeartbeatRequest
   TimeStamp: 07:43:40 2-27-12 UpTime: 3 days 00:24:26.54 Task: TCP_Read
9. Error: Invalid state for Rx HeartbeatRequest
   TimeStamp: 07:52:11 2-27-12 UpTime: 3 days 00:32:57.60 Task: TCP_Read
   Total Errors Logged = 9
   End of System log

maybe you already fixed this bugs in your beta version so i would be glad if you could send it to me. my mailadress is christoph.eder@elektrowagner.at.

regards
christoph