Yes, it looks like it is the ICD.
If I program it, it is working, so that make it a bit difficult if I want to debug a large project which are using HSERIN?
THX
Yes, it looks like it is the ICD.
If I program it, it is working, so that make it a bit difficult if I want to debug a large project which are using HSERIN?
THX
yeeehaaa! O.K so you can probably put some DISABLE DEBUG and ENABLE DEBUG in few place in your program OR use another structure in.
I mean, send some question or ideas with HSEROUT, then sit for an answer.
Just a thought... i'm not a big fan and user of any ICD. In fact, i can't remind when i used it for the last time... Sorry!
I'm sure somebody else will come up here with a better solution than mine anyways.
Good luck!
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Another thought. You can even use the serial communicator (no ICD) and use an USART interrupt routine that will do something you ask.
Let's make things more clear by using an example.
Let's say i want to change a,b,c parameter while the program is running. With serial communicator i'll send a specific start character, then the parameter i want to change. let's say UUCHANGEA#120
in the interrupt routine i'll write something like
By sending UUCHANGEA#120 , the a Variable is suppose to be equal to 120. Read the Serial Communicator help on that (under Transmit windows>> Parse control character) Really handy sometimes.Code:HSERIN [WAIT("CHANGE"),VarToBeChange,ValueToBeChange) Select case VarToBeChange CASE "A" : a=ValueToBeChange CASE "B" : b=ValueToBeChange CASE "C" : c=ValueToBeChange END SELECT
But be aware of the latency of your whole program... maybe a bigger amount of UU "Header" will be usefull. OR simply send something then wait fow the PIC question... as you wish.
HTH
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hi Steve.
The # sign in the sending message isn't it read by the ValueToBeChange variable?
Ioannis
Originally Posted by mister_e
NOPE, it's a MCS feature. Look in the help file. The parse control character must be enable in the MCS serial communicator.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Bookmarks