-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading other than memory area D #5
Comments
I could add that reading from D works fine - so the question really is if the headers or something else should change when reading from DM to HR (other than memoryArea byte) |
Fixed it - HR register is 0xB2, not 0x80 |
Hi Danibjor, Sorry for the late response. If you have any other problems let me know. |
Added a pull request with update to read HR register. |
yes, you have to use 0xA0 command. (see complete list below)
|
Thanks a lot, you save my day |
I tried to read data from memory area HR.
Googled around a bit and found HR to be 0x80.
I've updated the constants.js file to include HR area like this:
I've added a
console.log(temp)
to fins_client.js'_translateMemoryAddress
function just to verify that MemoryArea is in fact set to 0x80.I do a simple
.read('H00300', 24)
and do aconsole.log(msg)
in the 'reply' event method:In Omron Sysmac Studio, we inspect the H3xx memory area and it dones not look like this. Values should be like [big integer, 0, 2, ...]
Any ideas?
The text was updated successfully, but these errors were encountered: