I'm just returning to a LabJack project after several months on a different project. In my earlier work, I started with the LJWorkingWithModbus.py program, and got a configuration working with excellent help from LJ staff and this forum.
As I look at the evolution of this project, though, and add in some additional control activity, I'm thinking I should re-write this code using the LJ low-level functions rather then Modbus-oriented reads and writes. Before I embark on that, though, I want to ensure I'm moving in the right direction. Here is how I anticipate doing this: Am I on the right track?
- Operate in Command/ Response Mode
- Use low level functions
- Establish communication (I'll use existing code, which works fine) with ue9;
- Initialize ue9 devices with UE9.controlConfig() method;
- Read data with UE9.feedback() and UE9.timerCounter() methods;
- Iterate reads and send control signals via UE9.feedback() method;
I've got another question related to hardware setup: I will be counting pulses from a powermeter, with each output pulse signalling 1.25 Watt-hours. This powermeter is connected to a 60W heater, so I don't anticipate high-freq pulse counting. Hence, I expect counter0 can capture the falling edge of these pulses with no problem. However, I'm puzzled by the dynamic allocation of FIO lines to timers and counters. If I wire the pulse output from the power meter to FIO6, how can I always ensure the counter0 is looking at that pin? Or, am I misundertstanding what I read in Sec 5.3.5?
Thanks in advance, folks, I'd welcome any feedback!