Bug Reports
SW EXCEPTION (c8610007)

Hi,

When using dEX-2 to apply a schedule to our dataloggers, the dataloggers now give the error "SW Exception".

Some times the schedule does no load and there is "no config", sometimes it does load. But we get the error code every time we try to apply the schedule. The dataloggers and dEX 2 were working fine for two weeks but then this issue started. At first it was every second time but now it occurs everytime we reprogram the dataloggers.

It is happening on both our DT85 loggers, series 3 and a series 4.

The event log says: "Reset 9.22.9125 EXCEPTION (c8610007)"

Loggers are both v9.22.9125
dEX2 is v2.1.18

A second issue is the dEX program stopped recognising both dataloggers. I reinstalled dEX which fixed the problem temporally but dEX remembered its old set up and stopped communicating with the dataloggers. Deleting the logger profiles, reinstalling and trying to delete the hidden app data seemed to work for now. I am still having trouble with dEX talking to the loggers on another computer.

the error in dEX reads: "net::ERR_CONNECTION_REFUSED"

Please help resolve these issues.

Alicia

Hi, When using dEX-2 to apply a schedule to our dataloggers, the dataloggers now give the error "SW Exception". Some times the schedule does no load and there is "no config", sometimes it does load. But we get the error code every time we try to apply the schedule. The dataloggers and dEX 2 were working fine for two weeks but then this issue started. At first it was every second time but now it occurs everytime we reprogram the dataloggers. It is happening on both our DT85 loggers, series 3 and a series 4. The event log says: "Reset 9.22.9125 EXCEPTION (c8610007)" Loggers are both v9.22.9125 dEX2 is v2.1.18 A second issue is the dEX program stopped recognising both dataloggers. I reinstalled dEX which fixed the problem temporally but dEX remembered its old set up and stopped communicating with the dataloggers. Deleting the logger profiles, reinstalling and trying to delete the hidden app data seemed to work for now. I am still having trouble with dEX talking to the loggers on another computer. the error in dEX reads: "net::ERR_CONNECTION_REFUSED" Please help resolve these issues. Alicia

Hi Alicia,

Can you post the event log of the logger? SW exception will occur if there are too many events happening in a short time frame (i.e.: every a few seconds). It will create an overflow in the memory to handle those events. So if you have many events registered in the event log please try to solve it one by one. When all events have been addressed the reset will disappear.

nt::ERR_CONNECTION_REFUSED indicates you have incorrect either IP address or port number. If you use USB connection please check the information in DTUsb, if Command Port shows 7701 then you need to use port 81 in dEX 2.0

Best regards,
Rudy Gunawan

Hi Alicia, Can you post the event log of the logger? SW exception will occur if there are too many events happening in a short time frame (i.e.: every a few seconds). It will create an overflow in the memory to handle those events. So if you have many events registered in the event log please try to solve it one by one. When all events have been addressed the reset will disappear. nt::ERR_CONNECTION_REFUSED indicates you have incorrect either IP address or port number. If you use USB connection please check the information in DTUsb, if Command Port shows 7701 then you need to use port 81 in dEX 2.0 Best regards, Rudy Gunawan

Hi Rudy and Alicia,
I'm facing some similar issue, First I got "SW Exception" in device, then I deleted all Jobs using DeTransfer, using Command DELALLJOBS, now the device is showing "No current job" and to load a job I need DeX but the DeX 2.1.18 is showing "the device is offline" I uninstalled and reinstalled deleted app data still getting the same "the device is offline" . I don't know what to do to resolve this issue. any inputs would be appreciated.
Thank You.

Hi Rudy and Alicia, I'm facing some similar issue, First I got "SW Exception" in device, then I deleted all Jobs using DeTransfer, using Command DELALLJOBS, now the device is showing "No current job" and to load a job I need DeX but the DeX 2.1.18 is showing "the device is offline" I uninstalled and reinstalled deleted app data still getting the same "the device is offline" . I don't know what to do to resolve this issue. any inputs would be appreciated. Thank You.

Hi jaisantosh,

you can easily check the reason why the connection stay offline. Please go to Development - Development Tools and open up Console. Refresh the page using "Test Connectivity" button.

There are several response that you can see related to offline status:

  • No response (just Heartbeating device message) occurs when the firmware does not match the requirement.
  • 503 (Service Unavailable). occurs when the logger is not contactable (i.e.: offline, blocked by gateway)
  • net::ERR_CONNECTION_REFUSED, occurs when the port is not correct (or being blocked), IP address is not correct (or being blocked) or you use USB cable but there is no DTUsb running in the background which means the connection is virtual COM. This error may also occur when you use USB cable, there is another apps using port 80 thus DTUsb is forced to use port 81 while your dEX setting is using port 80.
  • net::ERR_INVALID_HTTP_RESPONSE, occurs when you use port number that is common for other function such as port 7700 or the target port was not running on JSON script but still giving a response

Best regards,
Rudy Gunawan

Hi jaisantosh, you can easily check the reason why the connection stay offline. Please go to Development - Development Tools and open up Console. Refresh the page using "Test Connectivity" button. There are several response that you can see related to offline status: - No response (just Heartbeating device message) occurs when the firmware does not match the requirement. - 503 (Service Unavailable). occurs when the logger is not contactable (i.e.: offline, blocked by gateway) - net::ERR_CONNECTION_REFUSED, occurs when the port is not correct (or being blocked), IP address is not correct (or being blocked) or you use USB cable but there is no DTUsb running in the background which means the connection is virtual COM. This error may also occur when you use USB cable, there is another apps using port 80 thus DTUsb is forced to use port 81 while your dEX setting is using port 80. - net::ERR_INVALID_HTTP_RESPONSE, occurs when you use port number that is common for other function such as port 7700 or the target port was not running on JSON script but still giving a response Best regards, Rudy Gunawan
133
3
3
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft