RS-485 with STC12C5A60S2 MCU issue

mjawed

Newbie
Joined
Nov 21, 2010
Messages
2
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Location
Karachi, Pakistan
Activity points
1,309
Hi Friends,
I am looking for some help regarding the PARKING GUIDANCE SYSTEM (based on STC12C5A60S2 MCU - CHINESE Manufactured) with RS-485 interface for the PC serial /USB port, as well as for the attached Ultrasonic Vehicle / Car presence sensor with RED/GREEN LED indicator light modules.

The problem is that the mentioned Baud Rate (as described in User Manual) for both of the RS485 serial ports are 4800 for Sensor Port and 9600 for PC serial interface (via USB to RS485 converter / adapter), respectively.

But, using the standard SERIAL TERMINAL Apps for PC, e.g TERMITE, REAL TERMINAL and Advanced Serial Port Terminal, the DATA bytes received or sniffed at the connected RS485 serial ports are NOT visible, or readable in HEX or ASCII, since the MCU starts to dump the data after power up (e.g. ASCII syntax to scan connected sensors at the SENSOR INTERFACE SERIAL PORTs).

Pictures and the USER MANUAL are attached for reference only.

Any help regarding this issue shall be appreciated.

Best Regards,
 

Attachments

  • PGS__Sensor__2.jpeg
    124.2 KB · Views: 12
  • PGS__Sensor__3.jpeg
    106.7 KB · Views: 11
  • PGS__Sensor__4.jpeg
    68.5 KB · Views: 11
  • PGS__Sensor__5.jpeg
    111 KB · Views: 11
  • PGS__Sensor__6.jpeg
    47.3 KB · Views: 13
  • PGS__Serial Terminal__1.jpg
    156.7 KB · Views: 12
  • PGS__Serial Terminal__4800.jpg
    278.9 KB · Views: 11
  • PGS__Serial Terminal__9600.jpg
    243.3 KB · Views: 12
  • PGS__SETUP__1.jpeg
    72.9 KB · Views: 12
  • PGS__SETUP__2.jpeg
    30.9 KB · Views: 14

I’m not sure I follow anything you’re saying, other than that you’ve got two devices with different baud rates connected. I think you need to resolve the baud rate issue before you do anything else.
 

Hi,

the raw data sent via terminal software may not be human readable.
In so far I´m not sure what you report as an error .. really is an error.

All the data recived ... and translated into ASCII strings (repersenting a HEX value) are huma readable. No matter whether the data make sense or not.

--> thus I recommend to dive deeper into error investigation:
* what reply data length do you expect?
* what reply data length do you get?
* do you get any framing errors, parity error, stop bit error?

Do you have a scope to show the communication signals?

Klaus
 

Similar threads

Cookies are required to use this site. You must accept them to continue using the site. Learn more…