Charmed Quark Systems, Ltd. - Support Forums and Community
Serial Port read failed, frame errors, can't purge....*sigh* - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=3)
+--- Forum: CQC Support (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=9)
+--- Thread: Serial Port read failed, frame errors, can't purge....*sigh* (/showthread.php?tid=8279)



Serial Port read failed, frame errors, can't purge....*sigh* - beelzerob - 04-22-2013

It's been very slow going getting these old drivers to come back up. For the Ocelot and Datanab, it seems to be a COMM port related issue, now that the local config file issue is resolved.

When first connecting, the Datanab does do some kind of response, but when going back for data, it gives a read error, and then a "can't purge" the read buffer error, and then just cycles over and over doing that. Is the problem possibly anywhere other than in the device itself?


Code:
04/22 22:55:14-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.559, Status/App Status
    <GetIncomingData>: Entering function
}
04/22 22:55:16-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.168, Status/App Status
    <GetIncomingData>: Msg received []
}
04/22 22:55:16-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.603, Status/App Status
    <GetIncomingData>: Unexpected response size received: 0
}
04/22 22:55:16-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.629, Status/App Status
    <GetIncomingData> No data to process.
}
04/22 22:55:26-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.1814, Status/App Status
    <Connect> Updating sensors (second try)
}
04/22 22:55:26-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.168, Status/App Status
    <Send> Sending msg: [FA0300640020]
}
04/22 22:55:26-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.659, Status/App Status
    <GetIncomingDataAddr>: Entering function
}
04/22 22:55:26-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.691, Status/App Status
    <GetIncomingDataAddr>: [DISCONNECT] Read failed on /Local/COM1. Port Err: {Frame}
}
04/22 22:55:26-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.1011, Status/App Status
    <UpdateSensors>: An error occured attempting to get data from the address.  Data req result was: Disconnect
}
04/22 22:55:26-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.1829, Status/App Status
    <Connect> [DISCONNECT]
}
04/22 22:55:29-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCKit, CQCDriver_DriverBase.cpp.3553, Status/App Status
    Driver 'Datanab32-1' is trying to connect to its device
}
04/22 22:55:29-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.1771, Status/App Status
    <Connect> Entering Connect function
}
04/22 22:55:29-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.764, Status/App Status
    <GetIncomingData>: [DISCONNECT] Could not purge the read buffer for /Local/COM1
}
04/22 22:55:29-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.1787, Status/App Status
    <Connect> Device at Address 250 is not responding.
}
04/22 22:55:29-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.1829, Status/App Status
    <Connect> [DISCONNECT]
}
04/22 22:55:32-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCKit, CQCDriver_DriverBase.cpp.3553, Status/App Status
    Driver 'Datanab32-1' is trying to connect to its device
}
04/22 22:55:32-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.1771, Status/App Status
    <Connect> Entering Connect function
}
04/22 22:55:32-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.764, Status/App Status
    <GetIncomingData>: [DISCONNECT] Could not purge the read buffer for /Local/COM1
}
04/22 22:55:32-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.1787, Status/App Status
    <Connect> Device at Address 250 is not responding.
}
04/22 22:55:32-hickory, CQCDrvDev, CIDMacroDbgThread1
{
    CQCGenDrvS, MEng.User.CQC.Drivers.DataNab.DriverImpl_Dev.1829, Status/App Status
    <Connect> [DISCONNECT]
}



Serial Port read failed, frame errors, can't purge....*sigh* - Dean Roddey - 04-22-2013

If you are getting frame errors, it would seem that the port settings don't match the device's port settings.


Serial Port read failed, frame errors, can't purge....*sigh* - beelzerob - 04-23-2013

Hmm...possible, I guess, though I haven't touched any of those devices since they last worked, so I've definitely not changed the hardware settings for the port (if there are any), and haven't changed the manifest settings for port connection. But I'll double check.


Serial Port read failed, frame errors, can't purge....*sigh* - Dean Roddey - 04-23-2013

Could also be because you need a null modem and aren't using one, or vice versa I guess?