adccommunitymod (AutomationDirect) asked a question.
DL06 PORT 1 BAUD RATE @ 300
Created Date: December 02,2007
Created By: elevmike
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Apparently I errored in my program code and over wrote the system memory thus changing the port 1 baud rate to 300. My solution would be to initialize the scratch pad, but that dosn't work. The next thing would be to add a line of code to change the baud rate, then re-edit the link for the defaut baud rate. The problem is the user manual dosn't indicate which Vmem controls port 1 baud rate. Does anybody know this?? Thanks, Mike
Created Date: December 03,2007
Created by: bcarlton
No solution - that's kind of scary. I thought port 1 was was FIXED. I would think something in system ROM would set that. I would think the answer to this would be either something they won't want you to share or it will be a 'return to AD ' type thing.
Created Date: December 03,2007
Created by: elevmike
Apparently it's not fixed by rom..
I had a data table that over wrote past V7377.
Created Date: December 03,2007
Created by: allukes
That doesn't make sense. If the firmware doesn't initialize it then the scratch pad initialization would have to. How else would it get set?
Created Date: December 03,2007
Created by: elevmike
This issue has been resolved using a DCM unit to initialize the scratch pad.
Thanks, Mike.
Created Date: December 03,2007
Created by: marksji
I also thought port 1 was fixed; its supposed to be the uber "I screwed up, but always have a way back in " port. Anyone at AD know how this could happen and what needs to be done by us writing the programs to make sure it doesn't?
Created Date: December 03,2007
Created by: bmaderazo
Even better question, if it can be changed, can we figure out the VMEM locations and use a different device address/port settings/etc?
Created Date: December 03,2007
Created by: elevmike
Guys,
No need to frett..
What I did here was really stupid, so the incidence of this happening to you is probably really really low. Additionally, recovery was very simple.
Not a big deal.
Created Date: December 09,2007
Created by: k1
What did you do? I have this same problem now with a 06. I'm stuck at 300 unless I cycle power. Upon restoring power it resorts back to 9600, but soon is at 300 again.
The only consequence is my impatience so I haven't thought much about it until now.
Created Date: December 09,2007
Created by: bcarlton
In his second post elevmike noted that he had written into an area past V7377. Probably he was using a pointer method of writing and did not stop at the end of the documented area and got into critical locations. It is strange that the operating system doesn't protect itself.
Created Date: December 10,2007
Created by: elevmike
bcarlton,
That's exactly correct!! I had an incrementing pointer that I forgot to limit at the end of the user Vmem.
K1,
Look over your code very carefully. Somewhere, somehow it's writing data to other then the User Vmem areas.