Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
PLUS+1 Compliant Hardware / Re: JS6000 and JS1 Interoperability
« Last post by Lukey on May 13, 2026, 05:33:30 AM »
Your JS6000 is 83018593https://powersource.danfoss.com/products/p/83018593
So it's a SAE J1939 type, with Node Id 0x34

JS1-H you'll have to find some more info on that, typically it will start with 11*******
https://powersource.danfoss.com/products/electronic-controls-hmi-and-iot/plus1-joysticks-and-foot-pedals/joysticks?hierarchy.level4=%22Electronic%20controls%2C%20HMI%2C%20and%20IoT%20%3E%20PLUS%2B1%C2%AE%20joysticks%20and%20foot%20pedals%20%3E%20Joysticks%20%3E%20JS1-H%20heavy-duty%20joysticks%22&tab=products
22
PLUS+1 Compliant Hardware / Re: JS6000 and JS1 Interoperability
« Last post by jraber on May 12, 2026, 04:46:19 PM »
JS6000-0126MK7, I also see JS6000-NY-CPL-F-S-FB-N-J341-A0BD-R-S-NNNNNNNR. The joystick has 2 tags on it, with serial numbers 18361744 and KD00029737.

JS1H, serial 32241157 (and that is all the info on the joystick)
23
PLUS+1 Compliant Hardware / Re: JS6000 and JS1 Interoperability
« Last post by Lukey on May 12, 2026, 05:30:30 AM »
What are the two materials No's?
24
PLUS+1 Compliant Hardware / JS6000 and JS1 Interoperability
« Last post by jraber on May 11, 2026, 07:08:04 PM »
Hello,

A client of mine is trying to physically use a JS1 in place of the obsoleted JS6000 and I am being told that it is not working. In our program we are using the JS6000_CANPlus block for handling this input, but I would think that all that is doing under the hood is parsing the raw CAN messages into an easy-to-use form. According to the data sheets of the JS6000 and the JS1 they use the same PGNs (0xFDD6, 0xFDD7), and I have verified this using the CAN logger in service tool. Same connector, same PGNs, so I would think it should be a plug-and-play upgrade, but apparently that is not the case (according to our client).

Does anyone have experience with this kind of hardware upgrade? Confirm or deny that it should "just work"?

Thanks,
JT
25
Controllers / Re: MC050-010 OBSOLETE
« Last post by samuelhj on May 07, 2026, 05:35:31 AM »
Quote from: Marbek_Elektronik on February 23, 2017, 11:15:14 AM
Please also check level on input pins.
If they are critical, you may have problems.
The thresholds are a little different.
We have had an application and the voltage levels were critical and by using MC050-010 we have had luck - it works.
By using MC050-100 our hardware produced error at the inputs:
We have send impulses to input pin and the voltage level was to high and some pulses were not counted.
So we optimized our hardware and MC050-100 worked well.

If your hardware-design is critical every change in hardware and software can produce errors!
So, check for good design everytime!

To add to that, the datasheet and the information within Guide can vary a bit, I've had that headache before, thankfully realising it early enough in the process, but I believe at least what i encountered has been updated.
26
Controllers / Re: Dynamic Node ID - Is this possible?
« Last post by Lukey on May 05, 2026, 04:39:02 AM »
It might be possible on a DM7/10/12 Display, as there is a reset/reboot/power cycle wire signal command.

On a controller/expansion module I don't think the above command is available.
27
Controllers / Dynamic Node ID - Is this possible?
« Last post by Mr.Jacobee on May 04, 2026, 08:37:10 AM »
Hello,

I would like to ask whether it is possible, from PLUS+1 GUIDE code or from an already compiled application, to reset or restart a CAN interface without performing a full power cycle.

The reason is that I need to change the Node ID of a specific CAN interface during operation. The application involves connecting two machines which normally operate independently, but in this case they need to be linked together and behave as one machine in a Master-Slave configuration.

Ideally, I would like to change the Node ID and then restart or reinitialize only the CAN interface, so the new configuration becomes active without switching the whole controller off and on again.

Is this possible in PLUS+1 GUIDE, or is a full power cycle required for the CAN interface to apply the new Node ID?

Thank you for any advice or experience.
28
PLUS+1 and C / OS API in C/C++ Files
« Last post by jraber on April 29, 2026, 06:54:22 PM »
Hello,

I am working on an internal tool that converts .dbc files into POUs that can imported into GUIDE as a single source of truth for CAN communication. I have the actual CAN communication functionality implemented using the functions provided Middleware_CAN_Base_Public (from the middleware library), but along with this I would like to implement a sort of "watchdog" that monitors for connectivity issues. I was initially trying to use time.h (the standard C99 header), and it did not work. I currently have this set up by passing OS.ETime into my POU and saving that to a static variable when the corresponding CAN message is received. From there I compare the passed in value to the static variable, and if a certain amount of time has passed since the last message was received an output variable is set to true indicating a timeout or communication error.

Now, it would be really nice if I could get the OS.ETime value directly from within the POU instead of requiring it to be passed in (there will be many POU calls so the fewer manual routes I have to do the better). The "OS C APIs in PLUS+1 GUIDE" section in the GUIDE user manual gives me hope that it is possible because it states "The presence of an APIs sub-node under the HWD node within the Project Manager tree indicates that the used HWD offers OS C API support for your project."

But I am also doubtful for my situation because I am using an MC050-110 (MC050-110/112-0_nl ver:70089372v230), and I do not see the aforementioned "APIs" sub-node under the HWD node. Is the API functionality missing from this controller or am I just missing something?

Any help would be greatly appreciated.

Thanks,
JT
29
PLUS+1 CS Hardware / Re: CS10 M2M Connection
« Last post by ToPe on April 23, 2026, 02:25:44 PM »
Hi
It is recommended to configure the CS10v125, especially the password settings, via a Bluetooth or Wi-Fi connection.

A new feature of the v125 update is that some parameters can only be written via an Interlink connection. This means that configuration is only possible via Bluetooth or Wi-Fi. This is to prevent unauthorized access to your CAN bus and lock you out (European RED-DA regulation).

Please try changing the parameters via Bluetooth instead of using the CG150.
30
Controllers / Re: MC050-010 OBSOLETE
« Last post by pinias on April 20, 2026, 07:09:58 PM »
Hey There,

I guess it is what it is but just in case.

I believe until early this year it was possible to open a file for the MC050-010 controller and get it modified if needed and compiled again for download.

now it seems it is not longer supported by GUIDE,

The question is, do you know if there is a way around to get a MC050-010 project file updated and compiled?

Otherwise I guess it will go to the recycling bin -the controller-

Thank you
Pages: 1 2 [3] 4 5 ... 10
This website uses cookies We and our partners use technologies, including cookies, to collect information about you for various purposes, including: Functionality, Statistics, Marketing By clicking 'Accept All' you consent to all these purposes. You can also choose to indicate what purposes you will consent to using the [Check boxes], then press 'Update consent'. You can always withdraw your consent by [clicking the small icon in the lower left corner of the page]. Detailed cookie information cannot be displayed if a cookie has been set behind a log-in webpage. However, the provided cookie consent prior to a log-in webpage is still applicable. You can read more about our use of cookies and other technologies, as well as our collection and processing of personal data by clicking on the link. Learn more