How to record data in csv and excel file

[aminulhaq]

Hi,
I want to record data first in csv file but when i am doing this it is not recording value after parser
is there any way to direct record data to excel with timespan directly
Thanks
See pic for reference

[Steve-Mcl]

As the help says...

When converting to CSV, the columns template is used to identify which properties to extract from the object and in what order.

Since you set the CSV node columns as ...

it is expecting you to feed it with data that looks like {"frequency": 49.29, "Hz": 50}

[aminulhaq]

The value after parser is not getting but before parser it is recording values

[Steve-Mcl]

that makes no sense nor does it help us to help you.

Additionally, please use the reply button on my comment (and NOT the reply button at the bottom of the thread) because I do NOT get a notification and do not know you have replied (to me)

[aminulhaq]

Hi,
I meant to say when i connect to point then csv file is getting data and saving to file
but when i connect csv node to point 2 then it is not getting data and save to file

[Steve-Mcl]

@aminulhaq

I meant to say when i connect to point then csv file is getting data and saving to file
but when i connect csv node to point 2 then it is not getting data and save to file

And that is because of what I said in my previous post...

@Steve-Mcl

Since you set the CSV node columns as ...

it is expecting you to feed it with data that looks like {"frequency": 49.29, "Hz": 50}

The fact it works by connecting to the modbus node is because that data is an array of 2 values and you have 2 entries in the column field.

SO - your options are depenedant on what you are trying to achieve. Do you want 1 value in the file or 2 values in the file?

If you simply want the value of item2 - set the column field to item2

The better solution...

A better solution is to do what I suggested in the previous thread...

@Steve-Mcl

If you are reading registers 240-241 AND registers 256-257 then I strongly recommend you read all registers from 240~257 in one MODBUS node and use the parser to pick out the values of interest. This has the following advantages....

1. values are read at the same scan of the device (and are therefore consistent)
2. reading 1 modbus poll of 28 items is faster than 2 modbus polls. This will only get worse with each additional single read/poll.
3. Individual modbus comms lead to contention on the wire (and eventually timeouts - search the forum - covered many times)

@Steve-Mcl

Use the offset to access other bytes,

MB address	Returns	offset byte
240	16 bit integer (2 bytes)	0
241	16 bit integer (2 bytes)	2
242	16 bit integer (2 bytes)	4
243	16 bit integer (2 bytes)	6
244	16 bit integer (2 bytes)	8
245	16 bit integer (2 bytes)	10
246	16 bit integer (2 bytes)	12
247	16 bit integer (2 bytes)	14
248	16 bit integer (2 bytes)	16
249	16 bit integer (2 bytes)	18
250	16 bit integer (2 bytes)	20
251	16 bit integer (2 bytes)	22
252	16 bit integer (2 bytes)	24
253	16 bit integer (2 bytes)	26
254	16 bit integer (2 bytes)	28
255	16 bit integer (2 bytes)	30
256	16 bit integer (2 bytes)	32
257	16 bit integer (2 bytes)	34

e.g...

If you do this and set the CSV column to energy,voltage then it will log both fields together with consistency (i.e. values read at the same point in time)

[aminulhaq]

no i didn't use that setting which you said in parser see my setting in picture i wnat to store frequency and voltage value on seperate column

[Steve-Mcl]

@aminulhaq

i wnat to store frequency and voltage value on seperate colum

If you want to store BOTH values you need BOTH values in a SINGLE message.

Setting the buffer parser as I have instructed several times will get BOTH values into 1 object - with well defined sensible names. That's why I suggested using the buffer-parser to pick both values from the data at once (as well as the consistency and reduced polling benefits).

What are you not understanding here?

[aminulhaq]

I understood what you are trying to say but as i am in testing phase so i am now just trying to get one value that is frequency but after parsing it is not coming in file but showing correct value in debug window

[Steve-Mcl]

@aminulhaq

but as i am in testing phase so i am now just trying to get one value that is frequency but after parsing it is not coming in file but showing correct value in debug window

ok, then change the CSV node column to match the payload property name. e.g. set the column field to item1 (better still, change the buffer-parser named "item1" to "Frequency" and set the CSV column field to Frequency- either way, the .propertyName has to match something in the column field.

[aminulhaq]

Thanks Steven once again
Now i will open another querry because i want my data with time stamp and need excel file will need your help there
Thanks