In IQAN, we have had the feature for reading of DM1 for ages, and DM2 reading since version 3, but reading other PGN:s that are sent as J1939 multi-packet is more tricky.
I come across more and more applications with requests for reading other PGN:s with > 8 bytes.
With a bit of knowlege and time, it is possible for an IQANdesign user to implement reading of BAM and TP.DT using JFIN channels, but it comes at the expense of overriding the DM1/DM2 reading features.
With a more integrated feature for J1939 multi packet, using e.g. a JFIN with length > 8 byte, requests such as these could be solved more easily:
With version 5.02 we added two features for outgoing multi-packet (DM1 and text), now might be a good time to develop incoming multi-packet further?
Currently its not possible to have J1939 & Generic on the same line... why not? As long as the bitcount (29) and KBPS are the same...
The thing is, I need some tricks from both systems. J1939 allows to handle engine messages more easily, and also allows to use the Page Mask byte(s), so the same PGN can be defined multiple times and split ways. But J1939 JFOUT does not allow to change the PGN programmatically, which is needed in this particular case in order to make a reusable library.
Generic JPOUTS do allow a dynamic messageID's, but don't bring the other benefits...
It would be nice if CANopen and CANopen Safety was implemented in IQAN Design.
We see the need of CANopen Safety as most of the suppliers for components such as CAN sensors are using or are planing to use CANopen Safety as the CAN-protocol for their safety related components (ISO 13849).
Today J1939 and Generic is implemented in IQAN Design. It would be nice if there was J1939, CANopen, CANopen Safety and Generic.
Would it be possible to add a SIC that holds the filename used to program the system and also timestamp of the file?
It would help us a lot to keep track of versions, specials and machines.
I know there is Version under Project Properties but it happen to often it don't get updated.
Hello again, thinking that we are in an era of smartphones applications, it would be interesting to have finger slide option to control objects movement in graphics.
Actually the "System Log" page called in "action" for a text button seems to has it. But the touch area defined by programmer to handle this is not available. Some images below. The last one is an example of how this feature would help to navigate through an alarm bar.
I think it would be useful to be able to take the description text from the CAN bus, VRef, etc or add free text to the List view of a master module:
This would allow for clearer definition when sending to a wire harness builder or for troubleshooting.
Hi, today we have silver and red reference lines. Furthermore we have the possibility to show all or only the lines from a component. When I select a component, the associated lines are highlighted a little bit with a thicker line. But it is still hard to see, if you got a mesh like I have here below.
Wouldn't it be nice if we add a third colour to highlight the lines of the selected component?
Customer support service by UserEcho