A function for exporting the IQANdesign channel to a DBC as Nick suggest would be a nice addition.
But for licensing reasons, we can't really make a function for exporting the SAE J1939 database that is embedded within IQANdesign.
I think the best way to work is to have DBC for the manufacturer proprietary PGN:s, and use the built-in database for the standard PGN:s.
No, the DLC will always be 8 bytes for a JFOUT.
The only J1939 message that will go out with another DLC is the request (RQST PGN 59904, DLC 3) that you send out by using the "poll trigger" on the JFIN.
The request PGN is the only J1939 message I know of that has a DLC that isn't 8.
Interesting. The MD4 low-side digital out is only checking for voltage to diagnose off state open load, I cannot see how this would cause the buzzer to give a noise.
The leakage current is quite small, less than 200 uA, but I wonder if this could be enough make the buzzer give this sound.
If you choose another resistor, the current supply needed for the RTC sets the limit on how high the resistance can be.
You'd want to minimize head dissipation in the resistor, so higher resistance is better as long as it doesn't limit the current too much for the RTC.
The Appendix A info sets the limits:
The MD4 RTC needs about 3.7 mA in a 24 V system, meaning the resistance shouldn't be higher than 24V/3.7mA = 6.5 kOhm.
I'd say that two separate 20 A fuses could be preferable. 40 A is the maximum specified for the MC4x, but one other aspect to consider is the wire gauge.
As Ken points out, if you do split it up in two 20 A fused wires, trobleshooting a cut wire could be tricky, as that would blow the fuse on the undamaged wire.
The MC4x will get time and date if a module on the bus sends the J1939 TDA message (Time/Date Adjust, PGN 54528)
But the current software on the GT doesn't implement this.
I checked and -11 V on the XC23 PWIM pin is no problem.
For this particular pin, you have plenty of margin when you don't exceed -32 V (actual limit is an even lower voltage).
Thanks for reporting.
I t's working now, but I checked and there was an issue some hours ago that prevented functionality, without crashing in a way that caused the server to stop responding to checks by the Uptime robot.
We'll need to improve the function that monitors the IQANconnect server.
In version 5.02, there was a compatibility change that required the apps to be updated. But the current version of IQANrun for tablets (5.02) should work fine with both 5.03 and 5.04 systems.
Did you run into problems when using IQANrun for tablets version 5.02 with your 5.03 system?
Customer support service by UserEcho