eagle.io does not seem to be able to connect to a CR1000 datalogger when the Level 3 security code is nonzero in the CR1000 datalogger. It can connect when only a Level 1 security code is set or when Level 1 and Level 2 security codes are set, but not when Level 1, 2, and 3 codes are set. I entered my Level 1 security code in the eagle.io data source setup in all three scenarios. I tested this 3 or 4 times and I got the same results each time. Very weird!
Can't connect when Level 3 security code is set
| Posts 2 | Views 16 | browsing
I've successfully replicated this issue - it seems it may be an issue with the CSI PakBus SDK.
So far i've confirmed the following:
- If Level 1 security is set and the logger is accessed with security code 1 all functions perform correctly
- If Level 1 & 2 security is set and the logger is accessed with security code 1, read operations succeed but public variable writes fail
- If Level 1, 2 & 3 security is set and the logger is accessed with security code 1, access is denied
From the CRBasic documentation:
If all three levels of security are set, each level of security code unlocks the following:
- Security(3) (lowest level) unlocks the data display, custom display, and status display.
- Security(2) unlocks the functions protected by Security(3), plus card operation and editing public table variables.
- Security(1) (highest level) unlocks the previous two levels of security, plus files, settings, configure, and editing status.
This implies that the security code submitted is being misinterpreted and the logger is assigning the wrong security level to the session. The error you received when attempting to control a value would appear to confirm this, i.e. your logger has security Level 1 & 2 set, eagle.io connected using security code 1 which should provide full access but instead is blocking updates to public variables - this would imply Security(3) (lowest level) is in effect when it really should be Security(1) (highest level).
I'll get in touch with CSI to get feedback on this issue - thanks for bringing it to our attention.